reg cleaner s-l-o-w

piaqt

I have a 60 gig c:\drive, vista ultimate, 2 gigs ram. So why does regcleaner take over an hour to run in agressive mode? I'm using v. 1.7.0.413.

jv16

piaqt wrote
I have a 60 gig c:\drive, vista ultimate, 2 gigs ram. So why does regcleaner take over an hour to run in agressive mode? I'm using v. 1.7.0.413.

Doesn't sound right. Have you tried to run different scan modules to see which one takes the most time?

piaqt

Yes, and even when I uncheck most options, it still runs slow. I'm using avast AV and Spybot. Would either of these affect jv16 performance?

Structured seems a little more problematic. I use the raw view. And it used to be FAST.

The slowdown starts when it's down to 7 or 8 threads.

piaqt

I unchecked "use as little cpu power as possible", and from a cold boot, with no other apps in use, it took 1.5 hours to get down to 3 threads, at which time I aborted it.

This is a list of running processes. Any of these possibly responsible?

PID: 424 (4) \SystemRoot\System32\smss.exe

PID: 492 (480) C:\Windows\system32\csrss.exe

PID: 536 (480) C:\Windows\system32\wininit.exe

PID: 548 (528) C:\Windows\system32\csrss.exe

PID: 580 (536) C:\Windows\system32\services.exe

PID: 596 (536) C:\Windows\system32\lsass.exe

PID: 604 (536) C:\Windows\system32\lsm.exe

PID: 692 (528) C:\Windows\system32\winlogon.exe

PID: 804 (580) C:\Windows\system32\svchost.exe

PID: 868 (580) C:\Windows\system32\svchost.exe

PID: 904 (580) C:\Windows\System32\svchost.exe

PID: 964 (580) C:\Windows\System32\svchost.exe

PID: 1032 (580) C:\Windows\System32\svchost.exe

PID: 1060 (580) C:\Windows\system32\svchost.exe

PID: 1200 (580) C:\Windows\system32\SLsvc.exe

PID: 1244 (580) C:\Windows\system32\svchost.exe

PID: 1400 (580) C:\Windows\system32\svchost.exe

PID: 1552 (580) C:\Program Files\Alwil Software\Avast4\aswUpdSv.exe

PID: 1628 (580) C:\Program Files\Alwil Software\Avast4\ashServ.exe

PID: 1772 (1032) C:\Windows\system32\Dwm.exe

PID: 1832 (1756) C:\Windows\Explorer.EXE

PID: 2032 (580) C:\Windows\System32\spoolsv.exe

PID: 268 (580) C:\Windows\system32\svchost.exe

PID: 332 (1060) C:\Windows\system32\taskeng.exe

PID: 1620 (1832) C:\Windows\System32\igfxpers.exe

PID: 1580 (1832) C:\Windows\System32\rundll32.exe

PID: 1572 (1832) C:\Program Files\Gigaware\Gigaware Driver\4.06\Mouse32A.exe

PID: 1524 (1832) C:\Program Files\QuickMenu\QuickMenuPlus.exe

PID: 1812 (1832) C:\Program Files\Alwil Software\Avast4\ashDisp.exe

PID: 640 (1832) C:\Program Files\Synaptics\SynTP\SynTPEnh.exe

PID: 1676 (1832) C:\Program Files\Windows Sidebar\sidebar.exe

PID: 1760 (1832) C:\Program Files\Spybot - Search & Destroy\TeaTimer.exe

PID: 1104 (1832) C:\Program Files\Mobile Master\MMAgent.exe

PID: 2056 (1676) C:\Program Files\Windows Sidebar\sidebar.exe

PID: 2072 (1832) C:\Program Files\Windows Media Player\wmpnscfg.exe

PID: 2100 (1832) C:\Program Files\WIDCOMM\Bluetooth Software\BTTray.exe

PID: 2128 (1832) C:\Program Files\Microsoft\Feeds Plus for Windows\feedsplus.exe

PID: 2304 (1104) C:\Program Files\Mobile Master\MMScan.exe

PID: 2680 (580) C:\Windows\system32\svchost.exe

PID: 2736 (580) C:\Program Files\Intel\Wireless\Bin\EvtEng.exe

