What the Windows Security page not available error means
If you are trying to open Windows Security and see that the page is unavailable, Windows Defender Antivirus or one of its supporting components is usually blocked, disabled, or misconfigured.
This guide explains how to fix Windows Security page not available by checking services, app registration, policy settings, and system files.
The issue can affect Windows 11 and Windows 10 after a malware infection, a failed update, a third-party antivirus install, or a registry or group policy change.
In many cases, the fix is straightforward once you identify whether the problem is caused by Microsoft Defender, the Security app, or Windows itself.
Common causes of the error
- Third-party antivirus software has disabled Microsoft Defender Antivirus.
- Required Windows services are stopped or set incorrectly.
- The Windows Security app is corrupted or unregistered.
- Group Policy or registry settings are blocking security features.
- Windows Update or system file corruption has broken the Security app.
- Device management software or a work profile is controlling security settings.
Check whether another antivirus is installed
Microsoft Defender often turns off parts of Windows Security when a third-party antivirus is installed.
That does not always cause an error, but it can lead to missing or unavailable security pages.
- Open Settings > Apps > Installed apps.
- Look for products such as Norton, McAfee, Bitdefender, Avast, Kaspersky, ESET, or Trend Micro.
- Uninstall the antivirus if you no longer need it.
- Restart the PC and open Windows Security again.
If you removed third-party antivirus software recently, use the vendor’s removal tool if available.
Standard uninstallers can leave behind drivers or services that continue to interfere with Microsoft Defender.
Restart the required Windows services
Several services must run for Windows Security to load correctly.
If one stops, the page may appear unavailable or blank.
Services to verify
- Security Center or wscsvc
- Microsoft Defender Antivirus Service or WinDefend
- Windows Security Service where available
- Base Filtering Engine
- Windows Management Instrumentation
How to check the services
- Press Win + R, type services.msc, and press Enter.
- Find each service listed above.
- Double-click the service and set Startup type to Automatic or Manual where appropriate.
- If the service is stopped, select Start.
- Restart the computer and test Windows Security again.
Do not disable these services unless a managed IT policy specifically requires it.
They are essential for Microsoft Defender and system security notifications.
Reset or repair the Windows Security app
The Windows Security interface is part of the modern Windows app system, so app corruption can break the page without affecting the entire operating system.
Repairing or resetting the app is one of the quickest ways to restore the UI.
- Open Settings > Apps > Installed apps.
- Search for Windows Security.
- Select the app, then open Advanced options.
- Choose Repair first.
- If the issue remains, choose Reset.
Afterward, open the app from the Start menu or by searching for Windows Security.
If the page still says it is unavailable, the problem is likely deeper than the app itself.
Run Microsoft Defender and system file repairs
Corrupt system files can prevent Windows Security from loading its pages and services.
Windows includes built-in repair tools that often fix the underlying problem.
Run System File Checker and DISM
- Open Command Prompt as an administrator.
- Run: sfc /scannow
- When it finishes, run: DISM /Online /Cleanup-Image /RestoreHealth
- Restart the computer after both commands complete.
SFC scans protected Windows files and replaces damaged copies.
DISM repairs the Windows image that SFC uses as a source, which is especially helpful after failed updates or component store corruption.
Check Group Policy and registry restrictions
On some systems, Windows Security is unavailable because policy settings are disabling Microsoft Defender features.
This is common on work-managed devices, but it can also happen after manual tweaks or security optimization tools.
Group Policy settings to inspect
- Turn off Microsoft Defender Antivirus
- Hide the Virus and threat protection area
- Disable Windows Security Center
- Real-time protection restrictions
Open the Local Group Policy Editor with gpedit.msc if your edition supports it.
Review policies under Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Antivirus and Windows Security.
Registry locations that may block the page
If your system does not include Group Policy Editor, or if a registry change was made directly, check for policy values that disable Defender.
Common locations include HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender and related Windows Security policy paths.
Before editing the registry, create a restore point or export the key.
Deleting the wrong value can create a bigger problem than the one you are fixing.
Make sure Windows is fully updated
Microsoft frequently ships Defender and Windows Security fixes through Windows Update.
Missing cumulative updates can leave the Security app out of sync with the operating system.
- Open Settings > Windows Update.
- Select Check for updates.
- Install all available updates, including optional quality updates if appropriate.
- Restart the device after installation.
If Windows Update itself is failing, the system may need its update components repaired before Windows Security can be restored.
Re-register the Windows Security app with PowerShell
When the app package registration is damaged, re-registering the Windows Security package can restore the missing page.
This is especially useful when the app opens but sections do not load correctly.
- Open PowerShell as an administrator.
- Run: Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage
- If that command is unavailable on your build, try re-registering the app package through the installed AppX manifest.
- Restart the system and open Windows Security again.
Because package behavior varies by Windows build, some commands work better on Windows 11 than older Windows 10 versions.
If one method fails, use app repair, SFC, or DISM before trying more advanced steps.
Test in Safe Mode or with a new user account
If Windows Security works in a different context, the issue may be linked to a damaged user profile or a startup conflict.
Testing in Safe Mode or with a new account helps isolate the cause.
- Safe Mode can reveal whether third-party startup software is interfering.
- A new local user account can show whether the original profile is corrupted.
- If Windows Security works in the new account, migrate your data and settings to the new profile.
This step is particularly useful when the rest of Windows seems stable but the Security page continues to fail in one account only.
When to use advanced recovery options
If none of the standard fixes restore Windows Security, the operating system may have deeper corruption or management restrictions.
In that case, use a repair install, system restore, or full reset depending on your environment and backup status.
- System Restore can roll back recent changes that broke Defender.
- In-place repair upgrade keeps files and apps while reinstalling Windows components.
- Reset this PC is a last resort if system corruption is widespread.
On managed devices, contact the administrator if security settings are enforced by Intune, Microsoft Entra ID, or domain Group Policy.
Local fixes may not override enterprise policies.
Quick checklist for the most effective fixes
- Uninstall conflicting antivirus software.
- Restart Security Center and Microsoft Defender services.
- Repair or reset the Windows Security app.
- Run SFC and DISM.
- Check policy settings that disable Defender.
- Install the latest Windows updates.
- Test with a new user profile if needed.
If you follow this order, you will usually identify how to fix Windows Security page not available without resorting to a full reinstall.
The most common causes are service failures, policy restrictions, and app corruption, so start there before moving to advanced recovery steps.