Current Events > My Windows 10 got screwed up and I'm depressed

(+) Yeah! (+)

Like every other game I try to launch... just doesn't launch. The Event Viewer shows me the below error. Tried asking on the PC board but no one has given a good solution there. ugh.

Faulting application name: WindowsPlayer.exe, version: 2019.4.13.34615, time stamp: 0x5f8683fd
Faulting module name: KERNELBASE.dll, version: 10.0.18362.1350, time stamp: 0x9ccf9e81
Exception code: 0xc00000fd
Fault offset: 0x000000000002e372
Faulting process id: 0x2e20
Faulting application start time: 0x01d71356ac8adb78
Faulting application path: E:\SteamLibrary\steamapps\common\Project Gorgon\WindowsPlayer.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: b6b544a0-6eb8-40ea-b0f4-e07ee8fe59f6
Faulting package full name:
Faulting package-relative application ID:

---

This is why the first thing I do after installing windows 10 is disabling auto-updates

sound like it windone

---

It's fudging weird. I was able to "fix" that one game by running it in compatibility with Windows 8 and as an admin... don't know why I need to do that for all the games these days.

---

have you gone to the file path listed in the error? just from a quick lookup it sounds like this game specifically gets flagged by antivirus programs so maybe the WindowsPlayer.exe launcher got quarantined? i've had my AV do that before.

---

monkmith posted...

have you gone to the file path listed in the error? just from a quick lookup it sounds like this game specifically gets flagged by antivirus programs so maybe the WindowsPlayer.exe launcher got quarantined? i've had my AV do that before.

As far as I can tell it's not Windows Security Essentials flagging anything, it's the game trying to reference that kernelbase.dll file and then something's glitching out.

WindowsPlayer.exe is that game launcher like you said, I think I was able to fix it through compatibility settings but I never had to do anything like that before :\

[LFAQs-redacted-quote]

Thanks for this. I tried several different ways to fix it. One response on MS Support page was to update the file's authorizations and permissions and I did that and it didn't work.

Also did a system file check (SFC) scan to find corrupted files and update/replace them and the command prompt said it fixed some things but that didn't fix it.

I guess my next step is to try pulling that file from another computer, just... blegh. I'm afraid if that doesn't work because then you get into the "repairing/reinstalling windows" territory.

---