The error indicates that SecurityHealthSSO.dll (part of Windows Security / SecurityHealthSystray) is corrupted or not loading correctly, so Windows Security stays black and the tray process shows a Bad Image dialog.
Use the built‑in repair tools first, then check for disk or driver issues that might have caused corruption.
- Run System File Checker (repairs corrupted system files)
- Open Start.
- Type cmd, right‑click Command Prompt > Run as administrator.
- Run:
sfc /scannow - Wait for it to complete and follow any on‑screen guidance.
- Run DISM to repair the component store (if SFC reports problems it can’t fix)
- In the same elevated Command Prompt, run:
DISM /Online /Cleanup-Image /RestoreHealth - After it finishes, run
sfc /scannowagain.
- In the same elevated Command Prompt, run:
- Check the system drive for file‑system errors
- Open File Explorer.
- Right‑click the C: drive > Properties > Tools tab.
- Under Error checking, select Check and let Windows scan and fix errors.
- If prompted to schedule a scan at next restart, accept and reboot.
- Run a deeper disk check
- Open an elevated Command Prompt again.
- Run:
chkdsk C: /f /r - Approve running at next reboot, then restart and let it complete. This looks for bad sectors and repairs logical errors that can corrupt system files.
- Ensure Windows and drivers are fully updated
- Go to Settings > Update & Security (Windows 10) or Windows Update (Windows 11).
- Select Check for updates and install all available updates, including optional driver/firmware updates for storage and chipset.
- If the problem persists
If
SecurityHealthSystray.exeand Windows Security are still broken after SFC/DISM and disk checks, perform an in‑place repair of Windows (setup from the current Windows 11 ISO and choose Keep personal files and apps). This replaces all system files, including the SecurityHealth components, while preserving data and installed apps.
If none of these steps resolve the issue, back up important data and consider a clean reinstall of Windows on the NVMe drive, as persistent STATUS_IMAGE_CHECKSUM_MISMATCH‑type errors are often due to deeper corruption that a full reinstall can clear.
References: