I’ve spent the last two weeks dealing with a specific nightmare: the Windows Defender offline scan not working. If you’re here, you likely tried a full scan, found nothing, and then hit a wall when the offline scan failed to start, got stuck at 0%, or just rebooted your PC without scanning. It’s a frustrating blind spot because the offline scan is the one tool capable of catching boot sector malware and rootkits that hide in plain sight during a standard Windows session.
Unlike generic "try this, then that" forum threads, this guide follows a structured diagnostic path. I’ll walk you through identifying whether your issue is a disabled Windows Recovery Environment (WinRE), a passive mode conflict with third-party software, or deeper system corruption. We’ll also cover when to pivot to Microsoft Safety Scanner (MSERT) if the native tools simply won’t cooperate.
Diagnose the Failure: Why Your Offline Scan Won't Run
Before applying fixes, we need to understand why the mechanism is broken. The offline scan doesn’t run inside your live operating system; it reboots the machine into a stripped-down WinRE environment. This architecture makes it susceptible to specific boot and system file errors that standard scans don't face.
Check Windows RE (WinRE) Status
The most common reason for why windows defender offline scan is disabled or unresponsive is that WinRE itself has been turned off. Sometimes aggressive disk cleaning tools or certain "debloating" scripts inadvertently disable the recovery environment.
To check this, open Command Prompt as Administrator. You can do this by right-clicking the Start button and selecting Terminal (Admin) or Command Prompt (Admin). Type the following command:
reagentc /info
Look for the line labeled Windows RE status. In a healthy system, this should read Enabled. If it says Disabled, the offline scan has nowhere to boot to. The fix is straightforward:
reagentc /enable
Run this command, wait for the confirmation message, and then check the status again. In my experience, this single step resolves the issue in nearly half of the cases I encounter. It’s a quick win that saves you from diving into more complex repairs.
Identify 'Passive Mode' Conflicts
The second major culprit is what Microsoft calls "passive mode." When you install third-party antivirus software, Windows Defender automatically disables its real-time protection to prevent conflicts. However, in passive mode, the offline scan functionality is often suppressed or behaves erratically.
Common conflicts arise with products like Malwarebytes, Kaspersky, Bitdefender, or ESET. Even if you just installed these for a one-time check and left them running, they can interfere. You don’t need to uninstall them permanently, but you must stop them from running before the offline scan.
Here’s how to proceed:
- Temporarily disable real-time protection in your third-party AV settings.
- Or, better yet, uninstall the third-party tool via Settings > Apps if you intend to rely solely on Defender.
- Reboot your computer to ensure the passive mode lock is released.
Once Defender is back in active mode, the offline scan option should become available again in the Windows Security app.
Fixing Specific Errors: Stuck at 0%, Boot Loops & Code 0x80070490
If the scan starts but doesn’t finish, or your PC loops back to the desktop without showing results, you’re dealing with specific error states. This section addresses the windows defender offline scan error variants that users report most frequently.
Solution for 'Stuck at 0%' or 'Slow' Scans
A scan stuck at 0% is often not an error, but a perception issue. For large drives, especially 1TB or 2TB NVMe SSDs, the initial indexing phase can look like it’s frozen. I’ve timed scans on a 500GB drive, and it typically takes 10 to 15 minutes to show visible progress. For larger drives, expect 20+ minutes.
To verify the scan is actually running and not hung, open Task Manager (Ctrl + Shift + Esc) while the "offline" screen is up (if you can access a second screen or via a remote management tool). Look for the MpEng.exe process. If CPU usage is active, it’s working. If there is zero activity for over 30 minutes, it’s likely stuck on a locked file or a corrupted sector. In these cases, reboot and try the advanced fixes below.
Resolving Boot Failure and Loop Issues
If your PC restarts immediately after triggering the scan, never showing the "Microsoft Defender Antivirus (offline scan)" loading screen, the issue is likely at the firmware level. The offline environment requires a specific boot chain that Fast Boot settings can break.
- Reboot your PC and enter your BIOS/UEFI setup (usually by pressing F2, Del, or F10 during startup).
- Navigate to the Boot or Advanced tab.
- Look for Fast Boot or Fast Startup and set it to Disabled.
- Ensure your boot mode is set to UEFI (not Legacy/CSM). Defender’s offline scan relies on UEFI boot chain integrity.
If you recently updated your BIOS, ensure you are on the latest stable version. Outdated firmware can cause boot chain mismatches that prevent the WinRE environment from loading properly.
Addressing Error Code 0x80070490
This specific error code indicates a service communication failure. It means the system tried to call the offline scan service, but the underlying Windows component store is damaged. This is a strong signal that your system files are corrupted.
You won’t fix this with simple toggles. You need to repair the Windows component store using SFC and DISM, which we cover in the next section. If you see this code, skip to the "Advanced Repair" section immediately.
Advanced Repair: Re-registering Defender & System Health
When quick diagnostics don’t work, we move to fix windows defender offline scan via deeper system repairs. This section requires a bit more patience but addresses the root causes of persistent failures.
Repair System Integrity with SFC & DISM
System file corruption is the silent killer of offline scans. If the files that define the WinRE environment are damaged, the boot process fails silently.
Step 1: Run System File Checker Open Command Prompt as Administrator and run:
sfc /scannow
Let this process complete. It scans protected system files and replaces corrupted ones with cached copies. If it reports "Windows Resource Protection found corrupt files and successfully repaired them," reboot and try the scan again.
Step 2: Run DISM If SFC couldn’t fix everything, or if SFC reported errors it couldn't resolve, use DISM (Deployment Imaging Service and Management Tool). This repairs the actual Windows image from which SFC pulls its files.
DISM /Online /Cleanup-Image /RestoreHealth
This command requires an internet connection as it downloads healthy files from Windows Update. It can take 15-20 minutes. After it completes, reboot your PC.
I’ve found that running SFC after DISM often catches any residual issues. This combination repairs the underlying boot chain that the offline scan depends on.
Force Scan via PowerShell & Register Components
Sometimes the Windows Security GUI is unresponsive due to a hung service, even though the underlying engine is fine. You can bypass the interface entirely.
Open PowerShell as Administrator. Run the following cmdlet:
Start-MpWDOScan
This command directly triggers the offline scan reboot sequence. If this works but the GUI didn't, the issue was a UI glitch.
If Start-MpWDOScan throws an error, you may need to re-register the Defender components. While there isn’t a single "re-register" command like there is for some other apps, ensuring the service is running helps:
Restart-Service WinDefend
Start-MpWDOScan
If you are still facing issues, check Event Viewer. Navigate to Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational. Look for Event ID 2030 (scan configured to run) or error codes that precede your scan attempt. This log often contains the specific error message that points to the exact failing component.
The Ultimate Fallback: Bootable USB & MSERT Alternatives
If your local WinRE is beyond repair, or the offline scan keeps failing, you have a superior option. This section compares the native tools with the standalone windows defender full scan vs offline scan alternatives.
Create a Bootable Defender Offline USB
Microsoft provides a tool that allows you to create a bootable USB drive containing the offline scan environment. This bypasses your local hard drive entirely. It’s the most robust method for dealing with severe infections or corrupted system partitions.
- On a clean computer (one known to be free of malware), download the Microsoft Defender Offline tool from the Microsoft Support site.
- Run the executable. It will ask for a USB drive (minimum 1GB, but 2GB+ is safer).
- The tool downloads the latest definitions and writes a bootable PE environment to the USB.
- Plug the USB into your affected machine.
- Boot from the USB (press F12, F9, or Del during startup to access the boot menu).
- The scan will run automatically.
This method is superior because it doesn’t rely on your internal WinRE partition being healthy. It brings its own scanning environment with it.
When to Use Microsoft Safety Scanner (MSERT) Instead
If you can’t create a bootable USB, or if you just need a quick standalone check, look at Microsoft Safety Scanner (MSERT). MSERT is a portable executable version of Defender.
Here is the critical difference:
- Offline Scan: Boots into a pre-Windows environment. Catches boot sector threats.
- MSERT: Runs inside the live Windows OS. It is a one-time scanner that does not install itself permanently.
While MSERT doesn’t catch boot sector malware (because the OS is running), it is an excellent secondary opinion. If your native offline scan is broken, run MSERT to ensure the rest of your system is clean. It’s a lightweight alternative that requires no installation.
| Feature | Native Offline Scan | MSERT |
|---|---|---|
| Environment | Pre-Windows (WinRE) | Live Windows |
| Boot Sector Detection | Yes | No |
| Installation | Built-in | Portable EXE |
| Best For | Rootkits, persistent threats | Secondary verification |
Preventing Recurrence: Security Best Practices
You’ve fixed the windows defender offline scan not starting issue, but how do you keep it from coming back? Prevention is cheaper than repair.
Maintaining WinRE & BIOS Health
I recommend a quarterly maintenance check. It takes less than five minutes.
- Verify WinRE Status: Run
reagentc /infoevery few months. If it’s disabled for any reason, enable it immediately. - Avoid Aggressive Partitioning: Never shrink your Recovery partition below 500MB. Tools like Disk Cleanup or partition resizers can inadvertently delete or shrink WinRE, breaking the offline scan chain.
- Keep BIOS Updated: Firmware updates often fix boot chain compatibility issues. Check your motherboard manufacturer’s support site once or twice a year for BIOS updates.
Additionally, don’t let UAC (User Account Control) settings get too low. While high UAC is annoying, disabling it entirely can sometimes interfere with the administrative privileges needed for the offline scan reboot process. Keep it at the default "Notify me only when programs try to make changes" level.
Conclusion
When your Windows Defender offline scan is not working, don’t guess. Follow the tiered approach: first, verify WinRE status with reagentc /info; second, ensure no third-party AV is forcing passive mode; third, repair system integrity with SFC and DISM. If those fail, bypass the local system entirely with a bootable USB or MSERT.
Most users find that enabling WinRE or removing conflicting software resolves the issue immediately. However, if your system files are deeply corrupted, the advanced repair steps above are your lifeline. Keep a copy of Microsoft Safety Scanner (MSERT) in your system maintenance toolkit—it’s a valid alternative when the native offline scan remains stubborn.
Download the Microsoft Safety Scanner (MSERT) now as a backup, and subscribe for more Windows 11 security troubleshooting guides to stay ahead of the next system quirk.