I originally installed WR-AIO on one of my test systems and had no problems. I didn't see any improvements, but nothing broke. So I then installed it here on my main system where I encountered the problems. I don't normally run tests or experiments on this system. Had the problem occurred on my test machine, it would have been no problem trying to duplicate the problem for you.
The test system only has one drive/partition too - if that had anything to do with it. Hopefully, more folks who install their apps off the boot drive will give it a go and hopefully have no problems either.
This was a simple recovery process, I didn't bother to restore the Registry. It took literally a few seconds for each pinned item I wanted to keep and that ended up less than a dozen between both places. It actually forced - well, gave me the opportunity to reevaluate what pinned items I really wanted on my Taskbar and in my Start Menu. And once I determined CoreTemp's problem was just a simple default text color issue, that was a simple fix too. While it appears all else is good, nothing affecting system stability or security occurred, and total recovery was a snap, I am not willing tempt fate again on this machine.
In effect, WR AIO is (in part) an automated Registry cleaner, and a fairly aggressive one. I am NOT against Registry cleaners in general - I like and use, and frequently recommend CCleaner's because it is not overly aggressive. But I recommend and use it for "maintaining" a working system, not fixing a broken one and that's because Registry cleaners, "System Optimizers", and the like have a history of doing more harm than good - though I am certain the numbers have been greatly exaggerated by a few very loud complainers repeating the same stories over the years. But sadly, I have seen too many computers myself come across my bench that were made worse by someone dinking with the Registry trying to fix a problem (some with Regedit, some with "Tools" found on the Internet. So it is hard to defend something you know can be dangerous to some colleagues, forum regulars and site staff who also have seen problems made worse.
Of course, your judicious encouragement and provision to backup the Registry sets your program apart from others. But that's not to say users will follow that advice.
Understand, I gripe but I appreciate your desire and demonstrated dedication to "getting it right".
I was one of a few hardware guys in a software company of 400 (very-sharp) programmers. One of my "other hats" was in-house alpha and beta tester for the software under development. I've made it a side career to avoid coding as much as possible but I understand and appreciate what it takes to "
create" it. Anyway, since this appears to be a one-off problem for now, let's wait and see if it appears on another system.
