Stuck at boot? Don’t panic—your system isn’t beyond saving. Whether it’s a corrupted system file, bad update, or drive issue, recovery is possible with the right tools. Even when Windows won’t boot, you can still access powerful repair utilities—like DISM and SFC—offline.
In this guide, I’ll walk you through the exact steps to use DISM and SFC from recovery environments, including how to target offline Windows installations.
Step 1: Boot into a Recovery Environment
If your PC won’t boot normally, you have a few ways to enter recovery mode:
• Use a Windows 10/11 Installation USB or Recovery Drive.
• Alternatively, force three failed boots (power on > hard shutdown) to trigger Automatic Repair.
Once in the recovery environment:
1. Choose Advanced Options.
2. Select Command Prompt.
You’re now ready to scan and repair—even if your primary OS isn’t running.
Step 2: Identify Your Windows Partition
To run DISM/SFC offline, you need to locate the drive letter assigned to your Windows install. Use this command:
diskpart
listdiskYou should see multiple disks. You need the operating system disk for example disk 0.
Select disk x (replace x with disk number)
List volumeLook for the familiar Windows folder on one of the volumes—usually `D:` or `C:`, depending on the recovery environment.
Type `exit` to leave Diskpart when you’ve found your target drive.
Step 3: Run DISM Offline
DISM (Deployment Imaging Servicing and Management) repairs the Windows image and prepares the ground for SFC.
Here’s how to use it offline:
dism /image:D:\ /cleanup-image /restorehealthReplace `D:\` with the actual drive letter of your Windows installation.
DISM will scan and attempt to restore health using built-in components on the local image. If needed, you can point it to a separate Windows source using:
dism /image:D:\ /cleanup-image /restorehealth /source:E:\sources\install.wimWhere `E:\sources\install.wim` is a clean image file (from a Windows ISO). You can mount the ISO and browse for the exact path.
Step 4: Run SFC Offline
After DISM completes successfully, it’s time to run System File Checker to fix integrity issues:
sfc /scannow /offbootdir=D:\ /offwindir=D:\WindowsAgain, replace `D:\` with the correct Windows volume.
SFC will scan the Windows directory for corrupt or missing files and attempt repairs automatically.
Wrap-Up: What to Do If Repairs Fail
If DISM or SFC can’t complete, consider:
• Booting into Safe Mode if accessible.
• Performing an in-place upgrade using a USB installer (you won’t lose files).
• Backing up data and reinstalling Windows as a last resort.
Got questions, edge cases, or want to dive deeper into PowerShell-based recovery automation? Drop me a line or check out other fixes on memoryisram.com where I explore real-world tech problems with practical solutions.
