Solving Win10 permissions by install into a user directory

[brygun]

As discussed on the forums at this time stamp I have a new laptop and was transferring the files over. Then there was a mix of issues (aside from not using 'transfer' licence but 'remove'... don't do that). 

Then I ran into the save game couldn't happen unless I ran as administrator. Okay, we figured that out.

Then I had a fleet battle start and I like to zip the game just in case of wonky things or real life interruptions like having to rapid close the laptop, cats walking on the keyboard and wondering how the cat got into the coffee shop.

So this couldn't zip or 7z to compress the game save also went I wouldnt be at good as doing bug reports.


Poking around found that the save directory was set to read only and was refusing to stop being that. In fact the whole NWS higher directory was doing that. A frustrating attempts at trying to convince my laptop that me the owner who only setup one user on the laptop is the administrator so do what I say was met with mischievous laughter of Win10 is robust to hacking which looks a lot like this.

So finally... what was the solution....

Install Rule the Waves 2 into a >user< directory not the default c:\ root directory. Such as C:\Users\that_cat


A root install Win10 does its weird super protection on.  In a user directory you don't have that issue.

A sign that a player installed to a root directory is that having to run as an admin in order to save the game or save preferences. Those not happening are showing the "read only" Win10 defense force is on duty. If you see that reinstall to a user directory.

If you use the Win10 uninstall and task manager then rerun the setup files (and current patch) the license information will survive so you won't have to email the devs again.

For the community,

Brygun

[rimbecano]

This can happen with any game that writes save data to its own install directory. Windows is basically the only OS today that lets applications do that at all, when they aren't installed in a user directory, for historical reasons related to DOS compatibility. But allowing that is a security risk (it makes it easier for persons with ill intent to slip malware onto a computer disguised as a legitimate application, and has even more security implications in a multi-user business environment than in home use), so even Windows puts a ton of restrictions on it. Applications these days are supposed to save their data in the Application Data directory in the user directory of the user running the application, wherever the application is actually installed, but a lot of users and developers are used to the DOS model of everything related to an application being under one directory, so that still survives.