Windows Security Service Started and then Stopped in Windows 11

After installing the Windows 11 22H2 update, the Windows Security dialog may not launch. It may show a blank page, as shown below:

windows security is blank

Also, when you attempt to start the Windows Security Service (“SecurityHealthService“) using the Services MMC console, the following error occurs:

The Windows Security Service service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

securityhealth service not starting

Cause

The above issues occur if the registry points to an old or non-existent path for the Security Health core files. On Windows 11 22H2, the Security Health Service files are located in the C:\Windows\System32 directory. Here are the module names:

  • SecurityHealthAgent.dll
  • SecurityHealthCore.dll
  • SecurityHealthHost.exe
  • SecurityHealthProxyStub.dll
  • SecurityHealthService.exe
  • SecurityHealthSSO.dll
  • SecurityHealthSsoUdk.dll
  • SecurityHealthSystray.exe
  • SecurityHealthUdl.dll

On some systems, the “CoreLocation” registry value may be pointing to the SecurityHealth platform folder (which causes the problem in 22H2 and higher), such as the one below:



\\?\C:\Windows\System32\SecurityHealth\1.0.2207.20002-0

As a result, the Security Health service tries to load outdated modules and fails to start.

Solution

To resolve the Windows Security Service (“SecurityHealthService“) service startup error, follow these steps:

  1. Download w11-sechealth-location.reg and save it to the desktop.
  2. Launch Regedit.exe as TrustedInstaller.
  3. From the File menu in the Registry Editor, click Import… and import the REG file.
  4. Exit the Registry Editor.
  5. Attempt to start the Windows Security Service now.

INFO: REG file contents

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Security Health\Platform]
"CoreLocation"="\\\\?\\C:\\Windows\\System32"

Note that the above fix is especially applicable for Windows 11 systems that have been upgraded to version 22H2.


One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

Leave a Comment