The Windows update damaged my PC's BIOS.
The Windows update damaged my PC's BIOS.
Your Windows 10 PC was recently updated during a shutdown. When you tried to start it this morning, you encountered error code 00 on your MSI X299 motherboard, preventing it from booting into BIOS. You changed the BIOS to the backup version but still couldn’t boot Windows. Using a Windows USB created with Microsoft’s Media Creation Tool 22H2, you attempted to fix updates and repairs, but Windows refused to uninstall or install, claiming it was still present. It seems your installation might be corrupted, and your backup files could be missing.
Even though it's not impossible, chances of getting BIOS updates through Windows updates are minimal... Assuming that, do you have BitLocker enabled or another form of encryption? If not, you might be able to retrieve the file by pausing Windows on another drive and accessing the data directly.
From a brief search online I noticed no mention of code "00" but found information about CODE "D0". Regarding your question, I tried removing the CMOS battery and then restarting just like the previous instructions. It seems similar to turning it off and on again, though it might be helpful. BIOS Debug Hex Codes Decoded & BIOS Manuals Links | MSI Global English Forum 00 - Not used 01 - Power on. Reset type detection (soft/hard) 02 - AP initialization before microcode loading 03 - System Agent initialization before microcode loading 04 - PCH initialization before microcode loading 05 - OEM initialization before microcode loading 06 - Microcode loading 07 - AP initialization after microcode loading 08 - System Agent initialization after microcode loading 09 - PCH initialization after microcode loading 0A - OEM initialization after microcode loading 0B - Cache initialization XE Error Codes D0 - CPU initialization error D1 - System Agent initialization error D2 - PCH initialization error D3 - Some architectural protocols missing D4 - PCI resource allocation error. Out of Resources D5 - No space for Legacy Option ROM D6 - No console output devices found D7 - No console input devices found D8 - Invalid password D9 - Error loading Boot Option (LoadImage returned error) DA - Boot option failed (StartImage returned error) DB - Flash update failed DC - Reset protocol not available
I didn't configure anything in that way. I haven't attempted to remove the battery at all.
Linux supports mounting BitLocker-encrypted drives. The user could simply boot from a live USB, attach the drive, and copy the data that way. It’s likely the user understands the encryption key, or if not, it remains possible under certain circumstances. However, this topic isn’t suitable for discussion here.
The output will show d0 instead of D0, confirming the error code is clearly 00...
Was das Laufwerk der Master Boot Record gewesen? Hast du versucht, die CSM-Funktion im neuen BIOS zu aktivieren?
I haven't explored the BIOS yet. MBR and SCM are terms you might be referring to. Small update: I've reset the BIOS settings back to default, but I encountered an issue with the Windows boot screen. Honestly, I'm unsure what's causing the problem or how to resolve it.
The MSI guide lists "00" as an unused code, indicating it hasn't been applied yet.