If Windows reports that the Security Center service is not running, your security status may be incomplete or misleading.
This guide explains how to fix Security Center service not running with proven checks, repairs, and recovery steps for Windows 10 and Windows 11.
What the Security Center service does
Security Center, also shown as Windows Security Center or the WSC service, monitors core protections such as antivirus, firewall, and update status.
It does not replace Microsoft Defender Antivirus, but it helps Windows display and coordinate security notifications from built-in and third-party protection tools.
When the service fails, you may see missing alerts, incorrect status messages, or the Windows Security app showing that protection cannot be verified.
In some cases, the issue is caused by a stopped service; in others, a registry problem, corrupted system files, or interference from third-party software is to blame.
Common reasons Security Center stops running
- The service startup type is disabled or configured incorrectly.
- Windows services such as Remote Procedure Call and WMI are not running properly.
- Security Center files or system components are corrupted.
- Third-party antivirus software is blocking Windows security integration.
- Recent Windows updates, driver changes, or malware have damaged service configuration.
- Registry entries for Security Center have been altered by cleanup tools or policy settings.
How to fix Security Center service not running
1. Restart your PC and check the service again
Before making deeper changes, restart Windows.
Temporary service glitches often clear after a clean reboot, especially after updates or software installs.
After Windows loads, open Services, find Security Center, and confirm whether it is running.
2. Start the Security Center service manually
Use the Services console to verify the service state:
- Press Windows key + R, type services.msc, and press Enter.
- Scroll to Security Center.
- Double-click it and set Startup type to Automatic (Delayed Start) or Automatic.
- If available, click Start, then select Apply and OK.
If the Start button is unavailable or the service stops immediately, continue with the next steps.
That usually means another dependency or configuration issue is involved.
3. Verify required dependency services
Security Center relies on core Windows services.
If they are stopped, Security Center may fail to launch correctly.
Check these services in the same console:
- Remote Procedure Call (RPC)
- DCOM Server Process Launcher
- RPC Endpoint Mapper
- Windows Management Instrumentation
These services should normally be running.
If one is stopped, start it if Windows allows it.
Do not disable or force-stop these components, because they are essential for system communication.
4. Run System File Checker and DISM
Corrupted system files are a frequent cause of service failures.
Open Command Prompt as administrator and run these commands one at a time:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
SFC checks protected system files and replaces damaged copies.
DISM repairs the Windows image that SFC depends on.
After both finish, restart the computer and check whether Security Center starts normally.
5. Remove or update third-party antivirus software
Many third-party security suites register themselves with Windows and can interfere with Security Center status reporting.
If you recently installed antivirus software from vendors such as Norton, McAfee, Bitdefender, Kaspersky, or Avast, test whether the service returns after uninstalling or temporarily disabling it.
If you keep a third-party antivirus installed, make sure it is fully updated.
Outdated security software can break the connection between the provider and Windows Security Center.
For a clean test, use the vendor’s official removal tool when available.
6. Check Windows Security Center registry settings
Registry corruption can prevent Security Center from starting or from reporting status correctly.
Before editing the registry, create a restore point or export the relevant keys.
Then open Registry Editor and review the Security Center service entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc
Look for the Start value.
On most systems, it should not be disabled.
If the value is set incorrectly, Windows may never launch the service.
Only change registry values if you are certain of the correct configuration, and avoid deleting keys unless a trusted repair guide specifically instructs you to do so.
7. Scan for malware
Malware can disable Security Center to hide other infections.
Run a full scan with Microsoft Defender and, if needed, an offline scan or a second-opinion scanner from a reputable security vendor.
If Windows Security itself is blocked, use Safe Mode with networking or a bootable rescue scanner.
8. Use the Windows Services reset path in Safe Mode
Safe Mode loads a smaller set of drivers and services, which can help isolate the cause.
If Security Center starts in Safe Mode but not during a normal boot, a startup program, driver, or security app is likely interfering.
Use Task Manager to disable nonessential startup apps, then reboot and test again.
9. Repair Windows with an in-place upgrade
If the service still will not run after standard repairs, an in-place repair install can refresh Windows system components without removing files and most apps.
This is often the best option when corruption is deeper than SFC or DISM can fix.
Use the latest Windows installation media that matches your current version and edition, then choose the option to keep personal files and apps.
How to confirm the fix worked
After each repair attempt, verify the result in two places:
- Services: Security Center should show as running and should not immediately stop.
- Windows Security: Open the app and confirm that antivirus, firewall, and device security statuses load correctly.
You can also check for warning icons in the taskbar or system tray.
If Windows is still showing stale alerts, give the system a minute or two after startup, since security status can take time to populate.
When the issue may be hardware or policy related
On managed PCs, local group policy, enterprise endpoint security, or mobile device management tools may control Security Center behavior.
In those environments, the service can appear broken when it is actually being governed by an administrator policy.
If you are on a work laptop, contact IT before changing advanced settings.
For home users, repeated service failures after repairs may point to broader Windows instability, storage problems, or disk corruption.
Running chkdsk, checking SMART warnings with a disk utility, or reviewing Event Viewer logs can help uncover a deeper system issue.
Useful checks if the service keeps stopping
- Review Event Viewer under Windows Logs for service-related errors.
- Confirm your date, time, and region settings are correct.
- Install the latest cumulative Windows updates.
- Remove recent system-tweaking tools or registry cleaners.
- Test with a new local user account to rule out profile corruption.
These checks help distinguish a one-time glitch from a recurring configuration problem.
If the service works in a new account, the original user profile may be damaged.
Best practices to prevent Security Center problems
Keep Windows updated, avoid unsupported registry edits, and use only one primary antivirus solution at a time.
Regularly reviewing Windows Security after updates helps catch issues early, before the service stops reporting status accurately.
A clean startup environment also reduces the chance that background utilities will disrupt core security services.