MRT.exe is normally safe when it is the Microsoft-signed file at %windir%\System32\mrt.exe. Windows commonly runs it after the monthly Malicious Software Removal Tool update, so temporary CPU or disk activity can be expected. Check the exact file if its location or origin is unexplained, its Microsoft signature is invalid, or its activity keeps recurring without a known scan or update. Do not delete the genuine file just because it started automatically.
A standalone MSRT package downloaded directly from Microsoft can legitimately be in Downloads, and the tool can create temporary extraction files. The standard installed copy, a download you chose, and an unexplained startup copy need different checks.
The filename alone is not proof either way. A legitimate Microsoft component and a malicious copy can use the same name. The reliable decision comes from checking the path, digital signature, runtime pattern, and MRT log together.
What is MRT.exe?
MRT.exe runs the Windows Malicious Software Removal Tool, usually shortened to MSRT or MRT. Microsoft distributes updated versions through Windows Update and releases a new version on the second Tuesday of each month as needed. The tool checks Windows for specific, prevalent malware families and attempts to reverse changes made by those threats.
That scope matters: MRT is an on-demand cleanup tool, not a full-time antivirus. It does not continuously monitor downloads, browser activity, email, or every program that starts. Microsoft explicitly recommends using current antimalware software even when MSRT is present.
How to run MRT.exe manually
- Check the copy you plan to run. The installed file should be at
%windir%\System32\mrt.exeand have a valid Microsoft signature. If either check fails, leave that copy closed and use the verification steps below. If the file is missing, use Windows Update or the Microsoft Download Center listed under References. - Open the verified tool. Press Windows + R, enter
%windir%\System32\mrt.exe, and press Enter. Approve the Windows permission prompt if it identifies the Microsoft tool you just checked, then select Next. - Choose what to scan. Choose Quick scan to check common infection locations, Customized scan to include a particular folder, or Full scan to check the whole computer. If MRT recommends a full scan after a detection, let it finish; it can take several hours.
- Read the final result. If MRT asks for a restart or lists steps to finish removal, follow those instructions. If the scan fails, note the error code and check the latest entry in
%windir%\debug\mrt.log. A result with no detections applies only to the threats MRT checks for.
If Windows cannot find MRT
First try the full installed path above. If it is absent, check Windows Update or use the official Microsoft Download Center entry under References. Microsoft also distributes MSRT as a standalone, versioned Windows-KB890830-...exe package: it does not have to be named mrt.exe or copied into System32. Verify that downloaded file’s Microsoft signature before opening it. Running MSRT requires administrator privileges; on a managed computer, ask your administrator rather than changing security settings.
Why is MRT.exe running and using CPU or disk?
Windows can start MRT.exe after the monthly tool update is installed. During its scan, the process reads files and compares them with the threats covered by that release. This can temporarily raise CPU or disk use, especially on a system with many files or slower storage.
There is no universal “safe” number of minutes. A one-time run that completes and releases its resources is different from a process that restarts repeatedly, remains busy indefinitely, or appears every time you sign in without an update or deliberate scan.
- A verified scan after Windows Update, or one you started: let it finish. Temporary CPU or disk use alone does not identify malware. Compare the completed run with the latest
mrt.logentry. - A file in Downloads or a temporary folder: check whether you obtained the standalone package from Microsoft or whether it belongs to MSRT extraction. Check that exact file’s signature; location alone does not settle the question.
- An unexplained copy in AppData, Startup, or another folder, or an invalid signature: leave it closed and scan with a trusted security tool. Do not launch an unknown copy to test it.
- Repeated starts, a scan that never completes, or unrelated suspicious activity: record the path, timing and log error, then follow the investigation section below. There is no fixed CPU percentage or duration that proves an infection.
How to verify MRT.exe
1. Open the file location
In Task Manager, find Microsoft Windows Malicious Software Removal Tool or MRT.exe, right-click it, and choose Open file location. The standard copy should resolve to:
C:\Windows\System32\mrt.exe
%windir% usually means C:\Windows, but checking the environment variable is safer than assuming the system drive. A familiar icon or the filename “MRT.exe” is not enough. Malware can copy both.
If you are checking a different executable, use the broader EXE file safety checklist for hashes, signatures, reputation, and behavior.
2. Check the Microsoft digital signature
Right-click the file, open Properties, and look at Digital Signatures. The signer should identify Microsoft, and Windows should report that the signature is valid. A valid signature confirms that the signed file has not been altered since signing; it does not excuse unexpected persistence or other malicious behavior around the process.
PowerShell users can inspect the standard copy without launching it:
Get-AuthenticodeSignature "$env:windir\System32\mrt.exe" | Format-List Status,StatusMessage,SignerCertificate
Check the file you actually found. The command above checks only the System32 copy. If Task Manager or a security alert points elsewhere, checking System32 does not verify that other file. Replace the example path below with the exact path you recorded:
Get-AuthenticodeSignature -LiteralPath "C:\path\to\mrt.exe" |
Format-List Status,StatusMessage,SignerCertificate
Look for Status : Valid and a Microsoft signer in the certificate details. NotSigned, HashMismatch, or an unknown signer needs investigation. A valid result applies only to the file at the path you checked. Microsoft documents Get-AuthenticodeSignature as the PowerShell command for obtaining Authenticode signature information from a file.
3. Check the runtime pattern and MRT.log
Open this file in Notepad:
%windir%\debug\mrt.log
The log records MSRT execution details and scan results. Compare its timestamps with the process activity you observed. A recent completed run after Windows Update supports the normal explanation. Repeated starts with no clear completion, recurring errors, or activity that does not line up with the log deserves a closer look.
If the scan displayed an infected-file count but the final result said no threats were found, do not infer an active infection from the preliminary number alone. The separate guide to Microsoft scanner result mismatches and log interpretation covers that intent in detail.

