The Windows Security app is the user interface that surfaces Microsoft Defender Antivirus, Windows Defender Firewall, Device Health, and related security features in one place. When the app fails to open, crashes on launch, or shows a blank white window, the Defender protection services themselves may still be running correctly. The app and the underlying services are separate components.
This distinction matters because the fix for ‘the app won’t open’ is different from ‘Defender is disabled.’ This guide covers both, starting with diagnosing which problem you actually have.
App vs Service: Understanding What Actually Broke
The Windows Security app (SecurityHealthHost.exe, the UWP interface) is a separate component from the Microsoft Defender Antivirus service (WinDefend) and the Security Center service (wscsvc). When the app crashes or won’t open:
- Your real-time protection may still be active even though the app is inaccessible
- The underlying Defender service (WinDefend) may be running normally
- The app’s local data or package may be corrupted independently of the service
When the service has a problem:
- Real-time protection is actually off or degraded
- The taskbar shield icon may show a warning
- The Action Center may show security alerts
Quick test: open Task Manager (Ctrl+Shift+Esc) and look for ‘Antimalware Service Executable’ or ‘MsMpEng.exe’ in the Processes tab. If it is running, Defender is active regardless of whether the app opens. If it is absent, the service itself has a problem.
Common Causes
- Corrupted UWP app package: The Windows Security app is a Universal Windows Platform (UWP) app. Like other UWP apps, its package files can become corrupted by interrupted updates, disk errors, or system file issues.
- Third-party antivirus conflict: Installing a third-party AV product (Norton, McAfee, Avast, Kaspersky, ESET) disables Defender and can leave the Windows Security app in an inconsistent state, particularly during the transition period after installation or removal.
- Dependent service not running: The Windows Security app depends on the Security Center service (wscsvc) and the Windows Management Instrumentation (WMI) service. If either is stopped or failed, the app may not launch correctly.
- Pending Windows Update requiring restart: Some Windows Updates require a reboot to complete. The Security app can appear broken while an update is in a pending state.
- Corrupted system files: Core Windows system files needed by the Security app may be corrupted, something SFC and DISM can detect and repair.
- User profile corruption: In some cases, the issue is isolated to one user profile’s app state while other user accounts work fine.
Fix 1: Restart the Required Services
The fastest fix to try. The Windows Security Center service and its dependencies can be restarted without a reboot.
| # Restart the Security Center service (run PowerShell as Administrator):
> Restart-Service -Name wscsvc -Force
# If wscsvc won’t restart, start its dependencies first: > Start-Service -Name RpcSs # Remote Procedure Call > Start-Service -Name EventLog # Windows Event Log > Restart-Service -Name wscsvc -Force
# Restart the Defender service: > Start-Service -Name WinDefend
# Verify services are running: > Get-Service wscsvc, WinDefend | Select-Object Name, Status |
After restarting the services, try opening Windows Security again. If it opens, a service that had stopped is the cause, and the above commands can be added to a startup script if the problem recurs.
Fix 2: Re-register the Windows Security App Package
If the services are running but the app still won’t open, the UWP app package itself may be corrupted. Re-registering it restores the app without losing data.
| # Re-register the Windows Security app (run PowerShell as Administrator):
> Get-AppxPackage -AllUsers Microsoft.SecHealthUI | ` Foreach {Add-AppxPackage -DisableDevelopmentMode -Register ` “$($_.InstallLocation)\AppXManifest.xml”}
# If the above fails, try the broader approach for all provisioned apps: > Get-AppxPackage -AllUsers | Foreach { > Add-AppxPackage -DisableDevelopmentMode -Register ` “$($_.InstallLocation)\AppXManifest.xml” 2>$null > }
# Restart Windows Security after running: > Start-Process “windowsdefender://” |
Fix 3: Check for Third-Party Antivirus Conflicts
When a third-party antivirus product is installed, Windows Defender Antivirus is typically placed in a passive mode or disabled. The Windows Security app should reflect this state correctly, but the transition is not always clean. Common conflict scenarios:
- Third-party AV recently installed: the Security app may not have updated its status correctly. Restart the machine and allow time for the status to sync.
- Third-party AV recently removed: after uninstalling a third-party AV, Defender should re-enable automatically. If it does not, the registry entries left by the removed AV may be preventing Defender from starting. Run Windows Defender’s PowerShell reset or use the Windows Security Troubleshooter.
- Multiple AV products installed: having two active AV products causes conflicts. Check Programs and Features (appwiz.cpl) and remove any AV products you no longer use.
After uninstalling a third-party AV, restart the computer. Defender typically re-enables within a few minutes after the reboot. If the Security app still shows issues after a restart, check whether the uninstaller left behind services (check Services.msc for any service names associated with the removed product) and remove them if present.
Fix 4: Repair Windows System Files
System File Checker (SFC) and DISM (Deployment Image Servicing and Management) repair corrupted Windows system files. SFC checks and restores files from a cached copy; DISM restores the Windows component store that SFC uses. Run DISM first so SFC has a good base to work from.
| # Run DISM to restore the component store (takes 5 to 15 minutes):
> DISM /Online /Cleanup-Image /RestoreHealth
# After DISM completes, run SFC: > sfc /scannow
# SFC output will indicate whether it found and repaired corrupted files. # Reboot after either tool makes repairs.
# Both commands must be run as Administrator. |
Fix 5: Install Pending Windows Updates
A Security app that appears to crash or show a blank window is a known symptom of a Windows Update that has been downloaded but not yet installed. The app requires a restart to complete the update installation before it can operate correctly.
Open Settings > Windows Update and check for any updates with a pending restart indication. If a restart is pending, save your work and restart. After the restart, open Windows Security again. If the update was the cause, the app will work correctly.
If Windows Update itself is broken or showing errors, run the Windows Update Troubleshooter (Settings > System > Troubleshoot > Other troubleshooters > Windows Update) before attempting to install updates.
Fix 6: Reset the Windows Security App
Resetting the app clears its local state and cached data without uninstalling it. This is useful when the app opens but shows incorrect information, hangs during loading, or displays persistent errors that don’t match the actual system state.
Open Settings > Apps > Installed apps. Find Windows Security in the list (or search for it). Click the three-dot menu next to it and select Advanced options. On the Advanced options page, click Reset. Confirm the reset. Launch Windows Security again after the reset completes.
App Reset clears the app’s local settings and cache. It does not affect Defender’s protection configuration, scan history, or exclusion lists, which are stored in separate locations. Your security settings are preserved.
Fix 7: Test with a New User Account
If all other fixes have not resolved the issue, create a new local administrator account and test whether Windows Security opens correctly under that account. If it opens cleanly for the new account but not for yours, the issue is isolated to your user profile’s app state.
Create a new account via Settings > Accounts > Family and other users > Add someone else to this PC > I don’t have this person’s sign-in information > Add a user without a Microsoft account. After creating the account, sign out and sign in with the new account. Open Windows Security.
If the app works in the new account, you can either migrate your data to the new profile or attempt to repair the original profile by rebuilding the LocalCache for UWP apps (which requires backing up and removing the original profile’s LocalCache\Packages\Microsoft.SecHealthUI folder).
When to Be Concerned vs Normal Issues
| Symptom | Concern level | Interpretation |
| App won’t open but Defender service is running | Low | App package issue, not a security gap; fix at convenience |
| App opens but shows all protections as Off | High | Defender may actually be disabled; check WinDefend service status |
| Tamper Protection toggle is greyed out | Medium | May indicate third-party AV conflict or Group Policy restriction; investigate |
| App says ‘No antivirus providers’ after removing third-party AV | Medium | Defender not re-enabled after third-party removal; restart machine, then re-register Defender |
| App crashes immediately after Windows update | Low to medium | Usually resolved by completing the update with a restart; if persists, run SFC/DISM |
| App stopped working suddenly on a previously stable system | Medium to high | Check for malware; some malware disables the Security app deliberately |
Frequently Asked Questions
If the app is broken, is my computer unprotected?
Not necessarily. As noted, the app and the protection services are separate. If MsMpEng.exe (Antimalware Service Executable) is running in Task Manager, real-time protection is active even if the app UI is broken. However, a broken app means you cannot see protection status, adjust settings, or respond to threat notifications. Fixing the app is important for maintaining visibility into your security posture, even if the underlying protection is currently working.
Can I reinstall Windows Security like a regular app?
Windows Security cannot be uninstalled and reinstalled through the normal app removal process because it is a core Windows component. The re-registration command in Fix 2 is the equivalent of a reinstall for UWP apps. If that does not resolve the issue, an in-place upgrade (running Windows Setup while keeping files and apps) reinstalls all Windows components including Windows Security while preserving your data and most application settings.
The app shows a blank white screen when opened. What causes that?
A blank white screen typically means the app process started but the UI failed to render. This is usually caused by a corrupted app package (Fix 2 resolves this), a pending Windows Update that the app is waiting on (Fix 5), or a display driver issue affecting UWP rendering. Try the re-registration command first. If the blank screen persists after Fix 2, check for pending updates. If both fail, running SFC and DISM (Fix 4) and then rebooting typically resolves the rendering issue.
Gloria Bradford is a renowned expert in the field of encryption, widely recognized for her pioneering work in safeguarding digital information and communication. With a career spanning over two decades, she has played a pivotal role in shaping the landscape of cybersecurity and data protection.
Throughout her illustrious career, Gloria has occupied key roles in both private industry and government agencies. Her expertise has been instrumental in developing state-of-the-art encryption and code signing technologies that have fortified digital fortresses against the relentless tide of cyber threats.