Question [SOLVED] Windows 11 won't boot after diskpart clean command

[bolorok]

Hi, so I installed a new NVME and cloned my system on it from my old NVME drive. Changed the boot order in BIOS then booted into Windows 11 without issues.
I then wanted to use the old NVME as a data drive, but the Windows disk Manager wouldn't let me format it since it was an (unused) system disk. So I searched the internet for a way to delete all files and partitions on this drive, and came upon a tip to use the "clean" command in diskpart. So I did, and indeed the disk was blank, all data and partitions gone, but there was a red dot symbol on the disk icon and Windows disk manager wouldn't let me create a new partition.
I thought, maybe a reboot would fix this, so I restarted Windows but instead of booting into Windows on the (not cleaned) new NVME, I was greeted by a BSOD titled "Recovery" and showing the error code 0xc00000e and a bunch of recovery options. However, nothing happens when I click on any of these options!
I checked my BIOS settings and it's definitely set to boot from the new device which was untouched by diskpart. Weird enough, but then it got weirder: I tried to run recovery from a Windows 11 installation bootable USB stick I created with Rufus, and although I set it as the boot device, it will still immediately go to the same BSOD!
I took the old NVME out of the PC and it's still the same outcome.
I am at a loss now and would truly appreciate any help. =/

 

[USAFRet]

This is why you never ever clean off the old drive, until you verify the system boots from only the new drive, with the old drive physically disconnected.

Does it now boot in any configuration?

 

[bolorok]

This is why you never ever clean off the old drive, until you verify the system boots from only the new drive, with the old drive physically disconnected.

Does it now boot in any configuration?

Lesson learned there. =S
It does not boot in any configuration. What bothers me most though is that it doesn't even load up the recovery menu from the bootable USB stick. I haven't tried booting it without any of the two NVME drives installed yet, but I doubt it will yield different results...

 

[USAFRet]

Lesson learned there. =S
It does not boot in any configuration. What bothers me most though is that it doesn't even load up the recovery menu from the bootable USB stick. I haven't tried booting it without any of the two NVME drives installed yet, but I doubt it will yield different results...

I'm seeing 2 options here:
1. Recover from the full drive image you made before this happened. But I'm assuming that does not exist, else we would not be having this conversation.

2. Fresh OS install. Along with everything else.
Have only ONE drive physically connected when you do this.
Your old data (not applications) may be somewhat recoverable from the original drive(s).

 

[bolorok]

Thanks for the help!
I managed to solve it by removing all storage drives first, then I was finally able to boot into the recovery tool on the USB stick. I then turned off the PC again, re-installed the NVME and made sure boot priority is on the USB stick. Started CMD from the stick and ran diskpart. There I saw what I already thought would be the case: the partitions on the new NVME had no drive letters, so I assigned drive letters to each. I repaired the boot records with the bcdboot command and restarted the PC (without the USB stick attached ofc). It booted smoothly straight into the OS on the new NVME!
Happy it went smoothly and that all my data is still there. I hope this helps anyone with a similar problem. I'll be more careful next time before toying with diskpart for sure. =)

 

[astroboylrx]

Thanks for the help!
I managed to solve it by removing all storage drives first, then I was finally able to boot into the recovery tool on the USB stick. I then turned off the PC again, re-installed the NVME and made sure boot priority is on the USB stick. Started CMD from the stick and ran diskpart. There I saw what I already thought would be the case: the partitions on the new NVME had no drive letters, so I assigned drive letters to each. I repaired the boot records with the bcdboot command and restarted the PC (without the USB stick attached ofc). It booted smoothly straight into the OS on the new NVME!
Happy it went smoothly and that all my data is still there. I hope this helps anyone with a similar problem. I'll be more careful next time before toying with diskpart for sure. =)

Hi bolorok, I ran into the same problem, and silly me, twice now. For the first time, I didn't find useful info after googling so I just did a clean install.
Now for a different machine, I fell into the same trap again (I wasn't sure the clean operation was the cause, now I'm sure).
Glad this time I found this post. Would you please elaborate the part "so I assigned drive letters to each. I repaired the boot records with the bcdboot command"? What exactly did you do? Thank you very much in advance!