locked
Registry Cleaners Taking A Long Time Scanning Vista x64.... RRS feed

  • Question

  • I'm using a couple registry cleaners and they both take a long time scanning! I'm talking hours and hours. I'm using Wise Registry Cleaner and I'm also using a demo version of TweakNow's RegCleaner Pro. Both are Vista x64 certified and both work, but I've yet to let them run through a complete cycle. They don't stall or stop, but when they get to the Wow6432Node registry keys, it takes FOREVER to scan. As I said before, it takes hours! I'm not exaggerating at all either. I've waited two hours before I stopped it and hit delete the safe keys, thinking maybe it would take a shorter time next time, but no luck so far.

    I'm starting to wonder if my Vista x64 install is borked or something. The only trouble I'm having with Vista x64 is with some Creative drivers for my X-Fi....no biggie really...just Creative's problem, not Windows I don't think. The other one is IE7 and Windows Messenger Live! giving me a Werfault when I have two separate IE7 browser windows open, it causes Messenger to shut down, but that's it.

    I don't see how something can be wrong with my system that would take it hours to go through. I don't have that many programs at all on windows! I just built this computer about 2 months ago and I am dual booting with Vista x64 and XP on two separate partitions of course. Why in the world is it taking so long to scan through this Wow6432Node key? I know it's some sort of reflector for 32-bit programs under Vista 64-bit, why so many keys?? I just want to make sure nothing is wrong here. I don't see how anything could be, but ya never know. When I do a quick scan with RegCleaner Pro, it only takes a few seconds, but when I do a full scan, it takes hours. I'm going to leave it on all night and see if it's still going in the morning. If I scan with Wise Registry Cleaner, it does the same thing, but if I uncheck scanning the software section, it only takes a couple minutes to scan the registry because it skips the Wow6432Node key.

    I just want to know if something is wrong....is this typical or if there's a way to speed things up. I have a Core 2 Quad Q6600, Asus P5B-E mobo, 4GB of Corsair XMS PC5400 RAM, GeForce 8800 GTX, SB X-Fi sound card.

    As of right now, it's been scanning for 32 minutes and it's scanned 2540000 value's and counting. In WinXP, when I had the same install for 2 years going, the longest it ever took was maybe 3 minutes using any any registry scanners including RegCleaner. If anyone can shed some light on this, that'd be great! 

    BTW, both Wise Registry Cleaner and TweakNow's RegCleaner Pro both claim to work with Vista x64.  I've stopped the scanning after a couple hours and let it delete the "safe" entries it had found so far and rebooted to make sure everything was still working fine and I haven't found any problems....it's just taking a looooooong time to scan and I want to know why....thanx
    Monday, June 18, 2007 10:50 AM

Answers

  • Thanks alot guys! After doing this I got the scanner in one care live (online) to work. Works great!

     

    Thursday, January 10, 2008 11:36 AM

All replies

  • Hi Bowen,

    very simple and stupid fix...

    there is a wow6432node entry inside the first one, should only contain info for IEXPLORE.EXE in it.. just delete it and PRESTO! prob solved

     

    eg

     

    HKLM -> SOFTWARE -> wow6432node -> wow6432node (-> microsoft..windows.. etc ..iexplore.exe)

    just delete the last wow6432node..

    Wednesday, June 20, 2007 3:22 AM
  •  bugfree wrote:

    Hi Bowen,

    very simple and stupid fix...

    there is a wow6432node entry inside the first one, should only contain info for IEXPLORE.EXE in it.. just delete it and PRESTO! prob solved

    eg

    HKLM -> SOFTWARE -> wow6432node -> wow6432node (-> microsoft..windows.. etc ..iexplore.exe)

    just delete the last wow6432node..



    You're kidding right? Why is it taking sooooooo long to scan? When I look at the reg scanners, you see Wow6432Node\Wow6432Node\Wow6432Node\Wow6432Node\Wow6432Node\Wow6432Node....
    like that. I forget how many of there are but allot! I wondered why there were so many of the same key.

    Upon further viewing...looking at the Wow6432Node key, I see there are much more than just IE. I see a whole list of things, in fact it looks like there is every 32-bit program I have installed within it. If I delete it, I'm quite certain, it will cripple my computer. I'll look and see how many other places it's in. Thanks for the response!

    After looking at it some more even, I found that there is a Wow6432Node in each section....that is there is one in HKEY_CLASSES_ROOT, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, HKEY_USERS. The only one that it's not in is HKEY_CURRENT_CONFIG. Can you be more specific as to which one to delete?

    I'm running a scan again to get a more complete view of what it's scanning and currently, it's on around 555,000 and this is what it says it's scanning.  Section: Applications Section
    Registry Key: software\Wow6432Node\Wow6432Node\Wow6432Node\Wow6432Node\Wow6432Node\.....and then it has values racing by too fast to see, but the Wow6432Node keeps on building and soon there will be 8 of those in a row, then 10 etc.  I'm not sure how far it keeps extending, only that it takes at least 4 or 5 hours to do, maybe more.  I don't understand why it takes sooooo long to scan this when I don't even have that much installed!
    Wednesday, June 20, 2007 3:40 AM
  • Thanks bugfree - that helped out a lot. Obviously Bowen just didn't get that you only delete the one key under Local Machine-software-wow6432node which is also called "wow6432node" and only has the Microsoft key under it with a couple of keys under the Microsoft one ending with IEXPLORER.exe. I now take seconds to clean the registry where before it took hours.

     

    Thanks again,

     

    Mike

    Saturday, June 23, 2007 8:06 AM
  •  mikekist wrote:

    Thanks bugfree - that helped out a lot. Obviously Bowen just didn't get that you only delete the one key under Local Machine-software-wow6432node which is also called "wow6432node" and only has the Microsoft key under it with a couple of keys under the Microsoft one ending with IEXPLORER.exe. I now take seconds to clean the registry where before it took hours.

    Thanks again,

    Mike



    No, I saw it...I just wasn't certain that, that was the one.  There are other Wow6432Node keys ya know.  I wanted to be absolutely certain that there was.  After you posted, I decided to go and give it a shot.  I went ahead and created a Restore Point and did it and bugfree was right!

    Now, having said that, I found a registry cleaner that overlooks that error even if you don't delete it.  It's a registry cleaner found in TuneUp Utilities 2007, but apparently that's a moot point as any one will work that is certified for Vista now.

    Thanks bugfree and thanks Mike for clearing that up for me.
    Sunday, June 24, 2007 12:39 PM
  • Thanks alot guys! After doing this I got the scanner in one care live (online) to work. Works great!

     

    Thursday, January 10, 2008 11:36 AM
  • in my opinion using the latest Software 2009 for windows is the best tools, I'm not PC health expert but I had problem like this before so I appreciate to many pc health advisor

    _____

    pchealthadvisor

    Sunday, October 17, 2010 9:30 AM