Yeah, things are much improved with Side-by-Side Component Sharing, but problems still occasionally happen. Corrupted installs/bad uninstallers, malware, and registry rot are still serious problems though.
ToadOfSteel wrote:
Isn't that was .NET was created to address?
That was indeed a major motivation for .NET assemblies, but that won't necessarily help with older software written before .NET.
gamefreak wrote:
Using system restore for every single problem will also eat hard drive space and memory
I thought it only took disk space to make more restore points, not to actually use them? You can delete the old ones you know. There's also a disk space usage slider in the system restore tab under system properties. I know system restore sometimes automatically renames folders after a restore to preserve data in case you want undo it later, but I usually don't want to so I search my drive for the folders with "(2)" in the name and delete them. Is there something else eating memory I should know about?
gamefreak wrote:
After a fresh install with all the settings i want i do a restore point and thats the only one4 i use.
Wouldn't you have to install all the new security updates again every time you system restore? That would be a major pain. (Unless you just don't do security updates, but that's just asking for trouble.) Besides, the settings I want seem to change every few weeks. I always try to use the most recent restore point possible!