Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Digerati

Pages: [1]
1 Support & Help / Re: WR-AIO Problem
« on: October 25, 2012, 09:47:49 AM »
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.
About 80% of the repairs are registering files.
Thanks for explaining that!

The info file...
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:
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.
That is the only way the program can get better.
I agree and again, appreciate the open channel.

2 Support & Help / Re: WR-AIO Problem
« on: October 24, 2012, 09:53:14 AM »
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.

3 Support & Help / Re: WR-AIO Problem
« on: October 23, 2012, 01:08:32 PM »
Well, it is not the first time I am the only one. I am certainly not going to say my machine is typical, but it is not an uncommon setup either. At any rate, we'll keep an eye out for future problems.


4 Support & Help / Re: WR-AIO Minor Quibble
« on: October 23, 2012, 12:45:04 PM »
I count on users to let me know when they find them lol.
I count on Speckie. ;)

5 Support & Help / Re: WR-AIO Problem
« on: October 23, 2012, 12:42:04 PM »
Not sure what to tell you either. But those locations you talk about appear to be for the taskbar only and they currently look good (now that I have repaired them all - more on that in a sec). Those locations don't set the Start menu pinned tasks, however.

As for repairing the pinned items, that was odd too. For Word, for example, I had to go to the main "target" location, right click on Word where my only option was to unpin from Start Menu. This happened even if I deleted the blank icon. Once I unpinned, I could immediately pin again and all was good, and is still good after a reboot.

I also noticed CoreTemp system tray icon went away. I thought at first the program was no longer running but got yelled at for trying to start it again. I then realized it was running, but the default text color (black) came back and I just could not see it with my very dark blue taskbar background. I had changed it to white. I've been running CoreTemp for 3 years with no problems like that.

I wish some of the fixes were not set by default. For example, restoring the default Hosts file and restoring the default services settings. And I wish it reported its findings before actually fixing anything. And a log to go back and see what happened would be good too.

I think it is important to test these apps on all sorts of configurations. I know a lot of computer users that don't let Windows install everything on c. I don't know if that is the issue, and I know it is impossible to test anything close to all possible configurations, but multiple drives (and multiple monitors too) are pretty common.

If it happens again, I will let you know.

6 Support & Help / WR-AIO Problem
« on: October 23, 2012, 09:26:56 AM »
I just ran WR-AIO on this system (W7 64-bit, i7) and have run into a problem with pinned items. It seems none work after running WR-AIO. None on my taskbar and none in the start menu. Normal shortcuts work - just not pinned items.

I take that back, Windows Update pinned to my Start menu works, the other items (to things installed on my D drive) have a blank default icon and when I click on them, an error reports the item I selected is unavailable, and may have been moved, deleted, etc.
Note I install Windows and hardware drivers ONLY on my boot disk. C drive. Everything else goes on another drive. I fear WR AIO resetting everything back to out-the-box defaults may not account for users having more than one drive. And the fact Windows Update, being my sole surviving pinned item, and the only pinned item that goes to C (my boot) drive seems to support that.

If the idea is to reset the Start Menu and the Taskbar by purging them of pinned items, then that didn't work either. The pinned items should have been completely removed, not replaced with Windows default icons that point to nothing.

7 Support & Help / WR-AIO Minor Quibble
« on: October 23, 2012, 05:15:29 AM »
I never install anything but the OS, OS updates, and hardware drivers on my boot (C:) drive. I always install programs somewhere under D, and in this case, D:\Utilities\Windows Repair AIO, and in my Start Menu, I have its shortcut under Utilities too.

The problem is, if WR-AIO is already installed and you are installing a newer version, the installer does not recognize a previous version and instead of updating the old in the existing install locations, it attempts to install the new (and now 2nd) version under C:\Program Files and under its own folder in the Start menu.

It would be good if the installer would first look for any previous installs, then prompt the user to use those locations.

PS - just noticed under Repair Missing Start Menu Icons, the repair Info says, "move by rouge virus". Well, the virus may be rosy red (rouge) but I think you meant "rogue". However, since I don't know of any virus that is not rogue, I think it should just say "malware".