PID: 2768 (580) C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG\mdm.exe

PID: 2924 (580) c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\sqlservr.exe

PID: 2940 (804) C:\Program Files\WIDCOMM\Bluetooth Software\BtStackServer.exe

PID: 2996 (580) c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe

PID: 3092 (580) C:\Windows\system32\svchost.exe

PID: 3108 (580) C:\Program Files\Dell Support Center\bin\sprtsvc.exe

PID: 3156 (580) c:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe

PID: 3172 (580) c:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe

PID: 3192 (580) C:\Windows\system32\svchost.exe

PID: 3228 (580) C:\Windows\System32\svchost.exe

PID: 3256 (580) C:\Windows\system32\SearchIndexer.exe

PID: 3912 (580) C:\Program Files\Alwil Software\Avast4\ashMaiSv.exe

PID: 3968 (580) C:\Program Files\Alwil Software\Avast4\ashWebSv.exe

PID: 1096 (1060) C:\Windows\system32\taskeng.exe

PID: 3068 (804) C:\Windows\system32\wbem\wmiprvse.exe

PID: 2712 (804) C:\Windows\system32\wbem\unsecapp.exe

PID: 4152 (580) C:\Program Files\Windows Live\installer\WLSetupSvc.exe

PID: 4960 (580) C:\Program Files\Windows Live\Messenger\usnsvc.exe

PID: 2400 (5748) C:\Program Files\Windows Live\Messenger\msnmsgr.exe

PID: 3628 (1760) C:\Program Files\Spybot - Search & Destroy\SpybotSD.exe

PID: 0 (0)

PID: 4 (0) System

PID: 1164 (964) audiodg.exe

jv16

Could you try only to run the very first scan module with Use as little cpu power as possible disabled?

piaqt

Doing so now.

Damn! The file reference scan took 35 minutes!

Repeat with each of the others?

And the results are in:

Add/remove software 6825.9 seconds=113.765 minutes

File extension 2934.8 secs=48.9 mins

font entry 1.6 secs

menu order 1.6 secs

obsolete software 189.4 secs

left-over software data 56.7 secs

help file entry 1.6 secs

app path 1.7 secs

open with entry 1.4 secs

shared components 1.6 secs

MRU/history 35.4 secs

ActiveX/COM/DCOM/OLE has been running for more than 1.5 hours, and still isn't done. :

piaqt

I cleared my superignore.dat file. (was 477kb)

Guess what? Regcleaner took only 105 seconds in aggressive mode!

Also, avast AV and spybot were disabled.

jv16

piaqt wrote
I cleared my superignore.dat file. (was 477kb)

Guess what? Regcleaner took only 105 seconds in aggressive mode!

Also, avast AV and spybot were disabled.

That's great news! Could you now try to run the Registry Cleaner with AV and spybot enabled to be sure that the slowness was caused by the ignore list file?

piaqt

Great minds think alike. With spybot And avast enabled, aggressive mode = 109.7 seconds.

trellame

piaqt wrote
I cleared my superignore.dat file. (was 477kb)

Guess what? Regcleaner took only 105 seconds in aggressive mode!

Also, avast AV and spybot were disabled.

I'm having this same problem, where's the superignore.dat file located? I'm not having any luck finding it. thanks!

piaqt

There are 6 of them, in this directory:

C:\Program Files\jv16 PowerTools 2006\Settings\

SuperDirIgnoreList.dat

SuperFileIgnoreList.dat

SuperHistoryCleanerIgnoreList.dat

SuperRegIgnoreList.dat

SuperRegManIgnoreList.dat

SuperSoftwareIgnoreList.dat

To remove items, or to clear the contents, open with notepad.

mikebcda

I use avast (home ver.) myself, and I've found it's a good idea to pause its Standard Shield when doing a scan with anything else. That way you don't have it trying to check the file while the other app is scanning, and scans tend to run quite a bit faster.

No need to totally disable avast, just pause its Standard Shield.

jv16

I have found one problem that could cause this: if your ignore list contains a lot of data this can slow down the Registry Cleaner a lot, as reported by piaqt.

This problem will be fixed in the next released version, thank you for reporting!

piaqt

De nada, and thanks.