Update from the creators: Issues reported. Please stay tuned for further developments.
Update from the creators: Issues reported. Please stay tuned for further developments.
The update process isn't working and resets the system to an older version of Windows. The OTA fails consistently, causing changes in the update but still being frustrating. A clean installation seems like a straightforward solution. The problem I encountered was that restarting stopped functioning. I receive a BCD boot error code 0xc000454 each time I power off. No repair method works, whether manual or automatic. This situation is very confusing since it was supposed to be a Windows 10 partner device for the Creators update. The RoG forums are also reporting the same issue. I've spent a week trying various fixes without success. Any advice or suggestions would be greatly appreciated. The laptop in question is an ASUS ROG STRIX GL502VS-DB71 Gaming Laptop with Intel Core i7 6700HQ, 16 GB RAM, 1 TB HDD, 256 GB SSD, NVIDIA GeForce GTX 1070, and Windows 10 Home 64-bit.
Yup. As @Constantin mentioned. Microsoft said that they have identified some system configurations to have issues with Windows 10 Creators Update. Microsoft suggest to not manually install the Creators Update if you want to be sure to have no issues, and to wait for your wave. Also, ensure that ALL your drivers are fully updated before starting the process helps a lot. Driver bugs that can block Windows upgrade is a strong possibility, that has happened before.
Have you ever utilized a registry cleaner? Which antivirus and anti-malware programs have you employed? Have you encountered any viruses during the installation of the current Windows version? Were you ever required to install or currently use any system tweak utilities?
I haven't relied on a registry cleaner. When I tried to resolve the issue by running Windows Update (last resort), it helped with some database update problems, but the problem remained. I'm using Windows Defender and haven't installed any additional software on this machine. I regularly monitor the resource monitor and see no system resources being consumed excessively or any unusual activity. So far, I haven't encountered any viruses. All drivers are current; the most recent fix was for NVIDIA drivers on several ASUS systems, which was addressed in the latest update a few days ago.
Curious... quite unusual... my main thought is to remove any driver programs such as GeForce Experience (even though many are installed and function properly), ASUS utilities, etc., then restart and see if it resolves the issue. I understand it might seem odd, but after applying the Anniversary Update, some users reported that deleting certain software resolved the problem. They reinstalled them post-upgrade and everything worked correctly.
I don’t rely on any driver programs (it’s frustrating when they change with your game settings). Just basic drivers and regular software—nothing that impacts Windows performance. It was a waste of about an hour. Here’s what I did: First, I cleaned the system format. Then I installed 1607 (Anniversary Update) and attempted to update to CU(1703), but that failed again. Next, I cleaned the Windows drive, removed installer files (using Disk Cleanup, no third-party tricks), and installed essential drivers—graphics, LAN/WIFI, audio, Bluetooth—from the Asus support site (NVIDIA included for graphics). I also kept the bonus feature software. Still can’t get it to work. Recently, I restored my system from a restore drive (USB stick). On the positive side, the BCD error is gone, but the Windows updater still asks to install CU(1703). It looks like Microsoft hasn’t disabled my device for the update, which is good news. What’s odd is the BCD error 454—can’t locate any reference or explanation. That’s what catches my attention.
Hi, I have met the same issue and I found one of the users of gl502vs has solved this issue on the ROG forum. Here is his (@ poptaz3r ) comment: " The more I mess with this the more I think it is a BIOS bug dealing with the power cycling on reboot. My guess is that on reboots the BIOS power cycles to quickly and causes the system to not read the MVMe drive. That is why a cold power down can reacquire the drive. This could be the result of larger capacitors on these OEM Samsung drives, but this is all just a guess. At any rate I found a workaround that has been stable for me. (below) Ok in BIOS under advanced changing the Smart self test setting to DISABLE. This allowed the update AE>CE install to complete with no BCD fails. Another BIOS change I made was to turn off secure boot because it was preventing me from entering recovery environment (safe mode) So with both of these settings changed in the BIOS I am back on the stock NVMe drive and all appears stable with no reboot BCD errors. " https://rog.asus.com/forum/showthread.ph...2VS/page10