If System Restore has been stuck at "Preparing 4%" for 2 hours, the safer next step is to stop waiting and return to Windows Recovery Environment, then try other recovery options one at a time. A restore or repair process can take time, but being stuck that long at the same percentage usually means it is not progressing.
Recommended order:
- Power off the PC
- Hold the power button until the PC shuts down.
- This can interrupt recovery, so there is some risk, but remaining indefinitely at the same percentage is not useful.
- Boot back into WinRE
- Start the PC and enter the recovery options.
- If needed, use Windows installation media and select Next > Repair your computer > Troubleshoot.
- Run Startup Repair first
- In WinRE, go to Troubleshoot > Advanced options > Startup Repair.
- This tool is designed to fix common startup problems such as damaged system files, corrupted boot configuration data, damaged MBR, incompatible drivers, and registry errors.
- After it finishes, shut down and test a normal boot.
- Check the Startup Repair log
- If Startup Repair fails again, review:
%windir%\System32\LogFiles\Srt\SrtTrail.txt - That log can help identify whether the issue is a corrupted boot file, driver, or system file.
- If Startup Repair fails again, review:
- Try offline system file repair
- In WinRE, open Command Prompt and run:
SFC /Scannow /OffBootDir=C:\ /OffWinDir=C:\Windows- This checks and repairs Windows system files offline.
- If disk corruption is suspected, run Check Disk
- In the same Command Prompt, run:
chkdsk /f /r- Warning: this can take a long time on large or damaged drives.
- If recovery options continue to fail, try uninstalling recent changes or resetting the PC
- In WinRE, use other available recovery options such as uninstalling the latest update, Safe Mode, or Reset this PC.
- If reset is used, choose the option that keeps personal files if needed.
Because the problem started with display behavior changing and then moved into SrtTrail.txt startup repair failure, the issue is more likely a Windows startup, boot, driver, or system file problem than a monitor problem.
References: