...snip... When I use the Command Ops 2 icon, I get: The product is not properly authorised. Please contact Lock 'n Load Publishing support....
When I use the Update icon, I get asked for the admin password, and then Command Ops 2 starts and runs well (extremely limited testing so far.)
If I right-click the Command Ops 2 icon and Run As Administrator, I am asked for the admin password, and then Command Ops 2 runs well.
I'm not honestly sure if this is one issue or two:
a) The Command Ops 2 icon needs rights to run;
b) The Update CO2 icon doesn't appear to run an updater, but maybe it is not meant to?
Yes we specifically made the default install directory outside of Program Files because of that behaviour. It's MS trying to do the right thing by protecting applications from outside interference. Alas the by product to this is that it saddles the user with a burdensome response regime every time they want to do something to a file within that directory.Another issue might be where you install your game.
Don't install in Program Files, because the writeable files are in subdirectories, and Program Files is write protected and programs there are supposed to use the user directories to store data.
How did you launch these? Was it direct from the Game directory in Windows Explorer?Following Erik Springelkamp's tests:
I can run the Estab Editor and Estab Manager s a normal user.
I cannot run the Map Maker or Scenario Maker; I get the same error as when running the Play.exe file.