I'm running Win 7 x64, but even in XP compatibility mode, I have the same trouble. I'm running in admin with UAC off.
I get the generic Windows error message (Windows cannot access the specified blah blah blah) every time.
The only recent (this year) post I saw concerning this was at www.cheathappens.com/show_board2.asp?headID=83604&titleID=13673 and I had already tried the solutions mentioned within.
To what I see is that you are not an UNL.member! So you would be getting the DEMO version, unless you paid for it.
There might be a security feature where Windows might be blocking EXE files downloaded from the net. For this, right click the main exe of the the trainer manager, you will get a message that the exe is blocked from the tab that is selected by default. Uncheck the box i.e. unblock the application. This is just a guess, as you are not specific with your error message.
As a 'free' member, I paid for a trainer (which works) and followed the instructions to try out the Trainer Manager before committing to becoming an Unlimited member. I don't see anything about it being a demo version on the download page (www.cheathappens.com/trainer_manager.asp)
When I said I was getting the generic Windows error message, I assumed that people would know what I meant. It's the one that always comes up in Windows since '95 to cover everything that isn't fully documented yet. The full error message is: "Windows cannot access the specified device, path, or file. You many not have the appropriate permissions to access the item."
Using Windows Troubleshoot Compatibility feature, no further information is provided other than the exe being incompatible.
So Disable your AV ----> Reinstall the trainer manager -----> Add the trainer manager's directory to your AV's exclusions ----> Restore your AV.
I hope this fixed your problem.
If I look at the zip file in winrar explorer, the icon 'looks' like an exe, but it goes changes to the 'missing shortcut' icon after extraction, though it is still registered as an application (exe) file.
Anyway, I ended running the exe on a USB drive, and that worked. I assume that there is an integral security element to Win 7 that I've not seen documented as yet.