The “Unknown Hard Error” message in Windows 11 is one of those cryptic popups that tells you almost nothing. Sometimes it appears on a black screen during boot with an OK button that does nothing. Other times it flashes briefly during shutdown, or shows up tied to a process name like sihost.exe, explorer.exe, or ctfmon.exe. The cause is almost always corrupted system files, a bad disk sector, a broken user profile, or a misbehaving third-party app.

⚡

Quick answer: If Windows boots, run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt, then reboot. If Windows is stuck on the error at boot, force three failed startups in a row to trigger the Windows Recovery Environment and run Startup Repair.

If you can’t get past the error screen

When the popup appears before you can sign in and clicking OK does nothing, you need the Windows Recovery Environment (WinRE). Windows 11 will boot into it automatically after detecting repeated startup failures.

Power on the PC. As soon as you see the spinning dots under the Windows logo, press and hold the power button for 5 to 10 seconds to force a hard shutdown.

Repeat that hard shutdown a second time on the next boot attempt.

On the third power-on, let the system boot. It should land on a “Preparing Automatic Repair” screen and then open the recovery environment.

Choose Troubleshoot → Advanced options → Startup Repair. Let it run; it can fix boot configuration and basic file corruption automatically.

If Startup Repair fails, return to Advanced options and pick Command Prompt or Startup Settings → Safe Mode to continue with the file and disk repairs below.

Microsoft documents the same WinRE entry points and recovery flows on its recovery options page.

Repair corrupted system files with SFC and DISM

Most “Unknown Hard Error” popups tied to sihost.exe or explorer.exe trace back to damaged system files. System File Checker and DISM repair the protected Windows image and replace bad components.

Press the Windows key, type cmd, then right-click Command Prompt and pick Run as administrator.

Run the System File Checker and wait for it to finish. Do not close the window mid-scan.


sfc /scannow

If SFC reports it could not fix everything, run the three DISM commands in order. The last one downloads replacement files from Windows Update, so an internet connection helps.


DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

Reboot and watch for the popup. A successful repair shows the “Windows Resource Protection successfully repaired corrupted files” or “The restore operation completed successfully” message.

Check the disk for bad sectors

Bad sectors and file system corruption can also throw the error, especially on aging SATA drives or after a sudden power loss. CHKDSK scans the volume and attempts to recover readable data from problem areas.

Open Command Prompt as administrator again.

Run the check on your system drive.


chkdsk C: /f /r

When prompted that the volume is in use, type Y and press Enter to schedule the scan at the next reboot.

Restart the PC and let CHKDSK finish all five stages before Windows loads. On large or slow drives this can take an hour or more.

Isolate third-party software with a clean boot

If the error returns after file and disk repair, a startup service or app is likely the trigger. Antivirus suites and system tweaking utilities are common culprits; a known case had Kaspersky causing the popup on shutdown until it was removed.

Press Win + R, type msconfig, and press Enter.

On the General tab, select Selective startup and uncheck Load startup items.

Switch to the Services tab. Tick Hide all Microsoft services at the bottom, then click Disable all.

Open Task Manager (Ctrl + Shift + Esc), go to the Startup apps tab, and disable every entry.

Click Apply and OK in System Configuration, then restart. If the error is gone, re-enable services and startup apps in halves until it returns; the last batch you turned on contains the offender.

When drivers or recent updates are the trigger

Display, storage, and chipset drivers tend to be the most disruptive when out of date or mismatched. The same applies to the latest cumulative Windows update if the popup started right after an install.

Suspected cause	What to do
Outdated GPU driver	Install the latest driver from NVIDIA, AMD, or Intel directly. Skip Windows Update for graphics if a vendor build is newer.
Storage controller driver	Open Device Manager → IDE ATA/ATAPI controllers and Disk drives, right-click each entry and pick Update driver.
Bad Windows update	Settings → Windows Update → Update history → Uninstall updates, then remove the most recent cumulative update.
Corrupted user profile	Settings → Accounts → Other users → Add account, create a local user, sign in there, and see if the error stops.

Last-resort recovery: System Restore and Reset

If targeted repairs don’t stick, roll the system back or rebuild it. Both options are available from inside Windows and from the recovery environment.

System Restore reverts system files, drivers, and the registry to an earlier checkpoint without touching personal files. Press Win + R, type rstrui, and pick a restore point from before the error appeared.

Reset this PC reinstalls Windows 11 in place. Go to Settings → System → Recovery → Reset this PC and choose Keep my files to preserve documents while wiping apps and settings. Use Remove everything only if you want a clean slate or suspect malware.

How to confirm the fix worked

The popup should not return through a normal boot, sign-in, shutdown cycle, and a few hours of regular use. To verify there are no lingering issues, open Event Viewer (Win + R → eventvwr), expand Windows Logs → Application, and look for fresh “Application Error” or “Windows Error Reporting” entries naming the same process that appeared in the popup. A clean log after a reboot is the strongest signal that the underlying corruption or conflict is resolved.

If the error keeps coming back after SFC, DISM, CHKDSK, a clean boot, and driver updates, the most likely remaining suspects are failing storage hardware or RAM. Run the manufacturer’s drive diagnostic and Windows Memory Diagnostic (mdsched.exe) before reinstalling Windows from scratch.