Solved How to do a Repair install with inaccessible boot device issue

chris1234 said:

There appears to be two, I've tried both

Can I restore my primary drive backup image to a USB drive and boot from it?

BTW thanks to everyone so far for your efforts even though I still haven't managed to fix my PC

Click to expand...

chris1234 said:

A) How do I fix a corrupt boot binary?

Click to expand...

Root cause found:
---------------------------
A recently serviced boot binary is corrupt.

Unable to boot Windows10, "A recently serviced boot binary is corrupt" - Windows 10 Help Forums

This is on Windows Version 10.0.19041.631 So I'm currently unable to get into my computer. I got a Windows 10 installation file from a friend though when I try to repair it still doesn't boot. When I check SrtTrail.txt, none of the tests say completed uns

www.tenforums.com

When you perform a custom install of Windows 11, a clean install of Windows 11 is performed only on the same partition as the current installation of Windows to replace it. The previous installation is moved into the C:\Windows.old folder as a backup. Once the new custom install has finished, you will be able to copy any files you want back from the C:\Windows.old folder.

A custom install of Windows 11 can be useful if you are unable to start Windows for whatever reason, need to reinstall Windows 11, but do not want to lose any files in your current installation by doing a full clean install.

Click to expand...

Custom Install Windows 11

This tutorial will show you how to do a custom clean install of Windows 11 on your PC. When you perform a custom install of Windows 11, a clean install of Windows 11 is performed only on the same partition as the current installation of Windows to replace it. The previous installation is moved...

www.elevenforum.com

zbook said:

1) Run command prompt:

Type:


notepad
notepad
notepad
dism /image:C:\ /get-drivers /format:list
(change C: to the applicable drive letter)
dism /image:C:\ /cleanup-image /revertpendingactions /scratchdir:C:\scratch
(change C: to the applicable drive letter)

Click to expand...

• Boot Binary Corruption: This refers to damage in the actual executable files or boot sector data (like the Boot Configuration Data - BCD) needed to start Windows. When these files are corrupted, the system cannot load the operating system properly. The error message is a specific symptom of this problem.

• Recently Serviced: This usually points to an issue that occurred during a Windows Update, which modifies system files and boot components.
• 
  
• Boot Binary is Corrupt: A "boot binary" is a crucial file (like winload.efi or others in the EFI partition) that the computer's firmware uses to load the Windows operating system. If this file is corrupt, the boot process halts.

• A failed Windows Update is a common cause for this error.
• Updates often involve making changes to system files and the registry.
• If the update process was interrupted (e.g., by a sudden shutdown) while servicing a boot binary or making a related registry change, it could result in an inconsistent or corrupt state in both the binary and the associated registry entries, leading to a boot failure.

zbook said:

Can this be registry corruption?

Click to expand...

Excellent follow-up — and yes, that’s a very smart question.
Short answer:
It can be related to registry corruption, but not directly — the “recently serviced boot binary is corrupt” error usually refers to binary file corruption, not registry hive corruption.
However, registry corruption can indirectly cause this message, because the registry contains information that the bootloader and servicing stack depend on.
Let’s unpack that clearly:

---

1. What the error actually targets​

This message from Startup Repair / WinRE is generated by the CBS (Component-Based Servicing) subsystem.
CBS checks the catalog (.cat) and manifest (.mum) files in C:\Windows\WinSxS against the binaries in System32 and the EFI folder.

• If a file like winload.efi or bootres.dll doesn’t match its expected hash or catalog signature → you get “a recently serviced boot binary is corrupt.”

That’s usually a file integrity problem, not registry.

---

2. When the registry is involved​

The boot process depends on several hives:

• SYSTEM — controls drivers, services, and control sets.
• SOFTWARE — used after kernel initialization.
• BCD — boot configuration database (not technically part of the registry but a hive-like file under \EFI\Microsoft\Boot\BCD).

If the SYSTEM hive or BCD file is corrupt or mismatched, Startup Repair can misreport it as a "corrupt boot binary" because the loader can’t resolve dependencies properly.
So in those cases:

• The file itself is fine, but Windows fails to verify or load it because the registry or BCD data that references it is broken.

---

3. How to test if the registry is the real culprit​

(a) Check for registry hive corruption:​

From the recovery command prompt:

Code:

dir C:\Windows\System32\config

If any hive (e.g. SYSTEM, SOFTWARE, DEFAULT, etc.) shows size 0 KB or a timestamp of the last crash → that’s a bad sign.
You can try restoring from automatic registry backups:

Code:

cd C:\Windows\System32\config\RegBack
dir

If there are files there (with reasonable sizes), restore them:

Code:

copy *.* C:\Windows\System32\config\

(b) Rebuild the BCD​

If the registry is fine but the boot database is bad:

Code:

bcdedit /export C:\BCD_Backup
attrib S:\EFI\Microsoft\Boot\BCD -h -r -s
del S:\EFI\Microsoft\Boot\BCD
bcdboot C:\Windows /s S: /f UEFI

---

4. Summary​

Possibility	Symptom	Fix
Corrupt boot binary	Damaged or mismatched boot file (winload.efi, etc.)	Use sfc, dism, bcdboot
Corrupt BCD / SYSTEM hive	Boot fails early, Startup Repair misreports “boot binary corrupt”	Restore registry hives or rebuild BCD
Both	Usually after interrupted Windows Update	Combine both fixes above

---

TL;DR​

The error itself isn’t directly caused by registry corruption, but registry or BCD corruption can trigger the same symptom because the bootloader fails to load or verify binaries properly.

Click to expand...

---

If you tell me:

• Whether you can mount and view your C:\Windows\System32\config folder, and
• Whether sfc /scannow /offbootdir succeeds or fails

…I can help you determine precisely whether your case is file or registry corruption.
Would you like to do that check next?

Click to expand...

chris1234 said:

Custom install is still an option, I'd rather not try just yet, I can still restore from one of my cloud backups
Something does appear to have gone wrong, somewhere, somehow and none of the suggestions appear to have worked.

Thanks to everyone for trying, I do appreciate the time and effort for helping someone brand new to this forum

At least I am confident, drives are not faulty and memory is good. I have more storage space and a new MB
I still have the previous drive if this restore fires my entire PC
At 160Mbps I'm good with that, already completed 12%.
Hopefully it boots up and my drives are in the correct order, I still might need some more help, I'll know in about 3-4 hours

Click to expand...