I personally see no reason Malware Removal folks should be involved (unless they help on the technical side too) or be concerned (once Combo-fix is removed). But I do wonder if you shouldn't narrow your focus by ensuring this is a "Windows Repair" tool and not intended as a security/malware removal or prevention tool too.

I agree that TDSS Rootkit Remover is an excellent tool and could stay as I believe the odds of further damage by an inexperienced user is minimal - worst case. But while I would argue "the normal user" could safely use TDSS, Rich (Ztruker) is right and at some sites the MR folks might (as they do with ComboFix) balk at it being suggested outside the (typically closed) Malware Removal forums.

And to that, Rich and I go way back and visit many forums on the "technical side" (HW, Windows, Networking, etc. - not malware removal). And sadly it is often the case where MR controls, or desires control of every and anything to do with malware - whether it be prevention or removal - because of the chance the untrained "normal user" may cause more harm than good. Thus only certified malware removal folks who completed an on-line MR course can suggest or manage their use. Certainly, HJT in the hands of the too-eager did result in dead systems, way too often. But that was awhile ago and when you are in the trenches surrounded by infected machines, it is hard to believe the vast majority of the 1 billion Windows machines are NOT infected. And many that are broken have a corrupted driver, a failed update, an incorrect setting somewhere. Or a real hardware problem - totally unrelated to anything malicious. Or sadly, suffered collateral damage from deployed malware, or the malware removal process itself. Or an over-eager user trying to free up too much space.

So while TDSS RKR is a great tool, not sure I would call it a Windows Repair tool. And to that, I am not crazy about specifying a specific anti-malware solution. I like how you say, "(In case you need one)" - but I think, if you really think it necessary to address security in this "Windows Repair" tool, just recommending to "get a good anti-malware program and keep it updated" prevents any unwanted opposition/tangents over which is who's favorite (ie, generic, like Step 1 of your instructions).

I see your tool as a "consolidated" Microsoft FixIt tool. A good thing! But I truly believe if you want the greatest acceptance of your tool (in terms of folks like Rich and me recommending it on the technical side of the forums), you need to narrow your focus to Windows Repair and remove any context to security and malware. JMHO.

9 Support & Help / Re: Registry Backup Problem
« on: June 10, 2012, 06:55:54 AM »

Your problem is very different than the other so I just split the thread to a new one :-)
First, sorry for hijacking the other thread. I should have just started a new one.

Still no good with new version. When it first runs, I get the following odd error:

Unable to detect which version of windows to run the VSS. Please manually select the correct VSS exe to use.
(Quibble note: note the lower case "w" on Windows).

When I select okay to close the error popup, I get the Registry Backup GUI, but then the backup fails with the same Volume Shadow Copy Failed error.

Here is the Log_VSS.txt:

[6/10/2012 - 8:50:38 AM]
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

D:\Utilities\Registry Backup>
[6/10/2012 - 8:50:38 AM]
CD /D C:\

[6/10/2012 - 8:50:38 AM]

C:\>set path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;D:\Utilities\Registry Backup\files

C:\>-script="C:\Windows\temp\vss-setvar.bat" -exec="C:\Windows\temp\vss.bat" C:
'-script' is not recognized as an internal or external command,
operable program or batch file.


10 Support & Help / Registry Backup Problem
« on: June 09, 2012, 08:05:20 AM »
New to here, but not forums or computers.
Ztruker asked me to check out Registry Backup and report any problems here. I am getting same error, so rather than start new thread, I piggybacked here (but can open new thread, if desired).

Error message:
Volume Shadow Copy Failed! isn't running. Check the Log_VSS.txt file to view any errors.
And said log says,
C:\>-script="C:\Windows\temp\vss-setvar.bat" -exec="C:\Windows\temp\vss.bat" C:
'-script' is not recognized as an internal or external command,
operable program or batch file.

This is with Windows 7 Pro, 64-bit. I have re-registered wmiutils.dll with no help.

Minor quibble - note the lower case "i" in isn't. Also, installation prompts for "Shortcut Folder". I find the term "Shortcut Folder" confusing as that is not a common term used in program installations. It should say "Start Menu" location.

Pages: [1]