Your AntiVirus / Security software blocks access to the trainer created tmp file in the "Work" folder, you will need to make an exclusion for the "work" folder and for the trainer itself. You can find information about this for the AV you use at this Link. AV scan history/log files and quarantine (if available) need to be deleted in security software.
Work folder can be found here: C:\Users\USERNAMEHERE\Cheathappens\
Also be aware that the trainer manager has been discontinued in favour of Aurora. So I would advice you to use Aurora as it's our new AIO. If the trainer is yet to be available on there, use the normal standalone. This may prevent any issues related to using trainer manager.
[Edited by SmileyJ, 8/2/2022 6:31:09 AM]
[Edited by SmileyJ, 8/2/2022 6:32:23 AM]
As noted above, the exclusion is set and all other trainers in that folder work as expected.
Also, as again noted above, I already tried to run it both in explorer and in command prompt.
This happens when you are not right clicking Run as Administrator on the trainer or your AV/security/privacy/third-party software is blocking it.
Unfortunately, same result when done this way.
At least with Windows Defender, it is *not* enough for me to exclude the folder where the trainers are at.
The reason for this is that the actual file goes to a temp folder once it has been decrypted by the CH account verification. Or something like that.
When I get the TMP error (for example yesterday with Sudden Strike 4 Trainer), then I have to go to the virus scanner screen of Windows Security settings and check for past threats. If I find one with CH TMP file, I have to manually click "accept on this device" every once in a while - that typically holds a couple days or weeks.
Ok, COOL! This did the trick. I had already discovered half of this answer when I just tried putting %TMP% as an exclusion, but that's an awful idea even though it worked.
This solution is much better, thank you!
So for anyone in the future with this problem, do as Zahlgraf says:
Open Windows Security/Defender, run the program that won't work; within windows security near live scan, it will false positive, where you can tell it to run anyway.