More information
How the Microsoft Malicious Software Removal Tool differs from an antivirus product
The Microsoft Malicious Software Removal Tool does not replace an antivirus product. It is strictly a post-infection removal tool. Therefore, we strongly recommend that you install and use an up-to-date antivirus product.
The Microsoft Malicious Software Removal Tool differs from an antivirus product in three key ways:
Note The Microsoft Malicious Software Removal Tool focuses on the detection and removal of malicious software such as viruses, worms, and Trojan horses only. It does not remove spyware. However, you can use Microsoft Security Essentials to detect and remove spyware. You do not have to disable or remove your antivirus program when you install the Microsoft Malicious Software Removal Tool. However, if prevalent, malicious software has infected your computer, the antivirus program may detect this malicious software and may prevent the removal tool from removing it when the removal tool runs. In this case, you can use your antivirus program to remove the malicious software.
Because the Microsoft Malicious Software Removal Tool does not contain a virus or a worm, the removal tool alone should not trigger your antivirus program. However, if malicious software infected the computer before you installed an up-to-date antivirus program, your antivirus program may not detect this malicious software until the tool tries to remove it.
The Microsoft Malicious Software Removal Tool differs from an antivirus product in three key ways:
- The tool removes malicious software from an already-infected computer. Antivirus products block malicious software from running on a computer. It is significantly more desirable to block malicious software from running on a computer than to remove it after infection.
- The tool removes only specific prevalent malicious software. Specific prevalent malicious software is a small subset of all the malicious software that exists today.
- The tool focuses on the detection and removal of active malicious software. Active malicious software is malicious software that is currently running on the computer. The tool cannot remove malicious software that is not running. However, an antivirus product can perform this task.
Note The Microsoft Malicious Software Removal Tool focuses on the detection and removal of malicious software such as viruses, worms, and Trojan horses only. It does not remove spyware. However, you can use Microsoft Security Essentials to detect and remove spyware. You do not have to disable or remove your antivirus program when you install the Microsoft Malicious Software Removal Tool. However, if prevalent, malicious software has infected your computer, the antivirus program may detect this malicious software and may prevent the removal tool from removing it when the removal tool runs. In this case, you can use your antivirus program to remove the malicious software.
Because the Microsoft Malicious Software Removal Tool does not contain a virus or a worm, the removal tool alone should not trigger your antivirus program. However, if malicious software infected the computer before you installed an up-to-date antivirus program, your antivirus program may not detect this malicious software until the tool tries to remove it.
How to download and run the Microsoft Malicious Software Removal Tool
You can download and run the Microsoft Malicious Software Removal Tool if your computer is running Windows 10, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista, Windows Server 2003, or Windows XP.
Note You cannot download and run the tool if you are running Microsoft Windows 98, Windows Millennium Edition, or Microsoft Windows NT 4.0.
The easiest way to download and run the tool is to turn on Automatic Updates. Turning on Automatic Updates guarantees that you receive the tool automatically every month. If you have Automatic Updates turned on, you have already been receiving new versions of this tool monthly. The tool runs in quiet mode unless it finds an infection. If you have not been notified of an infection, no malicious software has been found that needs your attention.
Note If your computer is running Windows XP Service Pack 2 (SP2), Automatic Updates is turned on by default.
Are you unsure about whether Automatic Updates is turned on? To have us turn on Automatic Updates for you, go to the "Fix it for me" section. If you would rather turn on Automatic Updates yourself, go to the "Let me fix it myself" section.
Note This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.
Download the Malicious Software Removal Tool. You must accept the Microsoft Software License Terms. The license terms are only displayed for the first time that you access Automatic Updates.
Note After you accept the one-time license terms, you can receive future versions of the Malicious Software Removal Tool without being logged on to the computer as an administrator.
Note You cannot download and run the tool if you are running Microsoft Windows 98, Windows Millennium Edition, or Microsoft Windows NT 4.0.
The easiest way to download and run the tool is to turn on Automatic Updates. Turning on Automatic Updates guarantees that you receive the tool automatically every month. If you have Automatic Updates turned on, you have already been receiving new versions of this tool monthly. The tool runs in quiet mode unless it finds an infection. If you have not been notified of an infection, no malicious software has been found that needs your attention.
Note If your computer is running Windows XP Service Pack 2 (SP2), Automatic Updates is turned on by default.
Are you unsure about whether Automatic Updates is turned on? To have us turn on Automatic Updates for you, go to the "Fix it for me" section. If you would rather turn on Automatic Updates yourself, go to the "Let me fix it myself" section.
Fix it for me
To fix this problem automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.| Turn Automatic Updates on | Turn Automatic Updates off |
|---|---|
Note This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.
Let me fix it myself
To turn on Automatic Updates yourself, follow the steps in the following table for the operating system that your computer is running.| If your computer is running | Follow these steps |
|---|---|
| Windows 7 |
|
| Windows Vista |
|
| Windows XP, or Windows Server 2003 |
|
, point to All Programs, and then click Windows Update. Video: How to turn on Automatic Updates in Windows 7
Download the Malicious Software Removal Tool. You must accept the Microsoft Software License Terms. The license terms are only displayed for the first time that you access Automatic Updates.
Note After you accept the one-time license terms, you can receive future versions of the Malicious Software Removal Tool without being logged on to the computer as an administrator.
When the Malicious Software Removal Tool detects malicious software
The Malicious Software Removal Tool runs in quiet mode. If it detects malicious software on your computer, the next time that you log on to your computer as a computer administrator, a balloon will appear in the notification area to make you aware of the detection.
You can clean specific files or all the infected files that the tool finds. Be aware that some data loss is possible during this process. Also, be aware that the tool may be unable to restore some files to the original, pre-infection state.
The removal tool may request that you restart your computer to complete the removal of some malicious software, or it may prompt you to perform manual steps to complete the removal of the malicious software. To complete the removal, you should use an up-to-date antivirus product.
Performing a full scan
If the tool finds malicious software, you may be prompted to perform a full scan. We recommend that you perform this scan. A full scan performs a quick scan and then a full scan of the computer, regardless of whether malicious software is found during the quick scan. This scan can take several hours to complete because it will scan all fixed and removable drives. However, mapped network drives are not scanned.Removing malicious files
If malicious software has modified (infected) files on your computer, the tool prompts you to remove the malicious software from those files. If the malicious software modified your browser settings, your homepage may be changed automatically to a page that gives you directions on how to restore these settings.You can clean specific files or all the infected files that the tool finds. Be aware that some data loss is possible during this process. Also, be aware that the tool may be unable to restore some files to the original, pre-infection state.
The removal tool may request that you restart your computer to complete the removal of some malicious software, or it may prompt you to perform manual steps to complete the removal of the malicious software. To complete the removal, you should use an up-to-date antivirus product.
Reporting infection information to Microsoft
The Malicious Software Removal Tool will send basic information to Microsoft if the tool detects malicious software or finds an error. This information will be used for tracking virus prevalence. No identifiable personal information that is related to you or to the computer is sent together with this report.How to remove the Malicious Software Removal Tool
The Malicious Software Removal Tool does not use an installer. Typically, when you run the Malicious Software Removal Tool, it creates a randomly named temporary directory on the root drive of the computer. This directory contains several files, and it includes the Mrtstub.exe file. Most of the time, this folder is automatically deleted after the tool finishes running or after the next time that you start the computer. However, this folder may not always be automatically deleted. In these cases, you can manually delete this folder, and this has no adverse effect on the computer.
How to receive support
Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security CenterSecurity solutions for IT professionals: TechNet Security Troubleshooting and Support
Help installing updates: Support for Microsoft Update
Local support according to your country: International Support.
More information for advanced users
Microsoft Download Center
Deploying the Malicious Software Removal Tool in an enterprise environment
Prerequisites for running the Malicious Software Removal Tool
Support for command-line switches
Usage and release information
Reporting component
Possible scanning results
Frequently asked questions about the Malicious Software Removal Tool
This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact support. For more information about how to contact Microsoft support, go to the Microsoft Support website.
Deploying the Malicious Software Removal Tool in an enterprise environment
Prerequisites for running the Malicious Software Removal Tool
Support for command-line switches
Usage and release information
Reporting component
Possible scanning results
Frequently asked questions about the Malicious Software Removal Tool
This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact support. For more information about how to contact Microsoft support, go to the Microsoft Support website.
Microsoft Download Center
You can manually download the Malicious Software Removal Tool from the Microsoft Download Center. The following files are available for download from the Microsoft Download Center:For 32-bit x86-based systems:
For 64-bit x64-based systems:
Release Date: June 14, 2016.
For more information about how to download Microsoft support files, go to the following article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Deploying the Malicious Software Removal Tool in an enterprise environment
If you are an IT administrator who wants more information about how to deploy the tool in an enterprise environment, go to the following article in the Microsoft Knowledge Base: This article includes information about Microsoft Systems Management Server (SMS), Microsoft Software Update Services (SUS), and Microsoft Baseline Security Analyzer (MBSA).Prerequisites for running the Malicious Software Removal Tool
Except where noted, the information in this section applies to all the ways that you can download and run the Malicious Software Removal Tool:- Microsoft Update
- Windows Update
- Automatic Updates
- The Microsoft Download Center
- The Malicious Software Removal Tool website on Microsoft.com
- The computer must be running Windows 7, Windows Vista, Windows Server 2003, or Windows XP.
- You must log on to the computer by using an account that is a member of the Administrators group. If your logon account does not have the required permissions, the tool exits. If the tool is not being run in quiet mode, it displays a dialog box that describes the failure.
- If the tool is more than 60 days out-of-date, the tool displays a dialog box that recommends that you download the latest version of the tool.
Support for command-line switches
The Malicious Software Removal Tool supports four command-line switches.| Switch | Purpose |
|---|---|
| /Q or /quiet | Uses quiet mode. This option suppresses the user interface of the tool. |
| /? | Displays a dialog box that lists the command-line switches. |
| /N | Runs in detect-only mode. In this mode, malicious software will be reported to the user, but it will not be removed. |
| /F | Forces an extended scan of the computer. |
| /F:Y | Forces an extended scan of the computer and automatically cleans any infections that are found. |
Usage and release information
When you download the tool from Microsoft Update or from Automatic Updates, and no malicious software is detected on the computer, the tool will run in quiet mode next time. If malicious software is detected on the computer, the next time that an administrator logs on to the computer, a balloon will appear in the notification area to notify you of the detection. For more information about the detection, click the balloon.When you download the tool from the Microsoft Download Center, the tool displays a user interface when it runs. However, if you supply the /Q command-line switch, it runs in quiet mode.
Release information
The Malicious Software Removal Tool is released on the second Tuesday of every month. Each release of the tool helps detect and remove current, prevalent malicious software. This malicious software includes viruses, worms, and Trojan horses. Microsoft uses several metrics to determine the prevalence of a malicious software family and the damage that can be associated with it.The following table lists the malicious software that the tool can remove. The tool can also remove any known variants at the time of release. The table also lists the version of the tool that first included detection and removal for the malicious software family.
This Microsoft Knowledge Base article will be updated with information for each monthly release so that the number of the relevant article remains the same. The name of the file will be changed to reflect the tool version. For example, the file name of the January 2005 version is Windows-KB890830-ENU.exe, and the file name of the February 2005 version is Windows-KB890830-V1.1-ENU.exe.
| Malicious software family | Tool version date and number | Current severity rating |
|---|---|---|
| Win32/Berbew | January 2005 (1.0) | Low |
| Win32/Doomjuice | January 2005 (1.0) | Low |
| Win32/Gaobot | January 2005 (1.0) | Moderate |
| Win32/MSBlast | January 2005 (1.0) | Low |
| Win32/Mydoom | January 2005 (1.0) | Low |
| Win32/Nachi | January 2005 (1.0) | Low |
| Win32/Sasser | January 2005 (1.0) | Low |
| Win32/Zindos | January 2005 (1.0) | Low |
| Win32/Korgo | February 2005 (1.1) | Low |
| Win32/Netsky | February 2005 (1.1) | Moderate |
| Win32/Randex | February 2005 (1.1) | Low |
| Win32/Zafi | February 2005 (1.1) | Low |
| Win32/Bagle | March 2005 (1.2) | Moderate |
| Win32/Bropia | March 2005 (1.2) | Low |
| Win32/Goweh | March 2005 (1.2) | Low |
| Win32/Sober | March 2005 (1.2) | Moderate |
| Win32/Sobig | March 2005 (1.2) | Low |
| Win32/Hackdef** | April 2005 (1.3) | Moderate |
| Win32/Mimail | April 2005 (1.3) | Low |
| Win32/Rbot | April 2005 (1.3) | Moderate |
| Win32/Sdbot | May 2005 (1.4) | Moderate |
| WinNT/Ispro | May 2005 (1.4) | Low |
| WinNT/FURootkit | May 2005 (1.4) | Moderate |
| Win32/Kelvir | June 2005 (1.5) | Low |
| Win32/Lovgate | June 2005 (1.5) | Low |
| Win32/Mytob | June 2005 (1.5) | Low |
| Win32/Spybot | June 2005 (1.5) | Moderate |
| Win32/Hacty | July 2005 (1.6) | Low |
| Win32/Optix | July 2005 (1.6) | Low |
| Win32/Optixpro | July 2005 (1.6) | Low |
| Win32/Purstiu | July 2005 (1.6) | Low |
| Win32/Wootbot | July 2005 (1.6) | Low |
| Win32/Bagz | August 2005 (1.7) | Low |
| Win32/Dumaru | August 2005 (1.7) | Low |
| Win32/Spyboter | August 2005 (1.7) | Low |
| Win32/Zotob.A | August 2005 A (1.7.1) | Low |
| Win32/Zotob.B | August 2005 A (1.7.1) | Low |
| Win32/Zotob.C | August 2005 A (1.7.1) | Low |
| Win32/Zotob.D | August 2005 A (1.7.1) | Low |
| Win32/Zotob.E | August 2005 A (1.7.1) | Low |
| Win32/Bobax.O | August 2005 A (1.7.1) | Moderate |
| Win32/Esbot.A | August 2005 A (1.7.1) | Low |
| Win32/Rbot.MA | August 2005 A (1.7.1) | Low |
| Win32/Rbot.MB | August 2005 A (1.7.1) | Low |
| Win32/Rbot.MC | August 2005 A (1.7.1) | Low |
| Win32/Bobax | September 2005 (1.8) | Moderate |
| Win32/Esbot | September 2005 (1.8) | Low |
| Win32/Gael | September 2005 (1.8) | Moderate |
| Win32/Yaha | September 2005 (1.8) | Low |
| Win32/Zotob | September 2005 (1.8) | Low |
| Win32/Antinny | October 2005 (1.9) | Moderate |
| Win32/Gibe | October 2005 (1.9) | Low |
| Win32/Mywife | October 2005 (1.9) | Low |
| Win32/Wukill | October 2005 (1.9) | Moderate |
| Win32/Bugbear | November 2005 (1.10) | Low |
| Win32/Codbot | November 2005 (1.10) | Low |
| Win32/Mabutu | November 2005 (1.10) | Low |
| Win32/Opaserv | November 2005 (1.10) | Low |
| Win32/Swen | November 2005 (1.10) | Low |
| Win32/IRCBot | December 2005 (1.11) | Moderate |
| Win32/Ryknos | December 2005 (1.11) | Low |
| WinNT/F4IRootkit | December 2005 (1.11) | Moderate |
| Win32/Bofra | January 2006 (1.12) | Low |
| Win32/Maslan | January 2006 (1.12) | Low |
| Win32/Parite | January 2006 (1.12) | Moderate |
| Win32/Alcan | February 2006 (1.13) | Moderate |
| Win32/Badtrans | February 2006 (1.13) | Low |
| Win32/Eyeveg | February 2006 (1.13) | Low |
| Win32/Magistr | February 2006 (1.13) | Low |
| Win32/Atak | March 2006 (1.14) | Low |
| Win32/Torvil | March 2006 (1.14) | Low |
| Win32/Zlob | March 2006 (1.14) | Moderate |
| Win32/Locksky | April 2006 (1.15) | Moderate |
| Win32/Reatle | April 2006 (1.15) | Low |
| Win32/Valla | April 2006 (1.15) | Low |
| Win32/Evaman | May 2006 (1.16) | Low |
| Win32/Ganda | May 2006 (1.16) | Low |
| Win32/Plexus | May 2006 (1.16) | Low |
| Win32/Cissi | June 2006 (1.17) | Low |
| Win32/Fizzer | June 2006 (1.17) | Low |
| Win32/Alemod | July 2006 (1.18) | Moderate |
| Win32/Chir | July 2006 (1.18) | Moderate |
| Win32/Hupigon | July 2006 (1.18) | Moderate |
| Win32/Nsag | July 2006 (1.18) | Low |
| Win32/Banker | August 2006 (1.19) | Moderate |
| Win32/Jeefo | August 2006 (1.19) | Moderate |
| Win32/Bancos | September 2006 (1.20) | Moderate |
| Win32/Sinowal | September 2006 (1.20) | Moderate |
| Win32/Harnig | October 2006 (1.21) | Low |
| Win32/Passalert | October 2006 (1.21) | Low |
| Win32/Tibs | October 2006 (1.21) | Moderate |
| Win32/Brontok | November 2006 (1.22) | Moderate |
| Win32/Beenut | December 2006 (1.23) | Low |
| Win32/Haxdoor | January 2007 (1.24) | Moderate |
| WinNT/Haxdoor | January 2007 (1.24) | Moderate |
| Win32/Stration | February 2007 (1.25) | Moderate |
| Win32/Mitglieder | February 2007 (1.25) | Low |
| Win32/Alureon | March 2007 (1.27) | Moderate |
| Win32/Funner | April 2007 (1.28) | Low |
| Win32/Renos | May 2007 (1.29) | Moderate |
| Win32/Allaple | June 2007 (1.30) | Moderate |
| Win32/Busky | July 2007 (1.31) | Moderate |
| Win32/Virut.A | August 2007 (1.32) | Moderate |
| Win32/Virut.B | August 2007 (1.32) | Moderate |
| Win32/Zonebac | August 2007 (1.32) | Moderate |
| Win32/Nuwar | September 2007 (1.33) | Moderate |
| Win32/RJump | October 2007 (1.34) | Moderate |
| Win32/ConHook | November 2007 (1.35) | Moderate |
| Win32/Fotomoto | December 2007 (1.36) | Moderate |
| Win32/Cutwail | January 2008 (1.37) | Moderate |
| Win32/Ldpinch | February 2008 (1.38) | Moderate |
| Win32/Virtumonde | March 2008 (1.39) | Moderate |
| Win32/Vundo | March 2008 (1.39) | Moderate |
| Win32/Newacc | March 2008 (1.39) | Moderate |
| Win32/Oderoor | May 2008 (1.41) | Moderate |
| Win32/Captiya | May 2008 (1.41) | Moderate |
| Win32/Corripio | June 2008 (1.42) | Moderate |
| Win32/Frethog | June 2008 (1.42) | Moderate |
| Win32/Taterf | June 2008 (1.42) | Moderate |
| Win32/Storark | June 2008 (1.42) | Moderate |
| Win32/Tilcun | June 2008 (1.42) | Moderate |
| Win32/Zuten | June 2008 (1.42) | Moderate |
| Win32/Ceekat | June 2008 (1.42) | Moderate |
| Win32/Lolyda | June 2008 (1.42) | Moderate |
| Win32/Horst | July 2008 (2.0) | Moderate |
| Win32/Matcash | August 2008 (2.1) | Moderate |
| Win32/Slenfbot | September 2008 (2.2) | Moderate |
| Win32/Rustock | October 2008 (2.3) | Moderate |
| Win32/FakeSecSen | November 2008 (2.4 ) | Moderate |
| Win32/Gimmiv | November 2008 (2.4) | Moderate |
| Win32/FakeXPA | December 2008 (2.5) | Moderate |
| Win32/Yektel | December 2008 (2.5) | Moderate |
| Win32/Banload | January 2009 (2.6) | Moderate |
| Win32/Conficker | January 2009 (2.6) | High |
| Win32/Srizbi | February 2009 (2.7 ) | Moderate |
| Win32/Koobface | March 2009 (2.8) | Moderate |
| Win32/Waledac | April 2009 (2.9) | Moderate |
| Win32/Winwebsec | May 2009 (2.10) | Moderate |
| Win32/InternetAntivirus | June 2009 (2.11) | Moderate |
| Win32/FakeSpypro | July 2009 (2.12) | Moderate |
| Win32/FakeRean | August 2009 (2.13) | Moderate |
| Win32/Bredolab | September 2009 (2.14) | Moderate |
| Win32/Daurso | September 2009 (2.14) | Moderate |
| Win32/FakeScanti | October 2009 (3.0) | Moderate |
| Win32/FakeVimes | November 2009 (3.1) | Moderate |
| Win32/PrivacyCenter | November 2009 (3.1) | Moderate |
| Win32/Hamweq | December 2009 (3.2) | Moderate |
| Win32/Rimecud | January 2010 (3.3) | Moderate |
| Win32/Pushbot | February 2010 (3.4) | Moderate |
| Win32/Helpud | March 2010 (3.5) | Moderate |
| Win32/Magania | April 2010 (3.6) | Moderate |
| Win32/Oficla | May 2010 (3.7) | Moderate |
| Win32/FakeInit | June 2010 (3.8) | Moderate |
| Win32/Bubnix | July 2010 (3.9) | Moderate |
| Win32/Stuxnet | August 2010 (3.10) | Moderate |
| Win32/CplLnk | August 2010 (3.10) | Moderate |
| Worm:Win32/Vobfus.gen!A | August 2010 (3.10) | Moderate |
| Worm:Win32/Vobfus.gen!B | August 2010 (3.10) | Moderate |
| Worm:Win32/Vobfus.gen!C | August 2010 (3.10) | Moderate |
| Worm:Win32/Vobfus!dll | August 2010 (3.10) | Moderate |
| Worm:Win32/Sality.AU | August 2010 (3.10) | Moderate |
| Virus:Win32/Sality.AU | August 2010 (3.10) | Moderate |
| Trojan:WinNT/Sality | August 2010 (3.10) | Moderate |
| Win32/FakeCog | September 2010 (3.11) | Moderate |
| Win32/Vobfus | September 2010 (3.11) | Moderate |
| Win32/Zbot | October 2010 (3.12) | Moderate |
| Win32/FakePAV | November 2010 (3.13) | Moderate |
| Worm:Win32/Sality.AT | November 2010 (3.13) | Moderate |
| Virus:Win32/Sality.AT | November 2010 (3.13) | Moderate |
| Win32/Qakbot | December 2010 (3.14) | Moderate |
| Win32/Lethic | January 2011 (3.15) | Moderate |
| Win32/Cycbot | February 2011 (3.16) | Moderate |
| Win32/Renocide | March 2011 (3.17) | Moderate |
| Win32/Afcore | April 2011 (3.18) | Moderate |
| Win32/Ramnit | May 2011 (3.19) | Moderate |
| Win32/Rorpian | June 2011 (3.20) | Moderate |
| Win32/Yimfoca | June 2011 (3.20) | Moderate |
| Win32/Nuqel | June 2011 (3.20) | Moderate |
| Win32/Tracur | July 2011 (3.21) | Moderate |
| Win32/Dursg | July 2011 (3.21) | Moderate |
| Win32/FakeSysdef | August 2011 (3.22) | Moderate |
| Win32/Hiloti | August 2011 (3.22) | Moderate |
| Win32/Bamital | September 2011 (4.0) | Moderate |
| Win32/Kelihos | September 2011 (4.0) | Moderate |
| Win32/EyeStye | October 2011 (4.1) | Moderate |
| Win32/Poison | October 2011 (4.1) | Moderate |
| Win32/Dofoil | November 2011 (4.2) | Moderate |
| Win32/Carberp | November 2011 (4.2) | Moderate |
| Win32/Cridex | November 2011 (4.2) | Moderate |
| Win32/Helompy | December 2011 (4.3) | Moderate |
| Win32/Sefnit | January 2012 (4.4) | Moderate |
| Win32/Pramro | February 2012 (4.5) | Moderate |
| Win32/Fareit | February 2012 (4.5) | Moderate |
| Win32/Dorkbot | March 2012 (4.6) | Moderate |
| Win32/Hioles | March 2012 (4.6) | Moderate |
| Win32/Yeltminky | March 2012 (4.6) | Moderate |
| Win32/Pluzoks.A | March 2012 (4.6) | Moderate |
| Win32/Claretore | April 2012 (4.7) | Moderate |
| Win32/Bocinex | April 2012 (4.7) | Moderate |
| Win32/Gamarue | April 2012 (4.7) | Moderate |
| Win32/Unruy | May 2012 (4.8) | Moderate |
| Win32/Dishigy | May 2012 (4.8) | Moderate |
| Win32/Cleaman | June 2012 (4.9) | Moderate |
| Win32/Kuluoz | June 2012 (4.9) | Moderate |
| Win32/Bafruz | August 2012 (4.11) | Severe |
| Win32/Matsnu | August 2012 (4.11) | Severe |
| Win32/Medfos | September 2012 (4.12) | Severe |
| Win32/Nitol | October 2012 (4.13) | Severe |
| Win32/OneScan | October 2012 (4.13) | Severe |
| Win32/Folstart | November 2012 (4.14) | Severe |
| Win32/Weelsof | November 2012 (4.14) | Severe |
| Win32/Phorpiex | November 2012 (4.14) | Severe |
| Win32/Phdet | December 2012 (4.15) | Severe |
| Win32/Ganelp | January 2013 (4.16) | Severe |
| Win32/Lefgroo | January 2013 (4.16) | Severe |
| Win32/Sirefef | February 2013 (4.17) | Severe |
| Win32/Wecykler | March 2013 (4.18) | Severe |
| Win32/Babonock | April 2013 (4.19) | Severe |
| Win32/Redyms | April 2013 (4.19) | Severe |
| Win32/Vesenlosow | April 2013 (4.19) | Severe |
| Win32/fakedef | May 2013 (4.20) | Severe |
| Win32/Vicenor | May 2013 (4.20) | Severe |
| Win32/Kexqoud | May 2013 (4.20) | Severe |
| Win32/Tupym | June 2013 (4.21) | Severe |
| Win32/Simda | September 2013 (5.4) | Severe |
| Win32/Shiotob | October 2013 (5.5) | Severe |
| Win32/Foidan | October 2013 (5.5) | Severe |
| Win32/Deminnix | November 2013 (5.6) | Severe |
| Win32/Napolar | November 2013 (5.6) | Severe |
| Win32/Rotbrow | December 2013 (5.7) | Severe |
| MSIL/Bladabindi | January 2014 (5.8) | Severe |
| VBS/Jenxcus | February 2014 (5.9) | Severe |
| Win32/Wysotot | March 2014 (5.10) | Severe |
| MSIL/Spacekito | March 2014 (5.10) | Severe |
| Win32/Ramdo | April 2014 (5.11) | Severe |
| Win32/Kilim | April 2014 (5.11) | Severe |
| Win32/Miuref | May 2014 (5.12) | Severe |
| Win32/Filcout | May 2014 (5.12) | Severe |
| Win32/Necurs | June 2014 (5.13) | Severe |
| Win32/Caphaw | July 2014 (5.14) | Severe |
| Win32/Bepush | July 2014 (5.14) | Severe |
| Win32/Lecpetex | August 2014 (5.15) | Severe |
| Win32/Zemot | September 2014 (5.16) | Severe |
| Win32/Hikiti | October 2014 (5.17) | Severe |
| Win32/Mdmbot | October 2014 (5.17) | Severe |
| Win32/Moudoor | October 2014 (5.17) | Severe |
| Win32/Plugx | October 2014 (5.17) | Severe |
| Win32/Sensode | October 2014 (5.17) | Severe |
| Win32/Derusbi | October 2014 (5.17) | Severe |
| Win32/Tofsee | November 2014 (5.18) | Severe |
| Win32/Winnti | November 2014 (5.18) | Severe |
| Win32/Zoxpng | November 2014 (5.18) | Severe |
| Win32/Emotet | January 2015 (5.20) | Severe |
| Win32/Dyzap | January 2015 (5.20) | Severe |
| Win32/Escad | February 2015 (5.21) | Severe |
| Win32/Jinupd | February 2015 (5.21) | Severe |
| Win32/NukeSped | February 2015 (5.21) | Severe |
| Win32/Alinaos | March 2015 (5.22) | Severe |
| Win32/CompromisedCert | March 2015 (5.22) | Severe |
| Win32/Saluchtra | April 2015 (5.23) | Severe |
| Win32/Unskal | April 2015 (5.23) | Severe |
| Win32/Dexter | April 2015 (5.23) | Severe |
| Win32/IeEnablerCby | April 2015 (5.23) | High |
| Win32/Gatak | June 2015 (5.25) | Severe |
| Win32/OnlineGames | June 2015 (5.25) | Severe |
| Win32/BrobanDel | June 2015 (5.25) | Severe |
| Win32/Bagopos | June 2015 (5.25) | Severe |
| Win32/Enterak | July 2015 (5.26) | Severe |
| Win32/Reveton | July 2015 (5.26) | Severe |
| Win32/Crowti | July 2015 (5.26) | Severe |
| Win32/Vawtrak | August 2015 (5.27) | Severe |
| Win32/Critroni | August 2015 (5.27) | Severe |
| Win32/Kasidet | August 2015 (5.27) | Severe |
| Win32/Teerac | September 2015 (5.28) | Severe |
| Win32/Tescrypt | October 2015 (5.29) | Severe |
| Win32/Blakamba | October 2015 (5.29) | Severe |
| Win32/Diplugem | October 2015 (5.29) | Severe |
| Win32/Joanap | October 2015 (5.29) | Severe |
| Win32/Escad | October 2015 (5.29) | Severe |
| Win32/Brambul | October 2015 (5.29) | Severe |
| Win32/Drixed | October 2015 (5.29) | Severe |
| Win32/Winsec | December 2015 (V 5.31) | Severe |
| Win32/Fynloski | March 2016 (V 5.34) | Severe |
| Win32/Vonteera | March 2016 (V 5.34) | High |
| Win32/Upatre | April 2016 (V 5.35) | Severe |
| Win32/Bedep | April 2016 (V 5.35) | Severe |
| Win32/Samas | April 2016 (V 5.35) | Severe |
| Win32/Kovter | May 2016 (V 5.36) | Severe |
| Win32/Locky | May 2016 (V 5.36) | Severe |
| Win32/Ursnif | June 2016 (V 5.37) | Severe |
** W32/Hackdef typically hides other potentially unwanted software on the computer. If the cleaner tool reports that W32/Hackdef was detected on the computer, we strongly recommend that you run a scan with up-to-date antivirus and antispyware programs (see http://www.microsoft.com/security/pc-security/spyware-prevent.aspx). If you want to view the software that W32/Hackdef was hiding, first open the log file for the cleaner tool (%Windir%\Debug\Mrt.log). Next, in the "Possible scanning results" section, find the line or lines that note the folder in which Win32/Hackdef was found. In that same folder, you should find the Win32/Hackdef configuration file that has the .ini file name extension. View this file to determine the software that Win32/Hackdef was hiding on the computer.
To scan for and remove more malicious software, use an up-to-date antivirus product. For more information, go to the following Microsoft Protect Your PC website: We maximize customer protection by regularly reviewing and prioritizing our signatures. Each month we add or remove detections as the threat landscape evolves.
Reporting component
The Malicious Software Removal Tool sends information to Microsoft if it detects malicious software or finds an error. The specific information that is sent to Microsoft consists of the following items:- The name of the malicious software that is detected
- The result of malicious software removal
- The operating system version
- The operating system locale
- The processor architecture
- The version number of the tool
- An indicator that notes whether the tool is being run by Microsoft Update, Windows Update, Automatic Updates, the Download Center, or from the website
- An anonymous GUID
- A cryptographic one-way hash (MD5) of the path and file name of each malicious software file that is removed from the computer
- The files that are suspected to be malicious software. The tool will identify the files for you.
- A cryptographic one-way hash (MD5) of any suspicious files that are detected.
Possible scanning results
After the tool runs, there are four main results that the removal tool can report to the user:- No infection was found.
- At least one infection was found and was removed.
- An infection was found but was not removed. This result will be displayed if suspicious files were found on the computer. To help remove these files, you should use an up-to-date antivirus product.
- An infection was found and was partially removed. To complete this removal, you should use an up-to-date antivirus product.
Frequently asked questions about the Malicious Software Removal Tool
- Q1: Is this tool digitally signed by Microsoft?
A1: Yes. - Q2: What kind of information does the log file contain?
A2: For information about the log file, go to the following Microsoft Knowledge Base article: - Q3: Can this tool be redistributed?
A3: Yes. Per the terms of this tool's license terms, the tool can be redistributed. However, make sure that you are redistributing the latest version of the tool. - Q4: How do I know that I'm using the latest version of the tool?
A4: If you are a Windows 7, Windows Vista, Windows XP, or Windows Server 2003 user, use Microsoft Update or the Microsoft Update Automatic Updates functionality to test whether you are using the latest version of the tool. If you have chosen not to use Microsoft Update, and you are a Windows 7, Windows Vista, Windows XP, or Windows Server 2003 Service Pack 1 (SP1) user, use Windows Update. Or, use the Windows Update Automatic Updates functionality to test whether you are using the latest version of the tool. Additionally, you can visit the Microsoft Download Center. Also, if the tool is more than 60 days out-of-date, the tool will remind you to look for a new version of the tool. - Q5: Will the Microsoft Knowledge Base article number of the tool change with each new version?
A5: No. The Microsoft Knowledge Base article number for the tool will remain as 890830 for future versions of the tool. The file name of the tool when it is downloaded from the Microsoft Download Center will change with each release to reflect the month and the year when that version of the tool was released. - Q6: Is there any way I can request that new malicious software be targeted in the tool?
A6: Currently, no. Malicious software that is targeted in the tool is based on metrics that track the prevalence and damage of malicious software. - Q7: Can I determine whether the tool has been run on a computer?
A7: Yes. By checking a registry key, you can determine whether the tool has been run on a computer and which version was the latest version that was used. For more information, go to the following article in the Microsoft Knowledge Base: - Q8: Why do not I see the tool on Microsoft Update, Windows Update, or Automatic Updates?
A8: Several scenarios may prevent you from the seeing the tool on Microsoft Update, Windows Update, or Automatic Updates:- Only Windows 7, Windows Vista, Windows XP, and Windows Server 2003 SP1 users are offered the tool on Windows Update or Automatic Updates.
- If you have already run the current version of the tool from Windows Update, Microsoft Update, Automatic Updates, or from either of the other two release mechanisms, it will not be reoffered on Windows Update or Automatic Updates.
- For Automatic Updates, the first time that you run the tool, you must be logged on as a member of the Administrators group to accept the license terms.
- Q9: How do Microsoft Update, Windows Update, and Automatic Updates determine who the tool is offered to?
A9: All Windows 7, Windows Vista, Windows XP, and Windows Server 2003 users are offered the tool if the following conditions are true:- The users are running the latest version of Microsoft Update or the Microsoft Update Automatic Updates feature.
- The users have not already run the current version of the tool.
- The users are not running Microsoft Update.
- The users are running the latest version of Windows Update or Windows Update Automatic Updates.
- The users have not already run the current version of the tool.
- Q10: When I look in the log file, it tells me that errors were found during the scan. How do I resolve the errors?
A10: For information about the errors, see Microsoft Knowledge Base article891717 How to troubleshoot an error when you run the Microsoft Windows Malicious Software Removal Tool - Q11: Will you rerelease the tool even if there are no new security bulletins for a particular month?
A11: Yes. Even if there are no new security bulletins for a particular month, the Malicious Software Removal Tool will be rereleased with detection and removal support for the latest prevalent malicious software. - Q12: How do I prevent this tool from being offered to me by using Microsoft Update, Windows Update, or Automatic Updates?
A12: When you are first offered the Malicious Software Removal Tool from Microsoft Update, Windows Update, or Automatic Updates, you can decline downloading and running the tool by declining the license terms. This decline can apply to only the current version of the tool or to both the current version of the tool and any future versions, depending on the options that you choose. If you have already accepted the license terms and would prefer not to install the tool through Windows Update, click to clear the check box that corresponds to the tool in the Windows Update UI. - Q13: After I run the tool from Microsoft Update, Windows Update, or Automatic Updates, where are the tool files stored? Can I rerun the tool?
A13: When it is downloaded from Microsoft Update or from Windows Update, the tool runs only one time each month. To manually run the tool multiple times a month, download the tool from the Download Center or by visiting the Microsoft Safety & Security Center website.
For an online scan of your system by using the Windows Live OneCare safety scanner, go to the Microsoft Safety Scanner website.- Q14: Can I run this tool on a Windows Embedded computer?
A14: Currently, the Malicious Software Removal Tool is not supported on a Windows Embedded computer. - Q15: Does running this tool require any security updates to be installed on the computer?
A15: No. Unlike most previous cleaner tools that were produced by Microsoft, the Malicious Software Removal tool requires no security update prerequisites. However, we strongly recommend that you install all critical updates before you use the tool, to help prevent reinfection by malicious software that takes advantage of security vulnerabilities. - Q16: Can I deploy this tool by using SUS or SMS? Is it compatible with MBSA?
A16: For information about how to deploy this tool, see Microsoft Knowledge Base article - Q17: Do I have to have the previous cleaner tools installed to run the Malicious Software Removal Tool?
A17: No. - Q18: Is there a newsgroup available to discuss this tool?
A18: Yes. You can use the microsoft.public.security.virus newsgroup. - Q19: Why does the "Windows File Protection" window appear when I run the tool?
A19: In some cases, when specific viruses are found on a system, the cleaner tool tries to repair infected Windows system files. Although this action removes the malicious software from these files, it may also trigger the Windows File Protection feature. If you see the Windows File Protection window, we strongly recommend that you follow the directions and insert your Microsoft Windows CD. This will restore the cleaned files to their original, pre-infection state. - Q20: Are localized versions of this tool available?
A20: Yes, the tool is available in 24 languages. Before the February 2006 release, each localized version of the tool was available as a separate download. Starting in February 2006, the tool is now offered as a multilingual download. Therefore, only one version of the tool is available, and the appropriate language appears based on the language of the current operating system. - Q21: I found the Mrtstub.exe file in a randomly named directory on my computer. Is the Mrtstub.exe file a legitimate component of the tool?
A21: The tool does use a file that is named Mrtstub.exe for certain operations. If you verify that the file is signed by Microsoft, the file is a legitimate component of the tool. - Q22: Can the MSRT run in safe mode?
A22: Yes. If you have run the MSRT before you start the computer to safe mode, you can access MSRT at %windir%\system32\mrt.exe. Double-click the mrt.exe file to run the MSRT, and then follow the on-screen instructions.