Your system supports Windows 1607 and 1511, yet it doesn't recognize the newest 1703 release.
Your system supports Windows 1607 and 1511, yet it doesn't recognize the newest 1703 release.
It began when my PC (running Windows build 1703) encountered severe BSODs after a BIOS update. I searched YouTube for fixes but found no reliable solutions—some advice only made things worse, leading to errors like BCD/BOOT 0x000000f during a Windows reinstall from USB. Eventually, I took my machine to a repair shop, who suspected the SSD was faulty and asked me to return it for warranty. After returning, I reinstalled Windows again, but the same BSOD persisted. I then tried booting from UEFI and installing via USB, though the installation failed. When I attempted a feature update (1703), it repeatedly triggered a restore to the previous version. I considered updating to 1607 first, which worked, but the 1703 update kept failing, returning me to the old version. I also experimented with resetting the BIOS via jumper, though I wasn’t sure if that was the issue. Finally, I tried installing Windows on a different drive, but it didn’t work for the 1703 build. My PC’s specs are: AMD Ryzen 5 1600, 8GB Corsair Vengeance LPX, 3000MHZ GPU, MSI R9 380, 4GB RAM, and a Western Digital Blue 500GB SSD (with OS).
It seems functionality might be limited. Varying the clear CMOS can reset the BIOS, which I’ve experienced before. As an alternative, using a USB drive with the W10 setup could help troubleshoot the installation.
I've tried this multiple times too, but it didn't succeed. It's similar to how Windows 10 version 1703 refuses to install on my PC. (By the way, my computer is still functioning, I'm just using it to respond.)
I wonder if you're familiar with turning off Windows Update's constant prompts about restarting after the 1703 update. It would be nice to avoid those reminders, especially since you enjoy using the new features it provides, like better game performance.
It seems we don’t require any memory dumps, though most of the files ending with .log in the list could be helpful. The usefulness depends on where the update encountered issues.