Intel 13700K paired with Asus B760, BIOS update applied, PC launches directly into EZFlash settings.
Intel 13700K paired with Asus B760, BIOS update applied, PC launches directly into EZFlash settings.
Updated the project name and corrected the memory of the EZflash helper who assembled the new PC. Experienced with building 40 to 50 computers before, yet this was the first Intel system in years. The PC was assembled, Windows 11 Pro was installed, and everything functioned normally. I downloaded the latest BIOS for the Asus B760-Plus Wi-Fi motherboard, version 1402—believed that. The update proceeded without issues, but upon restarting, the PC launched directly into the BIOS update screen instead of the main one. (Updated via BIOS using USB). During the update, it restarted and displayed Intel ME components before returning to the BIOS. When I re-entered the BIOS, checking the Boot order, only the SSD was listed first. To access Windows, I had to navigate further down the boot sequence, where I could locate the SSD under some override settings. I attempted to restart the BIOS update again, noticing they mentioned a Bitlocker key and suggested backing it up. I recall hearing about this during the launch of Windows 11, but never considered it before. About two weeks ago, I built an AMD 5700X PC for work, and this issue didn’t occur there, even though I updated the BIOS as I did. I tried resetting the BIOS, but it didn’t resolve the problem. Any suggestions on how to fix this? I’ve asked in a Norwegian forum, but none of the 120 members who read it offered any solution. I’m planning to reinstall Windows since the PC hasn’t been used yet—only testing things before this happened, so there’s no risk of losing data. However, if it keeps opening in EZSetup, it suggests a problem with the BIOS or motherboard. EDIT: It’s possible the BIOS is incorrect? I see Asus offers B760-PLUS WIFI and B760-PLUS WIFI D4 models. Could the motherboard accept a different version?
Motherboards usually come with unique BIOS versions, such as D4 versus D5. The microcode often warns about incompatibility or similar messages. It’s possible, but I doubt it’s just a BIOS mismatch since you mentioned BitLocker. Did he encrypt any drives or the primary boot disk? This usually happens with BitLocker enabled, as it can block boot from certain media without the correct key. Otherwise, you might need to explore troubleshooting steps for BitLocker issues, which seem to occur frequently.
I haven’t encountered anything out of the ordinary during setup, nothing related to enabling BitLocker or similar features. EDIT: I wonder if a mismatch between the motherboard and BitLocker could cause it to boot into Windows when selecting override in the boot menu. I’d expect an encrypted drive to function without the proper key.
I recalled the incorrect EZ name—it's actually the EZflash menu that launches directly. We located the USB stick and applied the correct BIOS file. There was a BIOS rollback option in the menu; could we upload an older BIOS version with that? I haven't used it before.
BIOS rollback test passed. Possible issue lies with the newest BIOS from Asus.