Another desto.exe problem - please help..

*sigh*

This one failed too. I double-clicked it to run it and a black window popped up instantly and disappeared just as quickly just like it does for every other .exe I try to open. I tried pressing any key very quickly as it popped up like you said, but it didn't do anything. No logs were created. It reacted just like everything else..

Hello.
Rename exehelper from .com to .scr and then try running it, let me know what happens.

Ha! That worked! Got a log.

09
Build 20090923
Run at 07:21:47 on 09/24/09
Now searching...
Checking for numerical processes...
Checking for bad processes...
Checking for bad files...
Found file C:\WINDOWS\system32\desot.exe
Deleting file C:\WINDOWS\system32\desot.exe
Found file C:\WINDOWS\system32\desote.exe
Deleting file C:\WINDOWS\system32\desote.exe
Found file C:\WINDOWS\svchast.exe
Deleting file C:\WINDOWS\svchast.exe
Error deleting C:\WINDOWS\svchast.exe
Found file C:\WINDOWS\system32\dddesot.dll
Deleting file C:\WINDOWS\system32\dddesot.dll
Found file C:\WINDOWS\ppp3.dat
Deleting file C:\WINDOWS\ppp3.dat
Found file C:\WINDOWS\ppp4.dat
Deleting file C:\WINDOWS\ppp4.dat
Found file C:\WINDOWS\system32\sysnet.dat
Deleting file C:\WINDOWS\system32\sysnet.dat
Found file C:\WINDOWS\system32\sonhelp.htm
Deleting file C:\WINDOWS\system32\sonhelp.htm
Found file C:\WINDOWS\system32\winhelper.dll
Deleting file C:\WINDOWS\system32\winhelper.dll
Found file C:\WINDOWS\system32\critical_warning.html
Deleting file C:\WINDOWS\system32\critical_warning.html
Found file C:\WINDOWS\system32\logon.exe
Deleting file C:\WINDOWS\system32\logon.exe
Checking for bad registry entries...
Removing HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\Advanced Virus Remover
Resetting filetype association for .exe
Resetting filetype association for .com
Resetting userinit and shell values...
Resetting policies...
--Finished--

Yes! It's actually all fixed from that! Thanks so much! I'm going to run Malwarebytes to find any leftover stuff and I'll post again if the problem arises again. That exeHelper fixed the problem quite easily.

Nice one. Run MBAM and post the log when you can.