If a manual Microsoft Defender scan won’t start on Windows 10 or Windows 11, first check whether Defender is your active antivirus and whether its WinDefend service is running. Then start a quick scan from Windows PowerShell and verify that it finished. If PowerShell can complete the scan but the Quick scan button does nothing, repair the Windows Security app rather than changing antivirus services. If neither method works, use the Defender event log to tell whether the scan never started or stopped before it finished.

Windows Defender’s quick scan completed with no threats found, shown in Security, PowerShell, and Event Viewer. Check which antivirus is active and whether WinDefend is running​

Use a local administrator account or have administrator credentials ready for the PowerShell and system repair steps. If this is a work or school PC, you can collect the status and errors, but leave provider and policy changes to IT. These steps apply to Windows 11 and Windows 10 PCs with built-in Microsoft Defender Antivirus. Microsoft ended regular support for Windows 10 Home and Pro on October 14, 2025; getting a scan to work does not restore operating system security updates.

  1. Check the registered antivirus provider. Open Start, search for Windows Security, and open the app. Select Settings inside the app, then Manage providers. Expand Antivirus to see which product is protecting the device. If a non-Microsoft antivirus is active, use that product’s manual scan. Defender can be disabled or run in a limited role, depending on the device’s configuration. A missing Defender scan button in that case does not establish a fault. If Windows Security won’t open, continue to the PowerShell check.
  2. Open an elevated Windows PowerShell window. Search Start for Windows PowerShell, select Run as administrator, and approve the prompt. Run these read-only commands:
    Code:
    Get-Service -Name WinDefend, SecurityHealthService, wscsvc |
        Format-Table Name, DisplayName, Status, StartType -AutoSize
    
    Get-MpComputerStatus |
        Select-Object AMRunningMode, AMServiceEnabled, AntivirusEnabled,
            RealTimeProtectionEnabled, AntivirusSignatureLastUpdated
  3. Read the service and protection results together. If Defender is your primary antivirus, expect WinDefend to show Running with an Automatic startup type, AMRunningMode to show Normal, and AMServiceEnabled and AntivirusEnabled to be True. RealTimeProtectionEnabled reports whether background protection is on; it does not tell you whether a manual scan finished. Likewise, a running SecurityHealthService or wscsvc is not proof that the antivirus engine is working. Those services help Windows Security report protection status.
  4. Follow the result instead of forcing a service to start. If Defender shows Passive, SxS Passive Mode, or EDR Block Mode, check the registered provider or ask IT whether that mode is expected. If Defender is your primary antivirus, its service is running, and only real-time protection is off, go to Windows Security > Virus & threat protection > Manage settings and switch Real-time protection to On if the control is available. Confirm the change with Get-MpComputerStatus. If the control is managed or reverts, or if WinDefend is stopped when Defender should be active, use the troubleshooting section below. Do not alter service startup types or turn off tamper protection to get past a blocked control.

Run a quick scan from PowerShell and verify completion​

  1. In the elevated Windows PowerShell window, note the local time and run:
    Start-MpScan -ScanType QuickScan
    Start with a quick scan rather than a full scan: you’re testing whether the scan engine can start and finish. This command uses the same Defender antivirus engine without relying on the Windows Security button. It does not require a restart. If PowerShell shows an error, save the full message and any hexadecimal error code.
  2. Check the timestamps rather than treating a returned prompt as proof of success:
    Code:
    Get-MpComputerStatus |
        Select-Object QuickScanStartTime, QuickScanEndTime
    Look for a start and end time that match the test you just ran. If Windows Security opens, you can also check Virus & threat protection > Current threats for the last scan time. An old end time is not evidence that the new scan finished.
  3. If the timestamps are unclear, or you need to distinguish an incomplete scan from one that never started, press Windows key + R, enter eventvwr.msc, and press Enter. Open Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational. Check events around the time you issued the command:
    • 1000: A scan started. Check the event details for Quick scan.
    • 1001: A scan finished. Match its Scan ID to the corresponding 1000 event so you don’t mistake a scheduled scan for your test.
    • 1002: A scan stopped before completion. This is a different failure from the scan not starting.

