How to Fix Windows Security Can’t Be Started

Fix Windows Security in this order: reset the app first, then start or repair the Security Center service, then run file repair tools. Skip that order, and Defender can stay off, virus scans can fail, and security alerts can disappear. This guide gives the exact checkpoints for Windows 10 and 11, so you can stop at the first fix that works.

Likely causes of the Windows security startup failure

The problem commonly comes from one of three places: the Windows Security interface is damaged, the Security Center service is stopped or disabled, or Windows system files are damaged enough to block both. Start with a restart, then open Windows Security from the Start menu to see if the fault sits in the app or the service.

Likely causes

• Most often, the Windows Security app itself is corrupt or stuck on a blank white or gray screen.
• The Security Center service, wscsvc, may be stopped, disabled, or blocked from starting.
• The protocol handler behind the windowsdefender link can be broken, which can trigger the “You’ll need a new app to open this windowsdefender link.” message.
• System file damage can stop the app, the service, or both.
• Less commonly, policy or management settings can block security controls on a managed PC.

If the Windows Security window opens as a blank gray panel and closes a second later, start with the app path. If the app will not open at all and Settings says the Security Center service is unavailable, start with the service path instead.

Fixes in order

Why the Security Center service won’t start

The Security Center service watches antivirus and firewall status, and its service name is wscsvc. It should not be disabled. On most systems, the startup type should be Automatic or Automatic (Delayed Start), and the service should show as running after you start it.

Check the service in services.msc

1. Press Win + R, type services.msc, and press Enter.
2. Find Security Center in the list.
3. Open its properties and check the Startup type.
4. Set it to Automatic or Automatic (Delayed Start).
5. Select Start, then close the window and restart Windows.

What to verify after the restart

Go back to services.msc and confirm that Security Center still uses the startup type you chose and that its status reads Running. Then open Windows Security from Start. If the service starts but the app still shows a blank screen, move to the app repair path next.

Can you repair the Windows Security app?

Yes, if the UI layer is the problem. Windows Security uses the SecHealthUI package, and that package can be repaired or re-registered when the interface will not open, crashes instantly, or shows a blank screen. If the app repair path is missing on your build, skip to the PowerShell method.

Try the available app repair path first

1. Open Settings > Apps > Installed apps.
2. Search for Windows Security.
3. If Advanced options appears, choose Repair before Reset.
4. Reopen Windows Security from Start after each step.

Re-register SecHealthUI with PowerShell

1. Right-click Start and open Windows PowerShell (Admin) or Terminal (Admin).
2. Run: Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage.
3. If that command is not available or fails, use the older Windows 10 registration command for the package instead.
4. Restart the PC, then open Windows Security again from the Start menu.

What to do if re-registration fails

If the package command fails again, do not keep repeating it. Run the system file checks next. A failed re-registration attempt often means the app problem is only a symptom of deeper OS damage.

How do you fix system file damage?

Run DISM first, then SFC. That order matters because DISM repairs Windows component integrity, and SFC checks protected system files after the component store is in better shape. Use both from an elevated command prompt or elevated PowerShell.

Run DISM /RestoreHealth first

1. Open Command Prompt (Admin) or Terminal (Admin).
2. Run: DISM /Online /Cleanup-image /Restorehealth.
3. Wait for it to complete fully before closing the window.
4. Restart if Windows asks for it.

Run SFC as administrator next

1. Open the same elevated command window again.
2. Run: sfc /scannow.
3. Let it finish, even if it takes a while.
4. Restart Windows and open Windows Security from Start.

Picture a machine that opens Windows Security only after a reboot, then fails again after a large update. That pattern usually points to file damage, not a one-time app glitch. If DISM and SFC repair the image, the app should start normally after the restart.

What if policy or registry blocks it?

If the service still will not start, a policy setting or management tool may be blocking it. Use the registry only as a last-resort check, and be careful on managed or hardened systems. A forced registry edit can be overwritten by policy.

Check the wscsvc registry key only if needed

1. Press Win + R, type regedit, and press Enter.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc.
3. Check the Start DWORD.
4. If it is disabled by mistake, change it back to 2, then close Registry Editor.
5. Restart the PC and verify the service in services.msc.

Confirm whether management tools are involved

If the device belongs to an employer or school, group policy or endpoint management may control the service. In that case, local changes may revert after reboot. If the service is still blocked after a clean reboot, skip repeated registry edits and move to the repair install step.

When should you use a repair install?

Use a repair install when DISM, SFC, service checks, and app re-registration have all failed, or when the Security Center service keeps disappearing or refusing to start. This is the better next move when lower-level repairs stop changing the result.

What it can preserve

A repair install, also called an in-place upgrade, replaces the OS files while keeping files and most settings. It can clear stubborn Windows Security damage without wiping the machine. That makes it a strong option for both Windows 10 and Windows 11 when the built-in checks no longer help.

What to confirm after the upgrade

1. Open services.msc and confirm Security Center still starts.
2. Open Windows Security from Start and confirm it displays normally.
3. Run a manual virus scan if the interface opens correctly.

If the issue keeps returning after updates, check whether third-party antivirus software is replacing Windows Security status reporting or disabling the service.

Frequently asked questions

How to fix windows security service can t be started

Open services.msc, find Security Center, and set the startup type to Automatic or Automatic (Delayed Start). Then start the service and restart Windows. If it still will not start, run DISM /Online /Cleanup-image /Restorehealth followed by sfc /scannow.

How to fix windows security center can t be started

First check whether the Windows Security app opens from Start. If it does not, repair or re-register Microsoft.SecHealthUI. If the app opens but reports a service problem, use services.msc to start wscsvc and confirm its startup type after reboot.

How to fix windows security center service can t be started windows 10

On Windows 10, the same service path applies. Open services.msc, set Security Center to Automatic (Delayed Start) if needed, then restart. If the service still fails, run DISM /Online /Cleanup-image /Restorehealth and sfc /scannow from an elevated command window.

How to fix windows security center service can t be started windows 11

On Windows 11, start with the same order: open Start, try Windows Security, then check services.msc for wscsvc. If the service is disabled, change it back and reboot. If the UI is blank or crashes, re-register Microsoft.SecHealthUI with PowerShell.

How to fix windows security not opening

If the window will not open at all, treat it as an app-layer problem first. Try the app repair path if it appears in Settings, then use the PowerShell package command. If that fails, move to DISM /Online /Cleanup-image /Restorehealth and sfc /scannow.