Quick fix: Force three failed boots to trigger Recovery Environment, then choose Troubleshoot → Advanced options → System Restore, pick the restore point, and let it run offline. Works when Windows is in such bad shape it can’t boot to the desktop.

Windows won’t boot, or boots to a broken state where you can’t use the Settings app. You know System Restore could fix this — there’s a restore point from before the issue. But you can’t run rstrui from a Windows that won’t start. Recovery Environment (WinRE) provides offline System Restore — runs without booting Windows.

Symptom: Need to run System Restore but Windows won’t boot to the desktop or can’t reach Settings.
Affects: Windows 11 (and Windows 10) in unbootable or partially-broken state.
Fix time: ~30 minutes.

What causes this

System Restore can run in two modes: Online (Windows is booted, you run rstrui from the desktop) or Offline (Windows isn’t running; the restore is performed by WinRE’s standalone restore engine). Offline restore is more reliable because no service is holding files open, no driver is locking the registry. The downside is reaching WinRE requires triggering the recovery flow, which means three consecutive boot failures (Windows interprets this as “something is wrong” and shows WinRE on the next attempt).

Method 1: Trigger Recovery Environment via three failed boots

The standard route. Works when Windows boots at all but you can’t reach Settings normally.

Force shutdown: hold the power button for 10 seconds until the PC powers off.
Wait 5 seconds. Power on.
When the Windows logo or spinning dots appear, force shutdown again with the power button.
Repeat. Total of three failed boots.
On the fourth power-on, Windows enters Recovery Environment automatically. You see the blue Choose an option screen.
Click Troubleshoot → Advanced options → System Restore.
Select your account, enter password if prompted.
The System Restore wizard appears. Click Next to see available restore points.
Pick a restore point from before the issue started. Click Scan for affected programs to see what apps will be removed/restored.
Click Next → Finish. Confirm.
System Restore runs offline. Takes 15-30 minutes. The PC reboots when done.

Offline restore works because no Windows services are running to block file replacement.

Method 2: Boot from installation USB to reach WinRE

Use when Method 1 doesn’t work — three failed boots don’t trigger Recovery Environment, or the PC won’t boot at all.

On a working PC, create a Windows 11 installation USB using the Media Creation Tool from microsoft.com/software-download/windows11.
Plug the USB into the affected PC.
Power on. Press the boot menu key (F12 / F11 / Esc, depending on manufacturer) to select the USB as boot device.
Wait for the Windows Setup screen.
Click Next, then click Repair your computer in the bottom-left corner.
You’re in Recovery Environment — proceed with Troubleshoot → Advanced options → System Restore as in Method 1.
System Restore runs from the USB-booted WinRE, restoring the offline Windows install on the internal drive.

This is the fallback when the PC can’t even fail-boot to trigger automatic Recovery Environment.

Method 3: Use the rstrui command directly from Command Prompt

Use this for finer control over which restore point — particularly when Method 1’s UI doesn’t show the restore points you expected.

Reach Recovery Environment via Method 1 or 2.
Choose Troubleshoot → Advanced options → Command Prompt.
Determine the Windows drive letter:
```
diskpart
list volume
exit
```
Note the letter for the Windows volume (often D: in WinRE, not C:).
Launch System Restore against that volume:
```
rstrui.exe /OFFLINE:D:\Windows=active
```
(Replace D: with your Windows drive.)
The System Restore wizard opens with the offline Windows install as the target. Pick the restore point and proceed.
Exit Command Prompt and reboot when restore completes.

This command-line approach is the supported way to run rstrui in offline mode and gives you more control over which volume gets restored.

How to verify the fix worked

Windows boots to the lock screen normally after the restore.
Open Settings → System → About. Check Installation date and OS Build — the OS should reflect the state from the restore point’s date.
Apps installed after the restore point are gone (System Restore removes them). Apps from before the restore point remain.
Personal files (Documents, Pictures, Downloads) are unaffected by System Restore — they survive untouched.

If none of these work

If System Restore fails or no restore points are available, three remaining options. No restore points exist: System Restore was disabled or restore points were deleted. You can’t restore — move to Uninstall Updates from the same Advanced options menu, or Reset This PC with Keep my files. Restore points exist but System Restore errors: typically 0x80070003 (path not found) or 0x80070005 (access denied). Try a different restore point. If multiple fail, the System Volume Information folder may be corrupted — use a Windows installation USB to do an in-place upgrade install (Keep files and apps). Restore completes but Windows still won’t boot: the issue is more fundamental than the restore could fix. Use the installation USB to perform Startup Repair, then sfc/DISM repairs, then consider Reset This PC.

Bottom line: Offline System Restore through Recovery Environment fixes Windows even when it won’t boot — three failed power-cycles to enter WinRE, then walk through the wizard. Personal files survive untouched.