A matching 1001 event confirms completion, not that the scan found nothing. Check Current threats and Protection history for detections or actions. If the PowerShell scan finishes but Quick scan in Windows Security still does nothing, continue with app repair.

Repair Windows Security without changing Defender services​

Windows 11​

  1. Open Settings > System > System components. Microsoft introduced this page in the October 31, 2023 Windows 11 update KB5031455. If your installation does not show it, check Settings > Apps > Installed apps for the Windows Security entry.
  2. Select the three-dot menu next to Windows Security, choose Advanced options, and select Repair if it’s offered. Repair is the first choice because it retains app data. When it finishes, reopen Windows Security from Start and try Virus & threat protection > Quick scan.

Windows 10​

  1. Open Start, search for Windows Security, right-click the app result, and choose App settings. This opens the app’s settings page without needing the Windows Security dashboard to respond.
  2. Select Repair if it’s offered, then reopen the app and test Quick scan. If you see Reset but no Repair, use the next step rather than looking for a separate Defender Antivirus repair button.

If Repair doesn’t help or only Reset is available​

  1. Before you select Reset: It can clear local app data and preferences, and there is no undo button for that data. Note any customized Windows Security notification preferences you can still see. Use Reset on the Windows Security app settings page, not Reset this PC. If you need to preserve the app’s local data, skip Reset and use the Windows component checks below.
  2. Select Reset and confirm with Reset if prompted. Reopen Windows Security, check that the expected antivirus is listed in Manage providers, and confirm real-time protection is on if Defender is your primary antivirus. Reapply any app preferences that changed.
  3. Start Quick scan from Virus & threat protection. Verify that Current threats shows a new scan time or that Event Viewer records a matching start and completion for this attempt. A successful PowerShell scan before the repair does not prove the button works afterward.

Troubleshoot a stopped service, a canceled scan, or an app that still won’t open​

  • WinDefend is stopped, or the command reports 0x800106BA. Microsoft lists a disabled Defender Antivirus service as a possible cause of this code. Confirm that Defender is supposed to be the active provider. If it is, save your work, restart Windows once, and rerun the service and protection checks before retrying the scan. If the service still won’t run and no other provider is active, treat that as a protection problem, not just an app problem. Escalate rather than changing service permissions or deleting policy keys.
  • The scan starts but records event 1002. Check whether Windows restarted around that time. Retry one quick scan with the PC awake and plugged in, without starting a second scan. If it stops again, capture the Scan ID, time, and any nearby Defender errors.
  • PowerShell says Start-MpScan isn’t recognized. Confirm that you opened the built-in Windows PowerShell application, not a Command Prompt tab or a different shell. If the cmdlet is still missing there, record whether Get-MpComputerStatus also fails. Don’t download a replacement Defender module from an unofficial source.

If Windows Security still opens blank or closes immediately, or Advanced options is missing, install available updates and check for damaged Windows components:

  1. On Windows 11, go to Settings > Windows Update > Check for updates. On Windows 10, go to Settings > Update & Security > Windows Update > Check for updates. Install available updates and restart before continuing. On Windows 11, Microsoft distributes the Windows Security app and its underlying service through Windows Update as KB5007651.
  2. If the problem persists, open Command Prompt with Run as administrator. Run Microsoft’s component repair command first:
    DISM.exe /Online /Cleanup-Image /RestoreHealth
    Wait for DISM to report success. If it fails, save the error rather than substituting an unverified repair image or package. If it succeeds, run:
    sfc /scannow
  3. Leave the window open until verification reaches 100%. If SFC repairs files, restart and test both Windows Security and the PowerShell scan again. If SFC cannot repair files, or if neither scan method can produce a matching completion event, give your IT administrator or Microsoft support the Windows version and build from winver, the active provider, the WinDefend status, the PowerShell error, and the relevant Defender event times and Scan IDs.