Run System Restore from the Windows Recovery Environment (WinRE) first, because this performs the rollback outside the normal Windows session and avoids interference from running services or drivers.
1. Retry System Restore from WinRE
- Save open work and back up important files.
- Hold Shift while selecting Start → Power → Restart.
- On Choose an option, select Troubleshoot → Advanced options → System Restore.
- Select the restore point and complete the rollback.
WinRE is included with Windows 11 and supports System Restore, which rolls back system files and settings without rolling back personal files.^1^ A closely matching Windows 11 System Restore failure was resolved by running the rollback from WinRE.^2^
If BitLocker is enabled, have the recovery key available before entering WinRE.^3^
2. If WinRE reports the same error, check the storage and file system
Error 0x800701B1 means “A device which does not exist was specified.”^4^ In this situation, that makes the storage path a priority for investigation; it does not prove that the named WinSxS file is corrupted.
Disconnect nonessential USB storage, docks, and other external hardware. Then open Command Prompt as administrator and run:
chkdsk /f C:
Accept the prompt to schedule the check, then restart. Back up important data first: /f repairs file-system errors rather than performing a read-only scan. Microsoft documents this command for repairing drive errors.^5^
After Windows starts:
- Open Device Manager.
- Expand Disk drives and Storage controllers.
- Look for yellow warning icons.
- If one appears, open Properties → Device status, record the displayed code, and obtain the appropriate storage/chipset driver from the PC or motherboard manufacturer.
Repeated 0x800701B1 errors, disk disappearances, I/O errors, or new crashes justify running the SSD/HDD manufacturer’s health diagnostic and backing up immediately.
3. Repair Windows components
The file merely being present under C:\Windows\WinSxS does not establish that its contents or the component store are healthy. Do not manually delete or replace files in WinSxS.
Open Command Prompt as administrator, then run DISM before SFC:
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
DISM repairs the Windows component image used by SFC; SFC then verifies protected system files and replaces damaged copies where possible.^6^
Interpret the final SFC result as follows:
- No integrity violations: system-file corruption was not detected.
- Corrupt files successfully repaired: restart, then retry System Restore from WinRE.
- Unable to repair some files: preserve the result and consider Windows repair/reinstallation options rather than manually modifying WinSxS.
About the crashes
The failed restore and the crashes may share a storage or driver problem, but this error alone does not establish that relationship. Record the exact stop code and any module name shown during the next crash. If disk checks pass but crashes continue, those details are needed to distinguish a storage failure from a device-driver or software problem.
If the drive diagnostic reports failure or chkdsk reports recurring errors, stop attempting restores, back up the data, and address the drive first. If storage tests pass but WinRE restore still fails, use the least-disruptive applicable recovery option, such as reinstalling the current Windows version where offered, before considering Reset this PC; Microsoft recommends backing up before recovery operations because some options can remove data.^3^
References
- Windows Recovery Environment (Windows RE)
- System restore fails because of Intel iCLSClient - Microsoft Q&A
- Recovery options in Windows
- Utilizing Microsoft Game Development Kit tools to install and launch your PC title
- [Windows 11](https://support.microsoft.com/windows/deployment/updates-lifecycle/troubleshoot-problems-updating-windows#repair-hard-drive-errors)
- Use the System File Checker tool to repair missing or corrupted system files | Microsoft Support