This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

How do you remove a spyware or virus WINDEFRAG 1816328.exe

  • 2 biyano
  • 121 eza na bankokoso oyo
  • 1 view
  • Eyano yasuka ya sillymoy

dadof3
dadof3
more options

I was looking for some information on the internet today and my computer had a popup that read : You are running very low disk space on local disk (C:) and also a Critical error Windosw can't find hard disk space Hard drive error....then this pop up came up after it rebooted that reads WinDefrag with a file that reads 1816328.exe

I was looking for some information on the internet today and my computer had a popup that read : You are running very low disk space on local disk (C:) and also a Critical error Windosw can't find hard disk space Hard drive error....then this pop up came up after it rebooted that reads WinDefrag with a file that reads 1816328.exe

All Replies (2)

abo35
abo35
more options

Hello,

1 - open process explorer (CTRL-ALT-SUPPR) 2- kill 1816328.exe process 3 - open directory : C:\Documents and Settings\XXX\Local Settings\Temp 4 - purge that directory. Some files will be locked by the malware 5 - kill explorer.exe process 6 - restart explorer.exe 7 - delete the files which were locked 8- open regedit 9- search for occurence of "1816328" (or whatever that number is) 10- delete entries which refers to that program

It works for me...

Bye

sillymoy
sillymoy
more options

This blog has a removal guide: http://deletemalware.blogspot.com/2010/11/win-defrag-removal-instructions.html

Safe mode and system restore did the trick for some users. You should try too.