Feedback, Complaints or Problems

I’ve been having issues with opening newer trainers (labeled as “Trainer Template”) intermittently. The issue seemingly resolved itself a month ago, but returned last week inexplicably. Nothing on my system has changed, except for continuing Windows Updates -- and I have installed the new .NET Core 3 update mentioned in another post, in addition to retaining all previous versions.

“Trainer Template” trainers will not open. (Older trainers with the orange icon open flawlessly.) I use Windows 10 Defender, and have long ago made exceptions for the User\CheatHappens and CheatHappens\Work folder, as well as the folder the trainers are in. The trainers do not open even when Defender and Windows Firewall are completely turned off.

What I do notice is that for a couple seconds after opening a newer trainer, that a trainer file generates in CheatHappens\Work, but promptly disappears, and the trainer does not open. Again, this location is under an exception in Defender, and I do not get any popups from the app that something has happened, nor is there anything in the logs.

To try to further troubleshoot, I have also deleted all folders where I keep my trainer files to let them regenerate, and have also reset the Trainer Manager app, but to no avail.

I'm open to any suggestions anyone might have but I'm almost wondering at this point if it's a bug with .NET Core

Did you restart your computer after installing .NET Core?

If yes, please paste the details from Event Viewer in this thread.

Yes, I restart/shutdown every night, so probably a dozen or more times since.

Forgot to mention last week I also did an sfc /scannow in Command Prompt, based on other threads here, but it didn't seem to fix this issue.

Here is the most recent error from event viewer:

Faulting application name: 21242-laurenke-No Mans Sky Trainer.exe, version: 1.0.0.0, time stamp: 0x5d7eb32c
Faulting module name: ntdll.dll, version: 10.0.18362.418, time stamp: 0x99ca0526
Exception code: 0xc0000005
Fault offset: 0x00000000000203ab
Faulting process id: 0x1c44
Faulting application start time: 0x01d580c8b11682dd
Faulting application path: F:\Trainers\21242-laurenke-No Mans Sky Trainer.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 69340139-e17c-419d-93fe-86d68f1a8c1b
Faulting package full name:
Faulting package-relative application ID:

Please close ALL other applications including graphic tools, overlay tools, security tools, etc. The error log indicates the issue happens before the trainer's code is even loaded. So either there are corrupted files the trainer tries to load, which should have been detected by sfc or solved by reinstalling .NET Core or external applications causes it.

The only overlay tool I can think of besides Steam itself would be GeForce Experience. I'll close it (and also Google Drive Sync just in case) and report back. I do not use Afterburner or any of the other things I've seen mentioned here in other threads.

Update: Nope, nothing, unfortunately. I closed the above mentioned apps, plus multiple random Windows processes and I am still getting this error:

Faulting application name: 21242-laurenke-No Mans Sky Trainer.exe, version: 1.0.0.0, time stamp: 0x5d7eb32c
Faulting module name: ntdll.dll, version: 10.0.18362.418, time stamp: 0x99ca0526
Exception code: 0xc0000005
Fault offset: 0x000000000001f59f
Faulting process id: 0x2adc
Faulting application start time: 0x01d58106bd87757c
Faulting application path: F:\Trainers\21242-laurenke-No Mans Sky Trainer.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 64a28013-9ba7-46a2-b596-f4278138aaa2
Faulting package full name:
Faulting package-relative application ID:

That said I do not know what ntdll.dll is or does, but it seems to be the culprit.

This probably won't work, but should I move the trainers themselves to a different hard drive?

Randomly closing Windows processes unfortunately won't solve the issue, but as 0x90 mentioned "reinstalling .NET Core" should.

Do not forget to restart your computer as soon as the .Net Core is re-installed!

[Edited by B4Marc, 10/15/2019 3:05:19 PM]

I'm assuming 3.0 is backwards compatible with the older versions? I'll strip off all .NET Core installations, reboot, reinstall 3.0, and see what happens.