Total Boot Failure After Removing Second SSD - Win 10

You are welcome.

(1) There is the Feedback Hub (type into Search) which Microsoft is said to monitor. I'm unsure how you would communicate your precise problem to them there, though. Try to explain what DISM/SFC do.

2. Get Help (type into Search) eventually will have a Contact Support button after you have asked it a question. I don't know whether it actually still works. Best tell them what you want before you give them money. Otherwise, they will think it is a fix to do a clean install/reset. That's no good for you, & you can do that yourself anyhow.

Sorry, I could find nothing better. Good luck & definitely let us know the solution if you find it.

I checked and both are x64. Bummer! Thanks for all the help!!!

Do you think I could get help from Microsoft? A long time ago, they had a pay service (was a flat fee of $100 or $200). It was that price regardless of how difficult it was to resolve the problem. I never used it, but our company did (back in the late 90s).

I haven't found any more on the NET but a clean install/reset for a cure. I want to compare the architecture (64-bit/x64 or 32-bit/x86) of your computer to the that of your Win 10 Installation USB. If they are different, it might explain the strange behavior of DISM/SFC. Does SystemType match the reported Architecture...?...

DISM /Get-Wiminfo /Wimfile:D:\Sources\Install.esd /Index:6

WMIC ComputerSystem GET Manufacturer, Model, SystemType

But that could only be an issue when running from the USB (repair your computer). If running from the internal recovery environment (Advanced Options button of a crash screen), the architecture has to be the right one.

I don't know where to go from here. And I don't see a solution dropping from the sky.

C:\WINDOWS\system32>DISM /Get-Wiminfo /Wimfile:e:\Sources\Install.esd /index:1

Deployment Image Servicing and Management tool

Version: 10.0.19041.844

Details for image : e:\Sources\Install.esd

Index : 1

Name : Windows 10 Home

Description : Windows 10 Home

Size : 14,826,317,709 bytes

WIM Bootable : No

Architecture : x64

Hal : <undefined>

Version : 10.0.19041

ServicePack Build : 1288

ServicePack Level : 0

Edition : Core

Installation : Client

ProductType : WinNT

ProductSuite : Terminal Server

System Root : WINDOWS

Directories : 26592

Files : 98251

Created : 10/6/2021 - 10:09:22 AM

Modified : 11/21/2021 - 11:24:28 PM

Languages :

    en-US (Default) 

The operation completed successfully.

C:\WINDOWS\system32>wmic computersystem get manufacturer, model, systemtype

Manufacturer Model SystemType

Dell Inc. Inspiron 3542 x64-based PC

Got the file renamed back and confirmed its back to the state it was before the rename. Tried the Repair option several times (and with rebooting)...no go.

OK. I didn't know that about that "disable" screen. Anyway, we discovered renaming it does let the boot proceed, but it complains about the next one. I think there will be too many to continue renaming them. These look like the myriad Microsoft services that Windows loads at boot to run in the background. Probably the system will be useless without them, even if it did boot. Let's rename that one back...

REN E:\Windows\system32\drivers\wd\WDBoot.sys.XXX WdBoot.sys

The boot process does begin. The files to load are in the right place. They are fetched. But Windows doesn't like them anymore. Why? SFC fails to initialize. DISM appears to have permissions troubles. Why? Time to hit the sack soon. I'll have to think/search more tomorrow.

Maybe try "Troubleshoot > Advanced Options > Startup Repair" 3 or 4 times in a row. I've seen some say it might eventually work. Good luck.