MSERT itself has not been described in the context as having a specific bug that prevents full scans from completing, nor as having a new “debugged” version that fixes such an issue.
However, if a Microsoft malware scan (including MSERT or other Microsoft anti‑malware tools) does not complete or appears to hang, the supported guidance is to troubleshoot the environment rather than wait for a new tool version:
- Ensure there is enough free disk space, especially on the system drive (usually C:). Microsoft Defender and related tools require disk space to quarantine and remove malware. If space is low, free up space and then run the scan again.
- Close non‑essential applications before starting the scan so that CPU and memory are available. For best results, restart the PC and run the scan immediately before opening other apps.
- If the scan fails with an error code, open the MSERT log and match the error code to the documented causes and resolutions:
- Open
%systemroot%\debug (typically C:\Windows\debug).
- Open the
msert log file.
- Find the error code (usually starting with
0x) and follow the documented action, for example:
-
0x80508019: Change the scan destination file or drive.
-
0x80508007: Download the Microsoft Safety Scanner again.
-
0x8050800C: Restart the computer and retry the scan.
-
0x8050A005, 0x8050A002: Download the Microsoft Safety Scanner again.
- If scans still take very long, note that full scans can legitimately take hours on large disks or when many large/archive files (such as ZIPs) are present.
Running through these steps is the supported way to get a full scan to complete on Windows 10 rather than relying on a specific “debugged” release.
References: