Main Forum > Tweaking.com Support & Help

WR-AIO Problem

<< < (2/2)

Shane:
If your willing, make a backup of the system and check the locations and reg key before and then after. I would really like to find out what is triggering it :wink:

If not then I will wait till you do report back :-)

Shane

Digerati:
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.

Shane:

--- Quote ---In effect, WR AIO is (in part) an automated Registry cleaner
--- End quote ---

Windows repair isnt even close or anything like a registry cleaner lol. Reg cleaners go through the registry and remove keys that it thinks are no longer in use. My program barley touches the registry and when it does it is putting back reg keys of services (Only a few of them and such. The ONLY thing the program removes from the registry is security policies put in place by viruses.

A lot of the repairs are more registering files (Which when you register a dll on the system that dll does write its info to the registry) About 80% of the repairs are registering files. The program doesnt scan the registry at all to look for keys to remove. So not a reg cleaner, at all.

The info file on each repair tells what it is going to do. :wink:

As for the rest, anytime a person finds or think there is a problem I like to do my best to find out what caused the problem, and if it was something in the program I get it fixed. That is the only way the program can get better.

Shane

Digerati:
Yeah, my apologies. I should not have said "cleaner" which brings up images of 100s and 100s of orphaned entries and stuff like that and I know this program is not like that.

--- Quote ---About 80% of the repairs are registering files.
--- End quote ---
Thanks for explaining that!


--- Quote ---The info file...
--- End quote ---
I got to admit, I missed them. Might be because in a folder right off the root of c is not where I expect to find logs. I thought they would be with the program (on my D drive), perhaps in the folder called, repairs_info, or under Users somewhere.

I see several errors like these:
--- Quote ---C:\Windows\SysWOW64\config\systemprofile\Documents\My Music - CreateFile Error : 2 The system cannot find the file specified.
C:\Windows\SysWOW64\config\systemprofile\Documents\My Pictures - CreateFile Error : 2 The system cannot find the file specified.
C:\Windows\SysWOW64\config\systemprofile\Documents\My Videos - CreateFile Error : 2 The system cannot find the file specified.
--- End quote ---
Windows lets users change those defaults to somewhere other than C. On this computer, Windows is on c but My Documents, downloads, temp files folder and the page file are not.
--- Quote ---That is the only way the program can get better.
--- End quote ---
I agree and again, appreciate the open channel.
 

Shane:

--- Quote ---I got to admit, I missed them. Might be because in a folder right off the root of c is not where I expect to find logs. I thought they would be with the program (on my D drive), perhaps in the folder called, repairs_info, or under Users somewhere.
--- End quote ---

Not the logs files, the info on each reapir. In the program there is a tab when you select a repair and the txt files for that info is int he same folder as the program under "repairs_info" :wink:



--- Quote ---I see several errors like these:
Quote

    C:\Windows\SysWOW64\config\systemprofile\Documents\My Music - CreateFile Error : 2 The system cannot find the file specified.
    C:\Windows\SysWOW64\config\systemprofile\Documents\My Pictures - CreateFile Error : 2 The system cannot find the file specified.
    C:\Windows\SysWOW64\config\systemprofile\Documents\My Videos - CreateFile Error : 2 The system cannot find the file specified.

Windows lets users change those defaults to somewhere other than C. On this computer, Windows is on c but My Documents, downloads, temp files folder and the page file are not.
--- End quote ---

That looks like just the file permissions repair. It does the whole drive except the normal user profile sections. Thats the only repair that touches everything on the drive since it is adding permissions. So with Windows virtual folder links (They did this to support old programs from xp) the program had seen there is a folder there but it was really just a link, so you get that error int he log. Nothing to worry about :-)

Shane

Navigation

[0] Message Index

[*] Previous page