NovHak: I'm glad to help !

Updates available in your library don't depend on the version you have installed. I currently have 1.6 and have the same patches available. You can see what version you have in the game menu screen.

I almost always do uninstalls/reinstalls instead of updating games, but I agree with you there can be problems if one's not aware of a few things. However, the same problems can occur when patching instead, but you should not have such problems with Chaos Reborn.

The problems often come with games that try to write in their own installation directory, when it's installed in C:\Program Files or C:\Program Files (x86). Note that neither games nor any other program should do that in the first place.

In such a case, and when the program doesn't contain a manifest with a RequestedExecutionLevel section, Windows activates UAC Virtualisation (UACV) so that writes to the installation directory are not rejected, which may prevent the game from functioning properly.

Non-administrative writes to the Program Files directories are normally not authorised, and UACV doesn't bypass this, instead it redirects the writes to a special user directory : %LOCALAPPDATA%\VirtualStore (type this in the file explorer adress bar and you'll be directed there). So, the game can still work and security is preserved.

UACV is a good thing, the real problem is that some game developers don't integrate their games in the OS properly. When the game is updated, everything is updated correctly in the Program Files directory, but data in the VirtualStore directory remain untouched with some leftovers of the old version and can prevent the game to work properly. One should have a check at one's VirtualStore directory before running the game, and delete these old files (with the possible exception of save games).

I'm used to UACV and have absolutely no problem with it. Imho UACV is a very good initiative from Microsoft. However, I see that many people don't want to use it, in which case there are alternative solutions, neither of which are good, except if the game is installed for one user only and doesn't require administrative rights in the process. It's not ideal since the executable can still become host of malware, but there's only a limited risk that it corrupts the whole system, unless the user is lured into giving admin rights to some unlawful process that is.

It seems GOG somehow chose the same path Steam did in that respect, that is one directory writeable by any user. It's likely the path you took as well when you mention installing outside "Program Files". It's a bad choice but I won't blame you on that, since almost everybody else does the same. Eventually I've yet to find someone who does things the way I do :D