Windows Security not opening: how to fix it
The Windows Security app is only the front window for Defender. When it won't open, the app package may be damaged or unregistered, system files may be corrupt, or another antivirus may be interfering. Repairing or resetting the app from Settings is the quickest thing to try, and the PowerShell and system file steps cover most of the rest.
On this page
What it means
The Windows Security app (the Microsoft.SecHealthUI package, formerly Windows Defender Security Center) is a window onto your protection. The protection itself is done by separate parts: the Security Center service (wscsvc), SecurityHealthService, and the Defender engine (WinDefend / MsMpEng). So an app that won't open does not automatically mean you are unprotected.
Microsoft has no dedicated troubleshooting article for this problem. The steps below come from Microsoft Q&A volunteer answers and a third-party guide, plus Microsoft's documentation on how Defender behaves next to other antivirus products. None of the causes are confirmed by Microsoft, so go in order and stop when the app opens.
On a work or school device, a policy or Defender for Endpoint may be hiding or restricting the app. Ask your IT team before changing anything there.
Symptoms and causes
You are likely dealing with this problem if:
- Clicking Windows Security in the Start menu or the shield icon in the tray does nothing.
- The window opens and closes at once, or opens blank.
- The message "You'll need a new app to open this windowsdefender link".
- Windows Security is missing from the list of installed apps in Settings, or its tooltip reads "ms-resource:DisplayName".
- A Windows Script Host error 80070002 (reported in one thread).
The usual causes, most common first:
- Corrupt or unregistered app package
- The
Microsoft.SecHealthUIpackage can be damaged or lose its registration, for example after an update or an interrupted update. - Corrupted system files
- Both the Microsoft Q&A thread and the MakeUseOf guide point to damaged Windows files.
- Conflicting or leftover third-party antivirus
- Microsoft says Defender switches to disabled mode when another antivirus is registered. If the Security Center service is disabled, Defender can't see the other product and stays active, which causes conflicts and is not supported.
- Defender or its services disabled or removed
- A user, a tweaking tool or malware may have disabled Defender or removed components.
- Background service or app conflict
- A clean boot can reveal this, according to MakeUseOf and the Q&A thread.
How to fix it
Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.
1.Restart and install pending updates
A half-finished update is a known trigger, so finishing it can be enough.
- Restart the PC.
- Open Settings > Windows Update, click Check for updates, install anything offered, and restart again.
2.Repair, then reset the app from Settings
Repair re-checks the app's files without touching the rest of the system. Reset wipes the app's own data and preferences.
- On Windows 11, open Settings > Apps > Installed apps, find Windows Security, click the ⋯ menu and choose Advanced options. You can also search for "Windows Security" and choose App settings.
- Click Repair and try opening the app.
- If it still fails, click Reset, then restart the PC.
3.Reset the package in PowerShell
Does the same job as the Reset button but works when the Settings page is missing or broken.
- Right-click Start and open Terminal (Admin) or Windows PowerShell (Admin).
- Check the exact package name on your PC. The sources write it two ways, so confirm what Windows reports. The result should show a name containing
SecHealthUIand an install location.Get-AppxPackage *SecHealthUI* -AllUsers | Select Name, InstallLocation - Run the reset command, then restart the PC.
Get-AppxPackage *SecHealthUI* -AllUsers | Reset-AppxPackage
4.Re-register the package
Fixes a package that exists on disk but is not registered. The poster in the Microsoft Q&A thread reported this did not fix their case, so treat it as one more attempt.
Before you start: Create a restore point first (search for Create a restore point). If the name check in the previous solution returned nothing, do not run this command.
- In an admin PowerShell window, run the command below, then reboot. It uses a wildcard so it matches whichever package name your PC reports.
PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage *SecHealthUI*).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"
5.Repair system files with SFC and DISM
Damaged system files are one of the causes named in both the Q&A thread and the MakeUseOf guide.
- Open Command Prompt as administrator and run the three commands one after another. Let each finish before starting the next, then restart.
sfc /scannow DISM /Online /Cleanup-Image /StartComponentCleanup DISM /Online /Cleanup-Image /RestoreHealth
6.Remove leftover third-party antivirus and try a clean boot
A second security product, or its leftovers, can stop Defender and its app from behaving normally.
Before you start: Do not stay without protection. If you uninstall an old antivirus, make sure Windows Security or your chosen product is active afterward. Some Windows Security pages showing "managed by your provider" is normal with third-party antivirus and is not a fault.
- Uninstall the other antivirus, using the vendor's own removal tool if it has one, and restart.
- If the app still fails, do a clean boot (disable non-Microsoft startup items and services using System Configuration), and see whether it opens. If it does, re-enable items in small groups to find the one that conflicts.
- If Defender is meant to be your main antivirus, check its running mode in an admin PowerShell window. Microsoft lists Normal, Passive and EDR Block Mode as states where protection is enabled. The command may also fail if the Defender service itself is damaged, which is useful to know. To see whether the engine is running, you can look for
MsMpEng.exeon the Details tab of Task Manager.Get-MpComputerStatus | select AMRunningMode
7.Use a restore point, or reset Windows as a last resort
Rolls back Windows files when nothing smaller worked.
Before you start: Back up your important files first. A factory reset erases apps and settings, so use it only if nothing else worked.
- Search for Create a restore point, click System Restore and pick a point from before the problem began.
- If that is not possible or does not help, a factory reset is the last resort listed by MakeUseOf.
Check that it worked
- Windows Security opens from the Start menu and from the tray shield icon, and shows its pages instead of a blank window.
- The protection areas such as Virus & threat protection load and show a status.
If it still fails
- If you are on a managed device, ask your IT administrator whether a policy hides or restricts Windows Security.
- Note which step you reached and any error text (such as 80070002), then ask on Microsoft Q&A or contact Microsoft Support with those details.
- If the problem began after disabling Defender or after a security update, mention that when asking for help.
Questions
Am I unprotected if the Windows Security app won't open?
Not necessarily. The app is only the front end. Protection is run by separate services, though a broken app can be a sign that those parts are also damaged or disabled, so it is worth fixing.
Sources
- Windows defender/security app isn't starting · Microsoft Learn Q&A
- Microsoft Defender Antivirus compatibility with other security productsOfficial · Microsoft Learn
- Windows Security app not starting or crashing · MakeUseOf