Windows Defender

What you experienced is a fairly common first-run behavior with Microsoft Defender and, while frustrating, it usually does not indicate malware or a broken system.

A “Quick Scan” is not a fixed-size job. On a first scan, Defender builds caches, evaluates startup items, scans memory, drivers, running services, and certain system areas that may not yet be indexed. If the machine has never been scanned before, has recently been upgraded, or has many third-party programs installed, a quick scan can take much longer than expected and may appear to stall near the end.

The scan percentage is not linear. The last 10–15% often includes memory inspection, driver verification, and cloud-based reputation checks. During this phase, progress may appear frozen even though Defender is still working in the background. If CPU or disk activity was still present, it was almost certainly still running. Unfortunately, Defender does not provide good on-screen feedback when this happens.

Stopping the scan manually does not harm anything, but it means the scan never completed and no final result was recorded. That alone is not a security concern.

A few things you can do now to get clarity and avoid a repeat of this experience.

First, check whether Defender logged anything. Open Windows Security, go to Virus & threat protection, then Protection history. If the scan truly stopped due to an error, it will usually be recorded there. If nothing appears, it likely never formally ended.

Second, reboot the system and try another Quick Scan, but let it run even if it seems stuck. On subsequent scans, Defender usually completes much faster because the initial analysis work has already been done.

If it hangs again at roughly the same point, it may indicate a specific file, driver, or service causing the scan engine to choke. In that case, running a scan from the command line often completes where the GUI appears frozen. Open an elevated Command Prompt and run:

"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -Scan -ScanType 1

This performs the same quick scan but provides more reliable execution.

If you want maximum certainty, you can run a one-time offline scan, which scans before Windows fully loads and bypasses interference from running software. This is the most thorough way to rule out malware when Defender behaves oddly. You can start it from Windows Security under Scan options, or via command line:

"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -Scan -ScanType 2

Finally, ensure Defender itself is up to date. An outdated engine or definitions can cause scan stalls. You can force an update with:

"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -SignatureUpdate

So effectively, a long or apparently frozen first quick scan is usually normal, especially on a new or long-unused system. If repeated scans consistently stop at the same percentage even after rebooting and updating, that would justify deeper investigation, but a single stalled first scan by itself is not a red flag.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin