Summary
The Windows Malicious Software Removal Tool (MSRT) helps remove malicious software from computers that are running any of the following operating systems:
-
Windows 11
-
Windows Server 2022
-
Windows 10
-
Windows Server 2019
-
Windows Server 2016
-
Windows 8.1
-
Windows Server 2012 R2
-
Windows Server 2012
-
Windows Server 2008 R2
-
Windows 7
-
Windows Server 2008
Microsoft generally releases the MSRT on a monthly cadence as part of Windows Update or as a standalone tool. (For exceptions, see Skipped releases.) Use this tool to find and remove specific prevalent threats and reverse the changes that they made (see Covered malware families). For comprehensive malware detection and removal, consider using Windows Defender Offline or Microsoft Safety Scanner. This article contains information about how the tool differs from an antivirus or antimalware product, how you can download and run the tool, what occurs when the tool finds malware, and tool release information. It also includes information for administrators and advanced users, including information about supported command-line switches.
Notes:
-
In compliance with the Microsoft Support Lifecycle policy, the MSRT is no longer supported on Windows Vista or earlier platforms. For more information, go to Microsoft Support Lifecycle.
-
If you are having problems in regards to an MSRT update within Windows Update, see Troubleshooting problems updating Windows 10.
More information
The MSRT 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 MSRT differs from an antivirus product in three important 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.
For more information about how to protect your computer, go to the Microsoft Safety & Security Center website.Note The MSRT focuses on the detection and removal of malicious software such as viruses, worms, and Trojan horses only. It does not remove spyware.
You do not have to disable or remove your antivirus program when you install the MSRT. 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 MSRT 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.
Note: Starting November 2019, MSRT will be SHA-2 signed exclusively. Your devices must be updated to support SHA-2 in order to run MSRT. To learn more, see 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
The easiest way to download and run the MSRT is to turn on Automatic Updates. Turning on Automatic Updates guarantees that you receive the tool automatically. If you have Automatic Updates turned on, you have already been receiving new versions of this tool. 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 requires your attention.
Enabling automatic updates
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 11 |
Note Whether you set the toggle to Off or On, you'll still get the regular security updates as usual. The toggle determines how quickly you get the additional non-security updates, fixes, feature updates, and improvements. |
|
Windows 10 |
Note Windows 10 is a service. This means that automatic updates are turned on by default and your PC always has the latest and best features. |
|
Windows 8.1 |
|
|
Windows 7 |
|
Download the MSRT. 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 MSRT without being logged on to the computer as an administrator.
The MSRT 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 appears in the notification area to make you aware of the detection.
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 MSRT sends 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.
The MSRT does not use an installer. Typically, when you run the MSRT, 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 Center
Help installing updates: Support for Microsoft Update
Local support according to your country: International Support.
Microsoft Download Center
Note: Starting November 2019, MSRT has been SHA-2 signed exclusively. Your devices must be updated to support SHA-2 in order to run MSRT. To learn more, see 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
You can manually download the MSRT from the Microsoft Download Center. The following files are available for download: For 32-bit x86-based systems:
For 64-bit x64-based systems:
Release Date: November 12, 2024.
For more information about how to download Microsoft support files, see How to obtain Microsoft support files from online services.
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 MSRT in an enterprise environment
If you are an IT administrator who wants more information about how to deploy the tool in an enterprise environment, see Deploy Windows Malicious Software Removal Tool in an enterprise environment.
This article includes information about Microsoft Systems Management Server (SMS), Microsoft Software Update Services (MSUS), and Microsoft Baseline Security Analyzer (MBSA).
Except where noted, the information in this section applies to all the ways that you can download and run the MSRT:
-
Microsoft Update
-
Windows Update
-
Automatic Updates
-
The Microsoft Download Center
-
The MSRT website on Microsoft.com
To run the MSRT, the following conditions are required:
-
The computer must be running a supported version of Windows.
-
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 215 days (7 months) 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 MSRT supports the following 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 MSRT is generally released on the second Tuesday of each 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.
This Microsoft Knowledge Base article will be updated with information for each 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 February 2020 version is Windows-KB890830-V5.80.exe, and the file name of the May 2020 version is Windows-KB890830-V5.82-ENU.exe. 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.
|
Malicious software family |
Tool version date and number |
|---|---|
|
MofngoLoader |
November 2024 (v 5.130) |
|
July 2024 (v 5.126) |
|
|
July 2024 (v 5.126) |
|
|
May 2024 (v 5.124) |
|
|
April 2024 (v 5.123) |
|
|
April 2024 (v 5.123) |
|
|
March 2024 (v 5.122) |
|
|
March 2024 (v 5.122) |
|
|
March 2024 (v 5.122) |
|
|
February 2024 (v 5.121) |
|
|
February 2024 (v 5.121) |
|
|
February 2024 (v 5.121) |
|
|
February 2024 (v 5.121) |
|
|
January 2024 (v 5.120) |
|
|
January 2024 (v 5.120) |
|
|
January 2024 (v 5.120) |
|
|
January 2024 (v 5.120) |
|
|
January 2024 (v 5.120) |
|
|
January 2024 (v 5.120) |
|
|
January 2024 (v 5.120) |
|
|
January 2024 (v 5.120) |
|
|
January 2024 (v 5.120) |
|
|
November 2023 (v 5.119) |
|
|
October 2023 (v 5.118) |
|
|
September 2023 (v 5.117) |
|
|
May 2023 (v 5.113) |
|
|
May 2023 (v 5.113) |
|
|
May 2023 (v 5.113) |
|
|
April 2023 (v 5.112) |
|
|
April 2023 (v 5.112) |
|
|
March 2023 (v 5.111) |
|
|
March 2023 (v 5.111) |
|
|
March 2023 (v 5.111) |
|
|
March 2023 (v 5.111) |
|
|
November 2022 (v 5.107) |
|
|
November 2022 (v 5.107) |
|
|
November 2022 (v 5.107) |
|
|
September 2022 (v 5.105) |
|
|
September 2022 (v 5.105) |
|
|
September 2022 (v 5.105) |
|
|
July 2022 (v 5.103) |
|
|
July 2022 (v 5.103) |
|
|
July 2022 (v 5.103) |
|
|
July 2022 (v 5.103) |
|
|
May 2022 (v 5.101) |
|
|
April 2022 (v 5.100) |
|
|
April 2022 (v 5.100) |
|
|
April 2022 (v 5.100) |
|
|
April 2022 (v 5.100) |
|
|
April 2022 (v 5.100) |
|
|
April 2022 (v 5.100) |
|
|
April 2022 (v 5.100) |
|
|
April 2022 (v 5.100) |
|
|
April 2022 (v 5.100) |
|
|
March 2022 (V5.99) |
|
|
March 2022 (V5.99) |
|
|
March 2022 (V5.99) |
|
|
March 2022 (V5.99) |
|
|
March 2022 (V5.99) |
|
|
February 2022 (V 5.98) |
|
|
July 2021 (V 5.91) |
|
|
July 2021 (V 5.91) |
|
|
July 2021 (V 5.91) |
|
|
July 2021 (V 5.91) |
|
|
July 2021 (V 5.91) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
April 2021 (V 5.88) |
|
|
February 2021 (V 5.86) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
January 2021 (V 5.85) |
|
|
September 2020 (V 5.83) |
|
|
September 2020 (V 5.83) |
|
|
September 2020 (V 5.83) |
|
|
September 2020 (V 5.83) |
|
|
September 2020 (V 5.83) |
|
|
September 2020 (V 5.83) |
|
|
March 2020 (5.81) |
|
|
March 2020 (5.81) |
|
|
January 2020 (5.79) |
|
|
January 2020 (5.79) |
|
|
January 2020 (5.79) |
|
|
October 2019 (5.76) |
|
|
May 2019 (5.72) |
|
|
April 2019 (5.71) |
|
|
March 2019 (5.70) |
|
|
December 2018 (5.67) |
|
|
December 2018 (5.67) |
|
|
December 2018 (5.67) |
|
|
December 2018 (5.67) |
|
|
December 2018 (5.67) |
|
|
October 2018 (5.65) |
|
|
October 2018 (5.65) |
|
|
October 2018 (5.65) |
|
|
October 2018 (5.65) |
|
|
June 2018 (5.61) |
|
|
June 2018 (5.61) |
|
|
May 2018 (5.60) |
|
|
May 2018 (5.60) |
|
|
May 2018 (5.60) |
|
|
April 2018 (5.59) |
|
|
March 2018 (5.58) |
|
|
March 2018 (5.58) |
|
|
December 2017 (5.55) |
|
|
December 2017 (5.55) |
|
|
December 2017 (5.55) |
|
|
December 2017 (5.55) |
|
|
December 2017 (5.55) |
|
|
December 2017 (5.55) |
|
|
December 2017 (5.55) |
|
|
November 2017 (5.54) |
|
|
October 2017 (5.53) |
|
|
October 2017 (5.53) |
|
|
June 2017 (5.49) |
|
|
May 2017 (5.48) |
|
|
February 2017 (5.45) |
|
|
December 2016 (5.43) |
|
|
November 2016 (5.42) |
|
|
November 2016 (5.42) |
|
|
October 2016 (5.41) |
|
|
October 2016 (5.41) |
|
|
October 2016 (5.41) |
|
|
September 2016 (5.40) |
|
|
September 2016 (5.40) |
|
|
September 2016 (5.40) |
|
|
September 2016 (5.40) |
|
|
August 2016 (5.39) |
|
|
August 2016 (5.39) |
|
|
July 2016 (5.38) |
|
|
June 2016 (5.37) |
|
|
May 2016 (5.36) |
|
|
May 2016 (5.36) |
|
|
April 2016 (5.35) |
|
|
April 2016 (5.35) |
|
|
April 2016 (5.35) |
|
|
March 2016 (5.34) |
|
|
March 2016 (5.34) |
|
|
December 2015 (5.31) |
|
|
October 2015 (5.29) |
|
|
October 2015 (5.29) |
|
|
October 2015 (5.29) |
|
|
October 2015 (5.29) |
|
|
October 2015 (5.29) |
|
|
October 2015 (5.29) |
|
|
October 2015 (5.29) |
|
|
September 2015 (5.28) |
|
|
August 2015 (5.27) |
|
|
August 2015 (5.27) |
|
|
August 2015 (5.27) |
|
|
July 2015 (5.26) |
|
|
July 2015 (5.26) |
|
|
July 2015 (5.26) |
|
|
June 2015 (5.25) |
|
|
June 2015 (5.25) |
|
|
June 2015 (5.25) |
|
|
June 2015 (5.25) |
|
|
April 2015 (5.23) |
|
|
April 2015 (5.23) |
|
|
April 2015 (5.23) |
|
|
April 2015 (5.23) |
|
|
March 2015 (5.22) |
|
|
March 2015 (5.22) |
|
|
February 2015 (5.21) |
|
|
February 2015 (5.21) |
|
|
February 2015 (5.21) |
|
|
January 2015 (5.20) |
|
|
January 2015 (5.20) |
|
|
November 2014 (5.18) |
|
|
November 2014 (5.18) |
|
|
November 2014 (5.18) |
|
|
October 2014 (5.17) |
|
|
October 2014 (5.17) |
|
|
October 2014 (5.17) |
|
|
October 2014 (5.17) |
|
|
October 2014 (5.17) |
|
|
October 2014 (5.17) |
|
|
September 2014 (5.16) |
|
|
August 2014 (5.15) |
|
|
July 2014 (5.14) |
|
|
July 2014 (5.14) |
|
|
June 2014 (5.13) |
|
|
May 2014 (5.12) |
|
|
May 2014 (5.12) |
|
|
April 2014 (5.11) |
|
|
April 2014 (5.11) |
|
|
March 2014 (5.10) |
|
|
March 2014 (5.10) |
|
|
February 2014 (5.9) |
|
|
January 2014 (5.8) |
|
|
December 2013 (5.7) |
|
|
November 2013 (5.6) |
|
|
November 2013 (5.6) |
|
|
October 2013 (5.5) |
|
|
October 2013 (5.5) |
|
|
September 2013 (5.4) |
|
|
June 2013 (4.21) |
|
|
May 2013 (4.20) |
|
|
May 2013 (4.20) |
|
|
May 2013 (4.20) |
|
|
April 2013 (4.19) |
|
|
April 2013 (4.19) |
|
|
April 2013 (4.19) |
|
|
March 2013 (4.18) |
|
|
February 2013 (4.17) |
|
|
January 2013 (4.16) |
|
|
January 2013 (4.16) |
|
|
December 2012 (4.15) |
|
|
November 2012 (4.14) |
|
|
November 2012 (4.14) |
|
|
November 2012 (4.14) |
|
|
October 2012 (4.13) |
|
|
October 2012 (4.13) |
|
|
September 2012 (4.12) |
|
|
August 2012 (4.11) |
|
|
August 2012 (4.11) |
|
|
June 2012 (4.9) |
|
|
June 2012 (4.9) |
|
|
May 2012 (4.8) |
|
|
May 2012 (4.8) |
|
|
April 2012 (4.7) |
|
|
April 2012 (4.7) |
|
|
April 2012 (4.7) |
|
|
March 2012 (4.6) |
|
|
March 2012 (4.6) |
|
|
March 2012 (4.6) |
|
|
March 2012 (4.6) |
|
|
February 2012 (4.5) |
|
|
February 2012 (4.5) |
|
|
January 2012 (4.4) |
|
|
December 2011 (4.3) |
|
|
November 2011 (4.2) |
|
|
November 2011 (4.2) |
|
|
November 2011 (4.2) |
|
|
October 2011 (4.1) |
|
|
October 2011 (4.1) |
|
|
September 2011 (4.0) |
|
|
September 2011 (4.0) |
|
|
August 2011 (3.22) |
|
|
August 2011 (3.22) |
|
|
July 2011 (3.21) |
|
|
July 2011 (3.21) |
|
|
June 2011 (3.20) |
|
|
June 2011 (3.20) |
|
|
June 2011 (3.20) |
|
|
May 2011 (3.19) |
|
|
April 2011 (3.18) |
|
|
March 2011 (3.17) |
|
|
February 2011 (3.16) |
|
|
January 2011 (3.15) |
|
|
December 2010 (3.14) |
|
|
November 2010 (3.13) |
|
|
November 2010 (3.13) |
|
|
November 2010 (3.13) |
|
|
October 2010 (3.12) |
|
|
September 2010 (3.11) |
|
|
September 2010 (3.11) |
|
|
August 2010 (3.10) |
|
|
August 2010 (3.10) |
|
|
August 2010 (3.10) |
|
|
August 2010 (3.10) |
|
|
August 2010 (3.10) |
|
|
August 2010 (3.10) |
|
|
August 2010 (3.10) |
|
|
August 2010 (3.10) |
|
|
August 2010 (3.10) |
|
|
July 2010 (3.9) |
|
|
June 2010 (3.8) |
|
|
May 2010 (3.7) |
|
|
April 2010 (3.6) |
|
|
March 2010 (3.5) |
|
|
February 2010 (3.4) |
|
|
January 2010 (3.3) |
|
|
December 2009 (3.2) |
|
|
November 2009 (3.1) |
|
|
November 2009 (3.1) |
|
|
October 2009 (3.0) |
|
|
September 2009 (2.14) |
|
|
September 2009 (2.14) |
|
|
August 2009 (2.13) |
|
|
July 2009 (2.12) |
|
|
June 2009 (2.11) |
|
|
May 2009 (2.10) |
|
|
April 2009 (2.9) |
|
|
March 2009 (2.8) |
|
|
February 2009 (2.7 ) |
|
|
January 2009 (2.6) |
|
|
January 2009 (2.6) |
|
|
December 2008 (2.5) |
|
|
December 2008 (2.5) |
|
|
November 2008 (2.4) |
|
|
November 2008 (2.4 ) |
|
|
October 2008 (2.3) |
|
|
September 2008 (2.2) |
|
|
August 2008 (2.1) |
|
|
July 2008 (2.0) |
|
|
June 2008 (1.42) |
|
|
June 2008 (1.42) |
|
|
June 2008 (1.42) |
|
|
June 2008 (1.42) |
|
|
June 2008 (1.42) |
|
|
June 2008 (1.42) |
|
|
June 2008 (1.42) |
|
|
June 2008 (1.42) |
|
|
May 2008 (1.41) |
|
|
May 2008 (1.41) |
|
|
March 2008 (1.39) |
|
|
March 2008 (1.39) |
|
|
March 2008 (1.39) |
|
|
February 2008 (1.38) |
|
|
January 2008 (1.37) |
|
|
December 2007 (1.36) |
|
|
November 2007 (1.35) |
|
|
October 2007 (1.34) |
|
|
September 2007 (1.33) |
|
|
August 2007 (1.32) |
|
|
August 2007 (1.32) |
|
|
August 2007 (1.32) |
|
|
July 2007 (1.31) |
|
|
June 2007 (1.30) |
|
|
May 2007 (1.29) |
|
|
April 2007 (1.28) |
|
|
March 2007 (1.27) |
|
|
February 2007 (1.25) |
|
|
February 2007 (1.25) |
|
|
January 2007 (1.24) |
|
|
January 2007 (1.24) |
|
|
December 2006 (1.23) |
|
|
November 2006 (1.22) |
|
|
October 2006 (1.21) |
|
|
October 2006 (1.21) |
|
|
October 2006 (1.21) |
|
|
September 2006 (1.20) |
|
|
September 2006 (1.20) |
|
|
August 2006 (1.19) |
|
|
August 2006 (1.19) |
|
|
July 2006 (1.18) |
|
|
July 2006 (1.18) |
|
|
July 2006 (1.18) |
|
|
July 2006 (1.18) |
|
|
June 2006 (1.17) |
|
|
June 2006 (1.17) |
|
|
May 2006 (1.16) |
|
|
May 2006 (1.16) |
|
|
May 2006 (1.16) |
|
|
April 2006 (1.15) |
|
|
April 2006 (1.15) |
|
|
April 2006 (1.15) |
|
|
March 2006 (1.14) |
|
|
March 2006 (1.14) |
|
|
March 2006 (1.14) |
|
|
February 2006 (1.13) |
|
|
February 2006 (1.13) |
|
|
February 2006 (1.13) |
|
|
February 2006 (1.13) |
|
|
January 2006 (1.12) |
|
|
January 2006 (1.12) |
|
|
January 2006 (1.12) |
|
|
December 2005 (1.11) |
|
|
December 2005 (1.11) |
|
|
December 2005 (1.11) |
|
|
November 2005 (1.10) |
|
|
November 2005 (1.10) |
|
|
November 2005 (1.10) |
|
|
November 2005 (1.10) |
|
|
November 2005 (1.10) |
|
|
October 2005 (1.9) |
|
|
October 2005 (1.9) |
|
|
October 2005 (1.9) |
|
|
October 2005 (1.9) |
|
|
September 2005 (1.8) |
|
|
September 2005 (1.8) |
|
|
September 2005 (1.8) |
|
|
September 2005 (1.8) |
|
|
September 2005 (1.8) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 A (1.7.1) |
|
|
August 2005 (1.7) |
|
|
August 2005 (1.7) |
|
|
August 2005 (1.7) |
|
|
July 2005 (1.6) |
|
|
July 2005 (1.6) |
|
|
July 2005 (1.6) |
|
|
July 2005 (1.6) |
|
|
July 2005 (1.6) |
|
|
June 2005 (1.5) |
|
|
June 2005 (1.5) |
|
|
June 2005 (1.5) |
|
|
June 2005 (1.5) |
|
|
May 2005 (1.4) |
|
|
May 2005 (1.4) |
|
|
May 2005 (1.4) |
|
|
April 2005 (1.3) |
|
|
April 2005 (1.3) |
|
|
April 2005 (1.3) |
|
|
March 2005 (1.2) |
|
|
March 2005 (1.2) |
|
|
March 2005 (1.2) |
|
|
March 2005 (1.2) |
|
|
March 2005 (1.2) |
|
|
February 2005 (1.1) |
|
|
February 2005 (1.1) |
|
|
February 2005 (1.1) |
|
|
February 2005 (1.1) |
|
|
January 2005 (1.0) |
|
|
January 2005 (1.0) |
|
|
January 2005 (1.0) |
|
|
January 2005 (1.0) |
|
|
January 2005 (1.0) |
|
|
January 2005 (1.0) |
|
|
January 2005 (1.0) |
|
|
January 2005 (1.0) |
We maximize customer protection by regularly reviewing and prioritizing our signatures. We add or remove detections as the threat landscape evolves.
Note: It is recommended to have an up to date next-gen antimalware product installed for continuous protection.
Reporting component
The MSRT 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
If apparently malicious software is found on the computer, the tool prompts you to send information to Microsoft beyond what is listed here. You are prompted in each of these instances, and this information is sent only with your consent. The additional information includes the following:
-
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.
You can disable the reporting feature. For information about how to disable the reporting component and how to prevent this tool from sending information to Microsoft, see Deploy Windows Malicious Software Removal Tool in an enterprise environment.
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.Note This result is 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.Note To complete this removal, you should use an up-to-date antivirus product.
Frequently asked questions about the MSRT
A1: Yes.
A2: For information about the log file, see Deploy Windows Malicious Software Removal Tool in an enterprise environment.
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.
A4: If you are a Windows 7 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 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 reminds you to look for a new version of the tool.
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.
A6: Currently, no. Malicious software that is targeted in the tool is based on metrics that track the prevalence and damage of malicious software.
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, see Deploy Windows Malicious Software Removal Tool in an enterprise environment.
A8: Several scenarios may prevent you from seeing the tool on Microsoft Update, 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.
A9: The tool is offered to all supported Windows and Windows Server versions that are listed in the "Summary" section if the following conditions are true:
-
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.
A10: For information about the errors, see How to troubleshoot an error when you run the Microsoft Windows Malicious Software Removal Tool.
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.
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 action 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 prefer not to install the tool through Windows Update, clear the checkbox that corresponds to the tool in the Windows Update UI.
A13: If 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.
A14: Currently, the Malicious Software Removal Tool is not supported on a Windows Embedded computer.
A15: No. Unlike most previous cleaner tools that were produced by Microsoft, the MSRT has 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.
A16: For information about how to deploy this tool, see Deploy Windows Malicious Software Removal Tool in an enterprise environment.
A17: No.
A18: Yes. You can use the microsoft.public.security.virus newsgroup.
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.
A20: Yes, the tool is available in 24 languages.
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.
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.
Skipped releases
The following months do not have an MSRT update:
-
December 2023
-
December 2024
