skeletonbow: I would definitely have to agree that if this problem happened to every person every time they installed it, that it would be a massive problem and the forums would be up in fireworks from just about every single person though. We're not seeing that of course, but we are seeing numerous people reporting issues where either the installation of, upgrading of, or general usage of Galaxy client has somehow caused a directory or several directories on their hard disk to just get blown away for no apparently obvious reason.
timppu: Are you talking about several different issues here together, like that Galaxy uninstallation may remove all files and folders (including GOG games) installed
inside the GalaxyClient\ subfolder? I think these are different issues (at least in severity) that should be discussed separately.
Even the Steam client uninstallation seems to work like this. I just uninstalled Steam, and it removed absolutely everything under the C:\WinPrg\Steam\, including all the installed Steam games under the steamapps subfolder, as well as a directory (temppi\) and a file (temppi\temppifile.txt) I created manually under the Steam directory just before Steam uninstallation. The whole Steam directory, and everything inside it, was wiped out, no questions asked. In fact, it did more than Galaxy uninstallation, as Galaxy didn't wipe the whole directory, but left some .js folder and file there (possibly created after the Galaxy installation?). Steam wiped out even the directory and txt file I created there manually.
Maybe that is bad design, but by some logic, maybe also expected. While I might have preferred the uninstall script to leave e.g. my temppi\temppifile.txt intact (because I had added it there manually afterwards), I am not really surprised it decided to wipe out everything that was there.
However, what the OP described is far worse and unexpected, similar to if Steam uninstallation would have wiped out the whole C:\WinPrg\ contents, also files not related to Steam in any way. That's why I was interested only in this particular problem, how many have reported it and possibly what triggers it.
I mentioned how the Galaxy uninstallation works for me because some seemed to fear that this is a widespread problem where no one can uninstall Galaxy anymore (without losing lots of other data as well from the common parent directory). Of course that doesn't help those who would be hit by it.
I come from the land of modern Linux package management philosophy and think that a package or installer should own only those files which it installs or which it personally creates during runtime all of which should be stored in a manifest file. When uninstalling, all files should be removed that are owned or created by the package, and then all directories should be removed NON-recursively - just the directory and only if it is empty. If something else dropped files in one of its directories then neither the file(s) nor the dir will get removed by that software uninstallation.
In Windows it is pretty much every app developer makes up their own rules sometimes with rather unfortunate consequences. ;/
