AutoClean

[NerdFencer]

Updated to Version 2.3!!!

Added multi-lingual support, but I do not know more than one language, so I just used google translator. If you would like to have better support for your language, please send me any fixed translations.

Other than that, everything just upgrades existing features. There is now detailed logging, and a revert feature for the services. The revert feature will expand in future releases.

@gregv

That is a case that I had not considered. I will create a fix and send it to you to test.

[NerdFencer]

This looks like a PHENOMINAL program, we actually use a few similar programs at work (I work at a computer repair shop, most of them, virus's). Just one (free) program I would like to recommend: Hijackthis. I don't know if you will be able to automate it, but if you get it to run a scan with a report, and copy and paste the report to hijackthis.de, it will tell you numerous things that malwarebytes might not pick up.

Otherwise, I am going to look forward to checking out this program, and thank you for something I was planning on doing myself .

Thanks

Although the program does not directly use HijackThis, it does clean out some of the same stuff.

As new versions of AutoClean roll out, you can expect to see more complete coverage.

If you have any other feature requests, please feel free to ask.

-Matt

[NerdFencer]

[bump]

Released version 2.4!!!

So many downloads, so few comments...

This version has 2 really big changes.

1- A handy background process runs every 15 seconds that kills some known malicious programs that may interfere with AutoClean (or sane use of the computer). Here is the list of programs it kills. (Separated by |)

mgmrwmrv.exe|rxjddnvj.exe|aapfr.exe|eooyt.exe|rAggge.exe|rtwwf.exe|qwwyyu.exe|xxfep.exe|0mcamcap.exe|0.exe|1.exe|2.exe|3.exe|4.exe|7.exe|1.tmp|3.tmp|4.tmp|764.exe|977efcdb.exe|a.exe|aav.exe|aconti.exe|adsmart.exe|adtech2005.exe|adtech2006a.exe|AlfaCleaner.exe|algg.exe|antispysoldier.exe|AntiSpy.exe|ASC 2.1.exe|AntiSpyCheck.exe|AntiSpyCheck 2.1.exe|antiviirus.exe|AntiVirusLab2009.exe|afqgda.exe|anti_troj.exe|AntiVermeans.exe|AntiVermins.exe|AntiVerminser.exe|AntivirusGold.exe|AntivirusGolden.exe|AntivirusXP.exe|AntiVirGear 3.7.exe|AntiVirGear 3.8.exe|AnvTrgr.exe|asasa.exe|asheriff.exe|ASpCh.exe|ASpyC.exe|atmclk.exe|atzrdada.exe|autos.exe|autosys.exe|av2010.exe|av2009.exe|av360.exe|ava.exe|AvirTr.exe|avm.exe|AVR09.exe|avrlabs.exe|avs.exe|avp.exe|Awola6.exe|b.exe|batserv2.exe|bikini.exe|BraveSentry.exe|braviax.exe|brastk.exe|bsw.exe|bu.exe|buritos.exe|bxproxy.exe|c.exe|cbinst$.exe|cmd32.exe|cmdtel.exe|combo.exe|ContraVirusPro.exe|Coreguard 2009.exe|Cpl32ver.exe|ctfmona.exe|ctpmon.exe|contextplus.exe|CWS_iestart.exe|d.exe|d3dn32.exe|d3pb.exe|dcomcfg.exe|dlh9jkdq1.exe|dlh9jkdq2.exe|dlh9jkdq3.exe|dlh9jkdq4.exe|dlh9jkdq5.exe|dlh9jkdq6.exe|dlh9jkdq7.exe|DL32.exe|dll32.exe|doser.exe|dfndr.exe|dfndra.exe|dfrgsrv.exe|dr.exe|drsmartload1.exe|drsmartload45g.exe|drsmartload46g.exe|drsmartload95a.exe|drsmartload849a.exe|drsmartload849g.exe|dwltqnmx.exe|dxole32.exe|e.exe|ecsiin.stub.exe|efsdfgxg.exe|ekvrlfzz.exe|epfg.exe|eqln.exe|ESHOPEE.exe|exa32.exe|exeha2.exe|exeha3.exe|exploeee.exe|explore.exe|fbxrqtwn.exe|ffvrdgt.exe|frplprg.exe|frmwrk32.exe|fsxloqf.exe|fxtqdrl.exe|gimmysmileys.exe|gimmysmileys1.exe|gimmysmileys2.exe|gimmysmileys3.exe|gimmysmileys4.exe|gimmysmileys5.exe|gimmysmileys6.exe|gimmysmileys7.exe|gimmysmileys8.exe|gimmysmileys9.exe|gopa.exe|gunist.exe|hcwprn.exe|helper.exe|HomeAntivirus2009.exe|hookdump.exe|hotporn.exe|hpmon.exe|IAvir.exe|icmntr.exe|icthis.exe|ieav.exe|iebtm.exe|iebtmm.exe|iedefender.exe|iedrv.exe|iedrvctrl.exe|ieengine.exe|iescan.exe|iexplorer.exe|ieyi.exe|ie_32.exe|ieupdates.exe|isfmntr.exe|imsmain.exe|imsmn.exe|infos.exe|intel32.exe|intell321.exe|intell32.exe|intmon.exe|intmonp.exe|intxt.exe|ipmon.exe|isamonitor.exe|isamini.exe|isamntr.exe|ishost.exe|ismini.exe|ismon.exe|isnotify.exe|issearch.exe|Install_1_1_.exe|iv.exe|installer.exe|kernels8.exe|kernels32.exe|kernels64.exe|keyboard.exe|keyboard1.exe|keyboard2.exe|keyboard3.exe|keyboard4.exe|keyboard5.exe|keyboard6.exe|keyboard7.exe|keyboard8.exe|keyboard9.exe|kjzna1562565.exe|kkcomp$.exe|kkcomp.exe|kl.exe|kl1.exe|kthemup.exe|kvnab$.exe|kvnab.exe|kybrd.exe|latest.exe|ld01.exe|ld02.exe|ld03.exe|ld08.exe|ld09.exe|ld10.exe|ld11.exe|liqad$.exe|liqad.exe|liqui-Uninstaller.exe|liqui.exe|lich.exe|links.exe|ll.exe|lnvegaow.exe|loadadv728.exe|loader.exe|main.exe|malwarebell.exe|MalwareCrush.exe|MalwareWipe.exe|MalwareWiped.exe|MalwareWiped 6.1.exe|MalwareWipeds.exe|MalwareWipePro.exe|MalwareWiper.exe|Malware-Wipe.exe|malwaredef.exe|maxd1.exe|maxd64.exe|mcrupdate.exe|mediacodec.exe|microAV.exe|mirarsearch_toolbar.exe|mgrs.exe|mxd.exe|monhop.exe|mousepad.exe|mousepad1.exe|mousepad2.exe|mousepad3.exe|mousepad4.exe|mousepad5.exe|mousepad6.exe|mousepad7.exe|mousepad8.exe|mousepad9.exe|mqgldfvo.exe|ms1.exe|msa.exe|msas2009.exe|msdrv.exe|msdrvctrl.exe|msiconf.exe|msmapi32.exe|mscornet.exe|mslog.exe|mssearchnet.exe|mshlpp.exe|msmsgs.exe|msn_0803_upd041807|msole32.exe|mssadv.exe|msctrl.exe|msavsc.exe|msscan.exe|msiemon.exe|msfw.exe|mstss.exe|msvcp.exe|mswinb32.exe|mswinf32.exe|MSx.exe|MTE3NDI6ODoxNg.exe|multitran.exe|muwqa.exe|muwql.exe|muwqm.exe|muwqp.exe|neltabxw.exe|netfilt4.exe|newname1.exe|newname2.exe|newname3.exe|newname4.exe|newname5.exe|newname6.exe|newname7.exe|newname8.exe|newname9.exe|npad.exe|NTCommLib3.exe|ntdetecd.exe|ntnc.exe|ntps.exe|nvctrl.exe|nwnm.exe|oadkxrts.exe|officescan.exe|ole32vbs.exe|olgdqarf.exe|ongi.exe|osaupd.exe|parad.raw.exe|paradise.raw.exe|patcher.exe|PAVRM.exe|paytime.exe|pc.exe|pcdefender.exe|pcpc_starter.exe|pcprotection.exe|pdefendr.exe|pebgkxwq.exe|PestCapture.exe|PestTrap.exe|pigglett.exe|plugin.exe|pmmnt.exe|pmmon.exe|pmsngr.exe|pmsnrr.exe|policyverifier.exe|pop06ap2.exe|popuper.exe|pornpassmanager.exe|Power-Antivirus-2009.exe|pp2.exe|pp06.exe|pp10.exe|printer.exe|priva.exe|proper.exe|ptlg.exe|PWA.exe|qjrkvy.exe|qttask.exe|qttaskm.exe|r.exe|reger.exe|RegistryCleaner.exe|RegistryFox.exe|regperf.exe|repigsp.exe|Restart.exe|rs32net.exe|runsrv32.exe|sachostc.exe|sachostp.exe|sachosts.exe|sachostx.exe|sav.exe|sawkip.exe|sbmntr.exe|sbsm.exe|scan.exe|scit.exe|sclick.exe|scm.exe|sb6i.exe|sdfdil.exe|sdkqq.exe|secure.exe|sender.exe|SetupAntivirusXP.exe|shdochp.exe|shdocsvc.exe|shell.exe|shell386.exe|shnlog.exe|setup.dat|setup2.exe|services32.exe|smartdrv.exe|Smart Antivirus-2009.exe|SmartAntivirus2009.exe|SmitFraudFixTool.exe|socks.exe|split.exe|split1.exe|split2.exe|spoolvs.exe|Spykiller.exe|spoolsrv32.exe|spwoqbmv.exe|sprmvr.exe|spyaxe.exe|SpyCrush.exe|SpyCrush 3.1.exe|SpyDawn.exe|spyguard.exe|spyguard_monitor.exe|SpyFalcon.exe|Spy-Heal.exe|SpyHeal.exe|SpyHeals.exe|SpyLocked.exe|SpyLocked 3.6.exe|SpyLocked 3.7.exe|SpyLocked 3.9.exe|SpyLocked 4.0.exe|SpyLocked 4.1.exe|SpyLocked 4.3.exe|SpyMarshal.exe|spysheriff.exe|Spy-Locked.exe|Spy-Quake2.exe|spysoldier.exe|spywareguard.exe|spywareknight.exe|SpywareLock.exe|SpywareLocked.exe|SpywareLocked 3.5.exe|SpywareQuake.exe|Spyware-Quake.exe|SpywareRemover.exe|spywarestrike.exe|Spyware Soft Stop.exe|srcss.exe|sumsw32.exe|susp.exe|svchop.exe|svchosts.exe|svcnt.exe|svcnt32.exe|svchost_32.exe|svhjdsah.exe|sysabmpmfr.exe|sysahbecjh.exe|sysatjsicj.exe|sysavxjgdu.exe|sysawechod.exe|sysrc32.exe|systemguard.exe|svchostw.exe|svwhost.exe|sware.exe|symsvcsa.exe|SYS32DLL.exe|SYSDLL.exe|sysbho.exe|sysen.exe|sysguard.exe|sysguard_s.exe|sysinit32.exe|sysinit32z.exe|sysjv32.exe|sysldr32.exe|sysqyzwud.exe|sysscpmqn.exe|syssngbeh.exe|systeminit.exe|sysutrnez.exe|syszweuas.exe|sysmonms.exe|sysockeu.exe|sysodkcs.exe|sysokuaw.exe|syst.exe|System32fab.exe|sysvcs.exe|sysvx.exe|sysvx_.exe|sywsvcs.exe|taras.exe|tcpipmon.exe|tcpservice2.exe|tctool.exe|temp.000.exe|tetriz3.exe|TheMatrixHasYou.exe|TheSpyBot.exe|ticads.exe|timessquare.exe|tipguard.exe|titanshield.exe|tool1.exe|tool2.exe|tool3.exe|tool4.exe|tool5.exe|toolbar.exe|TotalProtect2009.exe|tmp0.exe|tmp1.exe|tmp2.exe|tpopup.exe|tp_starter.exe|truetype.exe|TrustCleaner.exe|trustinbar.exe|TrustInPopups.exe|tse.exe|uav.exe|uninst.exe|Uninstall.exe|uninstDsk|uninstIU.exe|UnVirex.exe|updchk.exe|url.exe|user32.exe|userload.exe|users32.exe|VCClient.exe|VCMain.exe|vav.exe|vb.exe|VIE2.exe|VIE3.exe|VIE4.exe|VIE5.exe|VIEA.exe|VirusBlast.exe|Virus-Burst.exe|VirusBurst.exe|VirusBurster.exe|VirusBursters.exe|virus-bursters.exe|VirusHeat 3.9.exe|VirusHeat 4.3.exe|VirusHeat 4.4.exe|VirRL2009.exe|ViRsLab.exe|VirusProtect 3.8.exe|VirusProtect 3.9.exe|VirusProtectPro 3.3.exe|VirusProtectPro 3.4.exe|VirusProtectPro 3.5.exe|VirusProtectPro 3.6.exe|VirusProtectPro 3.7.exe|VirusRay 3.8.exe|VirusResponseLab2009.exe|virusrl2009.exe|VirusTriggerBin.exe|VResLab.exe|vrl32.exe|vrm2008.exe|VShield.exe|vxddsk.exe|w8673492.exe|wbeCheck.exe|wbeInst$.exe|wcm.exe|wcs.exe|wcu.exe|wdscan.exe|weather.exe|web.exe|win64.exe|winagent.exe|WinAvX.exe|WinAvXX.exe|wincrt.exe|windef.exe|windesktop.exe|windupdates.exe|WinHound.exe|WiniBlueSoft.exe|wininet.exe|winldra.exe|winmuse.exe|winnook.exe|winsrv32.exe|winstall.exe|winsysupd.exe|winsysban.exe|winsysban8.exe|winntify.exe|widupdate.exe|winupdate.exe|winter.exe|wml.exe|wmptray.exe|wn0008.exe|wcm.exe|wcs.exe|wp.exe|wsc32x.exe|wsremover.exe|wupdmgr.exe|wupeng.exe|wxvgsdbq.exe|xadbrk.exe|xadbrk_.exe|xbaqktfv.exe|xbqmfsed.exe|xcbhwuq.exe|xewuaqj.exe|xhbxcnv.exe|xmpstean.exe|XPA.exe|xpdeluxe.exe|xpassgenerator.exe|xpassmanager.exe|xppolice.exe|XPSecurityCenter.exe|xpupdate.exe|xpuupdate.exe|xxxvideo.exe|xxx.exe|yaemu.exe|YUR1.exe|YUR2.exe|YUR3.exe|YUR4.exe|YUR5.exe|YURA.exe|z11.exe|z12.exe|z13.exe|z14.exe|z15.exe|z16.exe|zloader3.exe|zysalwhkkw.exe|zysaoxcjiy.exe|zysapghucv.exe|zysaxyczld.exe

2. AutoRuns Prune has been COMPLETELY OVERHAULED

It is now MUCH more effective and FASTER. It can also be reberted by dragging the automatically generated .acd file onto the AutoClean executable.

3. Also... Try running it with the /simple parameter...

Comments?

Edit: Oops... The source is now up.

Edited April 6, 2010 by NerdFencer

[LzY]

Thank you ,It's very great tool !

[navajow]

I absolutely love the program. I was in the middle of writing something similar for my job but no use reinventing the wheel right?

I got a quick problem however. When I was running v2.3, Vipre hungup and I had to force quit the script. Now when I run it (v2.4 included), a error message appears

Error: Line 66 (File "...\AutoClean 2.4 x32.exe"
Error: Variable must be of type "Object".

When I ran the source through Scite, it hung on this message

>Running:(3.3.4.0):C:\Program Files\AutoIt3\autoit3.exe "C:\Documents and Settings\dgrint\My Documents\Downloads\AutoClean v2.4 SRC\Src\AutoClean.au3"    
C:\Documents and Settings\dgrint\My Documents\Downloads\AutoClean v2.4 SRC\Src\Lang.au3 (35) : ==> Variable must be of type "Object".:
$oLang.Add("ProgName","Automatic System Cleaner v2.4")
$oLang^ ERROR

If you could help me out, it would be awesome. I would love to use this program on our servers that have been running for 10+ yrs without any maintenance.

[NerdFencer]

@lzy

Thanks

@navajow

I think I know whats wrong.

At the top of Lang.au3, change...

#include "Logging.au3"

Global $oLang = ObjCreate("Scripting.Dictionary")

Func SelectLanguage($lang)

to

#include "Logging.au3"
#include "Services.au3"

_SvcSetStartMode('winmgmt','Automatic')
_SvcStart('winmgmt')
Global $oLang = ObjCreate("Scripting.Dictionary")

Func SelectLanguage($lang)
    If Not(IsObj($oLang)) Then Return

Edit: Also Add

If Not(IsObj($oLang)) Then Return ""

to the top of Func GetLang($item)

Recompile and try again.

Edited April 9, 2010 by NerdFencer

[onestcoder]

@lzy

Thanks

@navajow

I think I know whats wrong.

At the top of Lang.au3, change...

#include "Logging.au3"

Global $oLang = ObjCreate("Scripting.Dictionary")

Func SelectLanguage($lang)

to

#include "Logging.au3"
#include "Services.au3"

_SvcSetStartMode('winmgmt','Automatic')
_SvcStart('winmgmt')
Global $oLang = ObjCreate("Scripting.Dictionary")

Func SelectLanguage($lang)
    If Not(IsObj($oLang)) Then Return

Edit: Also Add

If Not(IsObj($oLang)) Then Return ""

to the top of Func GetLang($item)

Recompile and try again.

NOPE this didn't fix the problem for me. I'm having the same problem as navajow

[JRowe]

What happened is subtle. You should use System Restore to a point earlier than your most recent restore point (preferably more than a day prior to your run of AutoClean.)

The help & support service, along with several system objects lost their registry references somehow (I'm not exactly sure what happened, or why.)

I just fixed it on my netbook... perhaps use of 2.4 should be avoided until we find out more? Reversing via AutoClean is prevented if the process is interrupted, for whatever reason, because objects the program uses (scripting dictionary,etc) end up losing their registry settings.) Recompilation won't affect anything on disrupted systems because of that.

[NerdFencer]

@JRowe

How did you figure that out?

Specifically what objects lost their references in addition to help and support?

Help and Support has no correlation to WMI(which creates the scripting objects) that I know about.

Here is a link to a .reg file that should restore the help and support service

http://www.kellys-korner-xp.com/regs_edits/helpnsupport.reg

@navajow

@onestcoder

Just realized that that 'fix' I sent to you wont work because of a couple variables that are not created by the time the _svc calls are made.

I have uploaded 2 replacement files that fix that problem.

@all

It now uses Scripting.Dictionary to store language items. Thats the only major change. I don't see anything different between my use of that object and any other uses I have seen of it. Maybe something was previously wrong with the scripting.dictionary object, and AutoClean's attempted use highlighted the problem or exacerbated it.

I'm not entirely certain that AutoClean is the root cause. If it were, some piece of code that runs before the Execute button is pressed would have to touch that area of the system (otherwise navajow would reach the GUI), but there is no code fitting that profile. The only piece that comes close is the attempted initialization of scripting.dictionary, which should not cause any problem. Whether or not AutoClean caused the registry problem, this has highlighted a large problem in using scripting.dictionary for the language elements in AutoClean, and I will remove its use in the next release.

AutoClean.au3

Lang.au3

Edited April 9, 2010 by NerdFencer

[JRowe]

I ran autoclean, and my power saving settings caused a hibernation some 15 minutes into the process. Upon restarting, the program hung, so I had to restart. I then noticed that my automatic updates settings had changed and had reverted to default automatic settings. From there, I tried to open Security Center, which was disabled because the Help and Support service was disabled.

After a little research, I found that I couldn't restart Help and Support, and because the hang occurred right in the middle of the RegSeeker run, I figured that the registry had somehow been borked. AutoClean began to display the "line 66" error at that point. Recompiling didn't work, nor did recompiling with the fixes you indicated. Undoing the registry settings via RegSeeker did nothing. The AutoClean reversal was unavailable due to the scripting dictionary fail.

I then did a system restore to the point that AutoClean had created, which did not solve the problem. I restored to my next most recent point, from January, and everything was fixed. My conclusion was that the Help and Support service was somehow involved, however, it's not necessarily the case. It's probably just an issue parallel to the one causing the scripting dictionary to fail.

I think an option to make everything visible, instead of running it all hidden would be advisable, so that we aren't dependent on the tray notifications in the case something goes wrong. This may prove to be a tedious undertaking, in which case, don't bother... but if it's easy to change, then I'd vote for that option.

BTW, I want to clarify to users: don't stop using this program. It's a great piece of work, and the few bumps a couple of us are hitting aren't any reason to be leery or wary of this software. It's still one of the best automated optimizer and recovery compilations I've ever seen. It is certainly the best such tool that you get for free.

[Alfonzo]

AutoClean may make your computer to clean. It does its job very well and can save you tons of time when doing virus removal and computer cleanup.

First time I ran autoclean it made it all the way through and restarted my computer. When it was time for me to login I got stuck in a infinite login--->logoff loop.

This caused me to repair Windows but before I did that I loaded up a boot disc and ran "hijack this" and what I saw in the log was that I was missing a majority of my dll files for 3rd party programs and important startup files. not sure which program did it but you may want to add an option to ask the user what he wants deleted after each program produces it results

Other than that this was a great program and will be using it more once I run it a few more times in test environments

[NerdFencer]

The only component that touches 3'rd party DLLs is RegSeeker

I am considering swapping this out for another registry cleaner, or possibly writing my own.

What startups did it remove that you consider important?

[JRowe]

The CCleaner registry cleaner is wonderful, and you'd be able to skip a download. They packed a lot of functionality into that tool.

[NerdFencer]

Only problem is that I can't find command line options to do a registry cleaning in CCleaner.

[storme]

Only problem is that I can't find command line options to do a registry cleaning in CCleaner.

There is none. The Author refuses to put them in as he considers Registry cleaning to be dangerous and should only be done manually.

You could aways do some button clicking.

Edited April 12, 2010 by storme

[NerdFencer]

After reading a little bit more literature on registry cleaning, I believe this to be the the feature causing people's problems, and will be removing it in the next version all together. According to what I have read (from several sources), registry cleaning does little for performance and is riskier than it is worth. The riskiness is certainly evidenced by navajow, onestcoder, and Jrowe.

On the plus side, I will be improving the effectiveness of the CCleaner scan by including a custom winapp2.ini, which I have modified from the one available on the CCleaner forum.

[JRowe]

Good plan. Thanks for the work you're putting in on this. It is very much appreciated.

As to the registry cleaning, I agree. It's usually just a matter of 20 seconds or so using CCleaner, and it's got a backup feature for any and all changes. For the amount of work it'd require on your part to include something in, it's probably not worth it. Just point people to regseeker or CCleaner in your docs.

[NerdFencer]

This coming weekend I will attempt to release a version that fixes all known bugs. After that, I must pause development until May 11. On June 15, I will release the last major version update in the 2.x line (there will most likely be some minor updates after this, but nothing ground-breaking). In august, I hope to unveil version 3.0, which will be a complete rewrite of AutoClean with MANY new features and a drastic performance increase.

[NerdFencer]

Can someone that had the line 66 error please post some way that their computer was messed up (if you know).

I am trying to replicate the problem to fix it.

[FinalVersion]

this disabled my volume keys on my keyboard