cancel
Showing results for 
Search instead for 
Did you mean: 

Windows Creator Update Installation Failure on GL502VS - workaround

Rishme
Level 7
Has anyone faced any issues installing the New windows Creator Update on their GL502VS.
It gets stuck at BIOS when it restart. And then roles back to the old version

This is the error i see
0xC1900101 - 0x20017 Installation failed during safe OS phase with an error during boot operation'
Help please?
580 Views
356 REPLIES 356

GL502vs 6th gen here. I too struggled with the 1703 update months ago and had to disable SMART in BIOS. I figured 1803 update would cause similar issues and yes mine too hung at 15% or 30%, restarts on its own and then restores previous installation. SMART on or off did not make a difference. The errors in the setup log led me to a Microsoft page about checking drivers. I realized at some point that I had manually installed the Samsung NVME storage controller driver. I uninstalled the driver, rebooted and could never boot back into Windows kept getting errors after POST. I ended up having to reset using Windows 10 Recovery menu and then was able to update to 1803. No issues with SMART on or off. The storage controller driver was a standard microsoft driver. I then manually installed Samsung NVME 3.0 driver and all is still good. We are long overdue for a BIOS update with the microcode fixes too. Bit ridiculous for a $1,600 laptop.

TLDR, messed with Samsung NVME storage controller driver, caused laptop to not boot, had to reset using Win 10 recovery menu, then no problems updating to build 1803.

"I wonder what kind of workaround this scumbag company will come up with for 1803."

That's an easy question to answer.....nothing. If a workaround is to be had, it will have to come from here.

ajsupahiya wrote:
No I havent used OS migration , I dont have a spare ssd for now.
After Asus logo I did force shutdown and then on restart its going on the screen saying - restoring previous version of your windows...

Even after disabling SMART same thing is happening.


have you tried ALL the microsoft troubleshooting tips?

kingKAI wrote:
have you tried ALL the microsoft troubleshooting tips?



yaa almost all of them. Only thing remaining is doing a reset. What a disappointment. I love this laptop but its just crying too lound now.

ajsupahiya wrote:
yaa almost all of them. Only thing remaining is doing a reset. What a disappointment. I love this laptop but its just crying too lound now.


Why not consider a CLEAN INSTALL? i have been mulling over it since April 2017. Finally gave in by Feb 2018. Had to transfer my personal files. It sounds tedious, but theres no simpler way than this. (aside from the failed microsoft troubleshoot steps)

My 4th attempt on the 1803 update somehow went through on my GL502VS. It was rocky, but it completely successfully.

I have no idea if this helps, but I pulled all peripheral equipment (wireless mouse, external monitor, etc) before the attempt. When having trouble previously with the FCU back in October, I did this and it went through when previous attempts failed.


Good Luck.

RippedTester170 wrote:
My 4th attempt on the 1803 update somehow went through on my GL502VS. It was rocky, but it completely successfully.

I have no idea if this helps, but I pulled all peripheral equipment (wireless mouse, external monitor, etc) before the attempt. When having trouble previously with the FCU back in October, I did this and it went through when previous attempts failed.


Good Luck.


Tried but no luck. Thanks anyways.

hamsterzagard
Level 8
This winload efi happening again with 1803 update lol. Previously i worked around it with clean install to get 1607. 1607 to 1709 with os clone to sata bcs updating on sata got no problem. This is on G752VY,,, this time i was hopeful bcs samsung released new driver, but still no candy. Will end up doing the whole clone to sata to update shenanigan most likely, what a joke

chevell65
Level 12
Guys 'or gals' if you follow the steps in this link, it may help with your issues when installing the 1709 creators update. It also works to fix the installation sticking at a certain percentage which is all too common. I also found some major bugs with version 1803 where they yanked out the Home Group functionality in a half a**ed way which is a shame because my testing indicated that Home Group networking was finally working much better in version 1709, where since Windows 7 certain machines would randomly drop out of the Home Group 'machine not available' now seems to be fixed for the first time in history. So with this working they of course yanked it out of 1803? The bigger issue was that certain machines like my old Z97 Maximus would not even show up under networked machines. Others have complained about similar bugs in 1803 so if networking matters to you then don't install it. Luckily there are a couple of settings in Windows to prevent it from installing automatically.

sopipari
Level 7
I've opened a few tickets with Asus on this issue. They dropped me an update last week and said that they are working with Microsoft to fix the issue with updating windows. That was a bit of a surprise.