Question Did I brick my entire PC running this command in CMD?

Aug 14, 2025
2
0
10
I was trying to get my PC to boot without using CMS do I could enable secure boot so I could play a new game that requires it. I found the below commands and tried them myself:
The only difference is I replaced the "Assigned letter" from H to C, which I believe is the main issue.

Now I cannot boot into Windows whatsoever. In the BIOS, the boot menu is completely empty as if the MOBO is not recognizing any of my drives:

However, they show up under Storage Information:

I completely reset the BIOS to default settings but that did not fix the issue. I even tried to reinstall Windows but the installer can't even detect any of my drives:

I am almost completely out of ideas except for maybe getting a new MOBO since I feel like that command in CMD physically bricked the motherboard. Any assistance would be GREATLY appreciated!
 
You have all your disks in raid(your mobo pic says so) which is why the windows install doesn't find any drives, go to your mobo website and look for raid or sata drivers, decompress them onto a usb (even the same that the win install is on) and push the load driver icon and point to the decompressed folder.

How did you even assign C ? That's always your running windows partition so it's always already in use, did you do it by booting from an usb?
 
You have all your disks in raid(your mobo pic says so) which is why the windows install doesn't find any drives, go to your mobo website and look for raid or sata drivers, decompress them onto a usb (even the same that the win install is on) and push the load driver icon and point to the decompressed folder.

How did you even assign C ? That's always your running windows partition so it's always already in use, did you do it by booting from an usb?

I was having some trouble loading the drivers, I'm not sure if they actually managed to load on. However, I did stumble across another "fix" which was to disable the VMD controller in the BIOS. I did this and Windows booted completely normally, detecting all my drives and not losing any data.

Are there any unforeseen consequences to this "fix"? I honestly have no idea about the technical aspect of what disabling the VMD controller does. Is this more of band-aid fix than a proper one? Either way I'm very relieved to actually be able to boot!

If there's any mods, I think you can set this to solved.
 
However, I did stumble across another "fix" which was to disable the VMD controller in the BIOS. I did this and Windows booted completely normally, detecting all my drives and not losing any data.
If it shows all disks normally with VMD off than you turned that on by mistake which is why you lost all your drives.
VMD is volume management device and it's used to do raid, your disks are not in raid which is why they work fine now.