What is Mrtstub.exe in a random temporary folder?
MSRT updates can extract through Mrtstub.exe in a randomly named temporary folder, sometimes at the root of a drive with sufficient free space. Microsoft describes this as part of the tool’s deployment behavior. A random folder alone therefore does not prove malware.
Check the signature of Mrtstub.exe itself and whether its creation matches a known MSRT run. Microsoft says the temporary folder usually disappears after the run or the next restart, but it can remain. A leftover folder alone is not evidence that malware survived.
If the run has finished and you have identified the folder as MSRT’s temporary extraction folder, Microsoft says it can be deleted manually. This does not mean deleting an arbitrary folder at the drive root or the installed System32 copy. If the signature is invalid or a startup entry keeps launching an unexplained copy, investigate that exact file instead.
MRT, Microsoft Safety Scanner, or Defender?
- MRT / MSRT: Monthly check and cleanup for a limited set of specific prevalent threats. It can run through Windows Update but does not provide continuous protection.
- Microsoft Safety Scanner: A separately downloaded on-demand scanner for a manual second check. The download expires after a short period and must be downloaded again for current definitions.
- Microsoft Defender Antivirus: Built-in, ongoing real-time protection, scheduled scans, and broader everyday malware detection when enabled and up to date.
These tools can complement one another, but MRT should not replace Defender or another maintained real-time antivirus. Likewise, downloading a file named MRT.exe from an executable-download site is not a repair method. Obtain the tool only through Windows Update or an official Microsoft download.
What to do if MRT.exe is outside System32, unsigned, or keeps returning
- Leave an unexplained copy closed. Record the full path, signature result, any security alert and whether you started a Microsoft download or scan. If the only finding is a verified MSRT download or leftover extraction folder, use the checks above before treating it as an infection.
- Scan when the file or behavior remains suspicious. Update your security tool and run a full scan. With Gridinsoft Anti-Malware, update its detection database, choose Full Scan, review the findings and apply the recommended cleanup. Restart if prompted, then check whether the original process or warning returns. A same-name file may be accompanied by another component that recreates it.
- If it returns, investigate the trigger. Use the recorded path and scan results to narrow the search. Note the file creation time and any parent process shown by your security or process-monitoring tools; compare them with the scan or update you expected. Reviewing Startup Apps, Task Scheduler, services or Run keys is an optional advanced follow-up, not a prerequisite for scanning. Do not delete entries merely because their names look similar.
- Disconnect if there are signs of active compromise. Unexplained account changes, disabled security controls or suspicious credential prompts warrant disconnecting while you investigate. Network activity alone is not a verdict: Microsoft documents MSRT reporting when it detects malware or encounters an error.
- Keep the genuine System32 copy. If the verified file’s activity matches an update or deliberate scan, deleting it is unnecessary. If a security tool flags it, retain the detection details for review; do not add a blanket exclusion just because the filename or publisher looks familiar.
FAQ
Can I delete MRT.exe?
Do not delete the genuine Microsoft-signed copy in %windir%\System32. Windows Update can deliver it again, and removal does not fix the cause of high CPU or a malicious same-name copy. Investigate the exact path and signature instead.
Does MRT.exe run automatically?
Yes. Windows can execute the tool after its monthly Windows Update delivery. A one-time automatic run is normal; unexplained repeated launches or continuous activity should be checked.
Does MRT.exe find every virus?
No. MSRT targets specific prevalent malware and reverses certain changes made by those threats. It is not a comprehensive real-time antivirus and cannot guarantee that a system is clean.
Is MRT.exe outside System32 always malware?
No. A standalone package you downloaded from Microsoft and MSRT temporary extraction files can be outside System32. An unexplained copy still needs investigation. Check its exact path, Microsoft signature, download or update context, and activity; checking the genuine System32 copy does not verify a different file.
References
- Microsoft Support. “Remove specific prevalent malware with Windows Malicious Software Removal Tool (KB890830).” Microsoft, accessed November 5, 2026. support.microsoft.com.
- Microsoft Learn. “Get-AuthenticodeSignature (Microsoft.PowerShell.Security).” PowerShell 7.5 documentation; accessed November 5, 2026. learn.microsoft.com.
- Microsoft Download Center. “Windows Malicious Software Removal Tool 64-bit.” Standalone MSRT download; accessed November 5, 2026. microsoft.com.

