Question WD_BLACK SN770 NVMe can't boot after installing Windows ?

[Omphaloskeptic]

Hey all, sorry if I'm posting in the wrong place here, not sure if my problem is with storage or the mobo so I'm asking around to whoever can help.

NVMe SSD: WD_BLACK SN770 2TB
Mobo: Gigabyte B650 AORUS ELITE AX ICE, BIOS version F31
CPU: AMD Ryzen 7 7700X

I started with using this drive as only storage on a different build with no issues. After upgrading most of the parts of the PC, it was still recognized as a drive and I can still use it for storage now. The problem is when I try to install an OS on it because my OS is currently installed on an older SSD. Here's the process I went through: clean the drive to unallocated space using diskpart in the command prompt, shut down, physically unplugged my other drives from the motherboard, boot from USB with Windows installation media, installed Windows 10 (and have tried 11).

Afterwards, the NVMe SSD isn't recognized as a boot drive until I enable CSM support, but once it's recognized and I try to boot I get this:
" reboot and select proper boot device or insert boot media in selected boot device and press a key "

The drive appears to have Windows installed correctly and is in GPT format. The drive is installed in the M2A_CPU slot. After asking WD for help we determined that the drive is as 100% health and is probably not the problem if it can still be used for storage.

Please let me know what other information is required or how I can fix this problem.

Thank you for your help.

 

[dev_cyberpunk]

I've never had to do either of those, and no cloning software will work without decrypting a drive unless it warns you and only runs in bit-for-bit mode, and the TPM is perfectly capable of storing multiple keys so you could swap hard drives back and forth.

Cleaning the slate and starting new make no difference if they didn't encrpyt the drive. But you might be correct with leaving it alone since those keys have no meaning outside that machine and the user could have used it.

Secure boot has to be reset when the boot drive is changed regardless if an OS is installed on the disk or not. For both MBR or UEFI translation types.

Btw, the OP should just turn secure boot off until the drive can boot, then it can be set to install

 

[evermorex76]

Secure Boot isn't "reset" at any point. Nothing gets modified by Secure Boot by installing any operating system. It's just a set of keys saved in the BIOS that are used to recognize the OS, similar to the TPM storing encryption keys and other crypto data. Secure Boot has a set of public keys for known manufacturers of OSes stored, and uses public key cryptography to look at the key presented by an OS at boot time to verify that it's a "legitimate" OS. The keys in the Secure Boot store can be updated, but they aren't changed by installing an OS, and disabling it doesn't change anything or reset it to zero or the like.

The only thing Secure Boot does is validate that the OS is legit. The only thing that happens if you're booting a non-Secure Boot-compatible OS is that the BIOS prevents booting and reports an error. Any problems with Secure Boot would not manifest in what OP is seeing.

 

[dev_cyberpunk]

Secure Boot isn't "reset" at any point. Nothing gets modified by Secure Boot by installing any operating system. It's just a set of keys saved in the BIOS that are used to recognize the OS, similar to the TPM storing encryption keys and other crypto data. Secure Boot has a set of public keys for known manufacturers of OSes stored, and uses public key cryptography to look at the key presented by an OS at boot time to verify that it's a "legitimate" OS. The keys in the Secure Boot store can be updated, but they aren't changed by installing an OS, and disabling it doesn't change anything or reset it to zero or the like.

The only thing Secure Boot does is validate that the OS is legit. The only thing that happens if you're booting a non-Secure Boot-compatible OS is that the BIOS prevents booting and reports an error. Any problems with Secure Boot would not manifest in what OP is seeing.

I have to disagree.

I swap boot drives in a MSI cubi-n200 box often and its UEFI system I have to clear/reset secure boot every time I change the drive. Because UEFI bios checks signatures of anything used in the boot process.

If the NVME drive was a cloned SSD drive image, you still have to reset this, as the drive checksum signature will be different.

 

[evermorex76]

Well you're unique, I guess.