sodcalculator

10 Tech How-To

Fix Windows Defender Service Won’t Start

Guide 10-56424 · Updated · Step by step

When Windows Defender Service (WinDefend) refuses to start, you lose real-time malware protection, leaving your PC exposed. This guide walks through the most common causes and fixes, from checking the service’s dependencies to repairing corrupted files, so you can get Defender running again without reinstalling Windows.

What You’ll Need

  • An administrator account (you’ll need to approve UAC prompts)
  • Internet connection (for Windows Update and downloading the Microsoft Safety Scanner if needed)
  • About 15–30 minutes of time

Step-by-Step

  1. Restart the service manually. Press Win + R, type services.msc, and press Enter. Scroll to Windows Defender Antivirus Service, right-click it, and choose Start. If it starts, you’re done. If you get an error like “Error 1058” or “Error 5,” continue.
  2. Check the service’s dependencies. Right-click the same service, select Properties, then the Dependencies tab. Note the listed services. Common ones include RpcSs (Remote Procedure Call), DcomLaunch, and WdNisSvc (Windows Defender Network Inspection Service). Open each one in the Services window and ensure its Startup type is set correctly (usually Automatic for RpcSs and DcomLaunch) and that it’s running. If a dependency is disabled, enable it and start it, then try starting Defender again.
  3. Set the service startup type to Automatic. In the service’s Properties, set Startup type to Automatic (or Automatic (Delayed Start) if you see that option). Click Apply, then Start. If it won’t start, note the exact error code.
  4. Run the built-in Windows Defender troubleshooter. Open Settings (Win + I), go to System > Troubleshoot > Other troubleshooters. Find Windows Defender and click Run. Follow the prompts; it may automatically fix registry or policy issues.
  5. Check for third-party antivirus conflicts. If you previously had another antivirus (Norton, McAfee, Avast, etc.) and uninstalled it, leftover drivers can block Defender. Open Settings > Apps > Installed apps, look for any remnants of old security software, and uninstall them. If you see a driver like Sentinel or NAVENG in the list, that’s a strong clue. Reboot after uninstalling.
  6. Repair system files with SFC and DISM. Open Command Prompt as administrator (right-click Start, choose Terminal (Admin) or Command Prompt (Admin)). Run sfc /scannow and wait for it to finish. Then run DISM /Online /Cleanup-Image /RestoreHealth. This can take 10–20 minutes. Reboot and try starting the service again.
  7. Check the Windows Defender registry key. Press Win + R, type regedit, and press Enter. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend. On the right, double-click Start and set the value to 2 (Automatic). Also check the ImagePath value – it should be "C:\Program Files\Windows Defender\MsMpEng.exe" (including the quotes). If it’s wrong, fix it. Close regedit and reboot.
  8. Re-register Windows Defender via PowerShell. Open PowerShell as administrator. Run the following command and wait for it to complete:
    Get-AppxPackage Microsoft.WindowsDefender | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
    Reboot afterward.
  9. Use the Microsoft Safety Scanner as a temporary fallback. If Defender still won’t start, download the Microsoft Safety Scanner from the official Microsoft website. Run a full scan to ensure your system is clean. This doesn’t fix the service, but it protects you while you troubleshoot.
  10. Reset Windows Security app. Open Settings > Apps > Installed apps, search for Windows Security, click the three dots, choose Advanced options, then Reset. Reboot and try again.
  11. Perform a repair upgrade (last resort). Download the Windows 11 or Windows 10 Installation Assistant from Microsoft’s official site. Run it and choose Keep personal files and apps. This reinstalls Windows while preserving your data and often fixes broken system components. Back up important files first.

Common Mistakes

  • Skipping the dependency check. If RpcSs or DcomLaunch is disabled (often by third-party “optimizers” or after a failed update), Defender cannot start no matter what you do.
  • Setting the startup type to Disabled. Some guides tell you to disable Defender to install another antivirus; if you later re-enable it, you must set it back to Automatic, not leave it Disabled.
  • Editing the registry without checking ImagePath. A wrong path (missing quotes, wrong drive letter) will cause the service to fail instantly.
  • Not rebooting after changes. Many fixes require a restart to take effect; skipping it can make you think the fix failed.
  • Running only SFC and not DISM. SFC repairs files, but if the component store is corrupted, DISM must run first (or after) to provide valid source files.

Tips

  • Before making changes, create a System Restore point (rstrui.exe) so you can roll back if something goes wrong.
  • Use the Event Viewer (right-click Start > Event Viewer) and look under Windows Logs > System for errors with source Service Control Manager around the time you tried to start Defender. The error code there is the most direct clue.
  • Keep Windows Update current; many Defender failures are fixed by cumulative updates.
  • If you have a laptop, make sure the date and time are correct. Wrong system time can break certificate validation for Defender updates.

Troubleshooting

If the steps above don’t work, try these targeted checks:

  • Error 577: This means a file is corrupted. Run sfc /scannow and DISM again, then check the ImagePath registry key for typos.
  • Error 1079: The service’s log-on account is wrong. In the service’s Properties, go to the Log On tab, select Local System account, and check Allow service to interact with desktop. Apply and restart.
  • Error 1053: The service didn’t respond in time. This often means a driver conflict. Boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Advanced options > Startup Settings > Restart > press 4). In Safe Mode, try starting the service. If it works, a third-party driver is the culprit – use msconfig to disable non-Microsoft services and startup items, then reboot normally.
  • Group Policy blocks Defender. Press Win + R, type gpedit.msc (Pro/Enterprise only). Navigate to Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus. Ensure Turn off Microsoft Defender Antivirus is set to Not Configured or Disabled.
  • If nothing works, use the Windows Update Catalog. Search for the latest Windows Defender platform update (e.g., “Microsoft Defender Antivirus for Windows”) and install the appropriate .msu file manually. This can replace a broken engine.

Frequently Asked Questions

Why does Windows Defender keep stopping after I start it?

This usually means a dependency is crashing, or another security program is forcing it off. Check the Event Viewer for the exact error, and make sure no leftover antivirus drivers are present.

Can I fix this without admin rights?

No. Starting, stopping, or repairing system services requires administrator privileges. If you’re on a work or school PC, contact your IT department.

Will I lose my files if I do a repair upgrade?

No, a repair upgrade (using the Installation Assistant) keeps all personal files, apps, and most settings. However, it’s wise to back up to an external drive before doing it.

Is it safe to use third-party antivirus while Defender is broken?

Yes, but install one reputable product and uninstall it before trying to fix Defender again. Running two antivirus engines simultaneously can cause conflicts and system slowdowns.

How do I know if Defender is actually running?

Open Windows Security (shield icon in the system tray). If it shows a green checkmark under “Virus & threat protection,” it’s active. You can also type Get-Service WinDefend in PowerShell; the status should say Running.

What if the service is missing entirely from services.msc?

This is rare but can happen after a corrupted update. Run the DISM and SFC commands, then the PowerShell re-registration command from Step 8. If it’s still missing, the repair upgrade is the most reliable fix.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →