How to Fix ‘Security Center Service Cannot Be Started’ in Windows 11

When launching Windows Security or opening the Defender dashboard in Windows 11, users may encounter an alert stating: ‘The Windows Security Center service cannot be started’ or ‘Security Center service is turned off.’ Attempting to start the service manually inside services.msc frequently returns ‘Error 1068: The dependency service or group failed to start’ or ‘Error 1079: The account specified for this service is different from the account specified for other services.’ Because Security Center supervises real-time antivirus protection, firewall integrity, and tamper defence, a failure in this service leaves your workstation vulnerable to threats.

Root Causes of Security Center Service Failures

The Windows Security Center service (wscsvc) operates as an intermediary broker monitoring system security states. Common causes of stoppage include:

  • Disabled Dependency Services: Security Center relies strictly on the Remote Procedure Call (RPC) and Windows Management Instrumentation (WMI) services. If either dependency is disabled or corrupted, Security Center cannot launch.
  • Corrupted WMI Repository: Inconsistent or damaged WMI database files preventing system services from querying hardware and security telemetry.
  • Registry Permission Tampering: Malware infections or aggressive third-party optimisation utilities modifying the startup type or access control lists (ACLs) under the wscsvc registry keys.
  • Third-Party Antivirus Uninstallation Leftovers: Legacy security software uninstallers failing to release system hooks, leaving registry keys configured in a disabled state.

Step 1: Verify and Configure Service Dependencies

Security Center cannot execute if its prerequisite background services are inactive or misconfigured.

  1. Press Win + R, type services.msc, and press Enter to open the Services Management Console.
  2. Locate Remote Procedure Call (RPC) in the alphabetical list. Verify that its status reads Running and its startup type is set to Automatic.
  3. Locate Windows Management Instrumentation (WMI). Ensure its status is Running and startup type is set to Automatic. If it is stopped, right-click and select Start.
  4. Scroll down to find Security Center.
  5. Right-click Security Center, select Properties, and verify the Startup type. If the options are greyed out, administrative registry repair is required in the next step.

Step 2: Restore Default Security Center Registry Keys

If third-party tools or malware modified the service startup configuration, resetting the registry settings restores default Windows operation.

  1. Press Win + R, type regedit, and press Ctrl + Shift + Enter to launch the Registry Editor as an administrator.
  2. Navigate to the following registry path:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc
  3. In the right-hand pane, locate the DWORD value named Start.
  4. Double-click Start and set its value data to 2 (which corresponds to Automatic delayed start).
  5. Locate the DWORD value named DelayedAutoStart and ensure its value is set to 1.
  6. Close the Registry Editor and restart your computer to apply the service configuration.

Step 3: Repair the Windows Management Instrumentation (WMI) Repository

If WMI repository corruption prevents the service from querying system components, rebuilding the repository resolves Error 1068.

  1. Press Win + X and select Terminal (Admin) or Command Prompt (Admin).
  2. Check the integrity of the WMI database:
    winmgmt /verifyrepository
  3. If the output returns ‘WMI repository is inconsistent’, execute:
    winmgmt /salvagerepository
  4. If the repository remains unreadable, perform a complete reset:
    net stop winmgmt /y
    winmgmt /resetrepository
    net start winmgmt
  5. Reboot your workstation and check if Security Center launches normally.

Step 4: Execute System File Checker and DISM Deployment Scans

Damaged operating system binaries and corrupted security service DLLs must be repaired using native Windows deployment tools.

  1. Open an elevated Command Prompt or PowerShell window as an administrator.
  2. Run the Deployment Image Servicing and Management (DISM) tool to repair the local component store:
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Once DISM finishes at 100%, execute the System File Checker scan:
    sfc /scannow
  4. Allow the scan to detect and replace damaged system binaries from the pristine Windows component store.
  5. Restart Windows 11 upon completion. The Windows Security Center service will now start automatically.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.