I have licensed Windows 7 x64 Professional.
And I had the same error with DistantWorlds.exe when I tried to execute it as a non-admin user with reduced privileges.
This is a poor programming practice, when developers know nothing about UAC and execute every task on their OSes as administrators, without protection. And they make same applications which always need admin rights for ordinar tasks.
Though many modern (and even old) games already "know" about UAC and user profiles. And work fine with reduced privileges.
And there are many topics in the Internet, how to properly use the System.Diagnostics.Process.StartWithCreateProcess, and how to make same things entirely without the StartWithCreateProcess call.
In spite of this, there exists the solution how to run the "Distant Worlds" game with reduced privileges under a non-admin account.
The "DistantWorlds.exe" is somehow controlled by the "autorun.exe" located in the same game folder.
The only thing needed is to set the "RunAsInvoker" property of the "autorun.exe" application. After this the "autorun.exe" becomes running without admin privileges. And the "DistantWorlds.exe" becomes being launched via the "autorun.exe" also under ordinar user account.
Again, the "RunAsInvoker" property must be set for the "autorun.exe", not for the "DistantWorlds.exe".
To set the "RunAsInvoker" property you may use the "Microsoft Application Compatibility Toolkit".
Just google about the "RunAsInvoker" and the "Microsoft Application Compatibility Toolkit".
Nevertheless, I hope, developers of the "Distant Worlds" game would correct this ugly bug with UAC.
< Message edited by wnxpow -- 11/10/2012 5:02:10 PM >