Hi, I built a new PC, and I'm having a problem installing Windows 11.

I installed Windows 11 from a USB onto the WD\_BLACK SN7100 1TB. The installation started normally, but after the PC restarted, it went straight into the BIOS instead of continuing to Windows.

The SSD is detected in the BIOS in M2\_1, but Windows Boot Manager doesn't appear in the Boot options.

Things I've already tried:

Made sure the BIOS is set to UEFI, not CSM.

Secure Boot is enabled and set to Standard.

Performed a clean Windows installation.

Deleted the SSD partitions and installed Windows again on the unallocated space.

Used CMD to check the EFI partition, and it exists (200MB FAT32).

Ran bcdboot C:\\Windows /s S: /f UEFI and got “Boot files successfully created.”

Checked that bootmgfw.efi exists in the EFI partition.

bcdedit /enum firmware does show Windows Boot Manager with the correct path.

Despite all this, it still boots straight into the BIOS, and Windows Boot Manager doesn't appear in the F11 Boot Menu or Boot Options.

I also updated the BIOS to the latest version, but the problem is still happening.

Does anyone know what could be causing this or what else I can check?

It feels like I already tried everything

Specs: https://es.pcpartpicker.com/list/qGYvbp

make a windows usb https://www.youtube.com/watch?v=Mfp0ROs-e3U&t=94s

then insert this into uab port then post a screenshot of your bios in easy mode

"Used CMD to check the EFI partition, and it exists (200MB FAT32)" how are you checking this windowws is not installed

Redownload the Windows 25H2 ISO direct from Microsoft using Chrome or Edge and write it to a USB stick using Rufus ...

http://rufus.ie/

Configure Rufus to use NTFS instead of FAT32. The Windows Media Creation Tool will use FAT32, which has a 4GB file size limit, causing the 6.3GB WIM file to be split into two files, which opens the file up for corruption. NTFS doesn't have this issue. Rufus will copy the 6.3GB WIM file as-is and supports EFI booting from NTFS volumes.

>The Windows Media Creation Tool will use FAT32, which has a 4GB file size limit, causing the 6.3GB WIM file to be split into two files, which opens the file up for corruption.

I am pretty sure that Microsoft knows how to split .wim files. Besides, the large install.wim image has nothing to do with the boot configuration.

The might give my autounattend.xml generator a try. When you select the Generate a .cmd script to handle the Windows PE stage and the Pause before Windows Setup reboots at the end of the Windows PE stage settings, you will be able to see the output of both bcdedit.exe and bcdboot.exe, which might point to the problem.

But it needlessly splits the WIM, inviting corruption to both split files and drastically increasing the install time because both WIM files are first de-compressed, split in two, and then re-compressed all over again. NTFS does not have this issue, making Rufus more reliably and time efficient for the task at end.

The WIM file contains everything Windows needs to partition and install Windows on storage media.

A corrupt WIM can NOT be relied on. Period.

Microsoft certainly knows how to fuck up a junkyard with a foam rubber hammer. Unless you're an MSFT shareholder or know of a junk yard that could use the NERF treatment, there is ZERO reason to trust Microsoft official tools to do a Microsoft job. Pete Batard proves that with Rufus and Mosby every day.

In the Windows Preinstallation Environment (PE), of course.

well yeah