cl-Albert,
Is there a later image? I just got mine back from RMA 2 weeks ago, and it shipped back to me with 1607 not 1703. I know that I can disable SMART in the BIOS and install the Creator's update, but I would prefer to not perform a workaround if I can help it. I am also sporting the latest BIOS (302) and all the latest drivers using the ASUS update tool.
The issue with booting, for me, was during a reboot or cold boot I would be stuck at the BSD error black screen, but a normal ctrl-alt-del would not trigger it, so when I was at that error, if I would simply press ctrl-alt-del I could get past it no problem.
Another artifact of the BIOS workaround and the Creator's update, was (at least for me) the inability to use the recovery image anymore. I don't know if it didn't ship built correctly, or if during the upgrade it didn't update it. But I noticed that when I tried to use it, it would get to the 2nd reboot and say that there was an unexpected error and revert back to 1703. I spent many hours digging on forums trying to find a way to update the recovery partition and validate it. And all signs pointed to a non-usable (but not corrupt) recovery partition post update. My thinking is the CU caused the disconnect with the RP, but there is still a firmware issue with the SSD's that needs to be addressed, as the Fall CU is right around the corner and we don't want to go through this again.
I am sitting nice and tight on 1607 with the Spring CU in the ignore list for now until ASUS comes up with an official fix/response.
Also, if there is need to have a test machine, or to test out a BIOS fix I am willing to use my machine. It is just for games, so not production or used for work or anything like that.
Thanks and I hope this helps.
Is there a later image? I just got mine back from RMA 2 weeks ago, and it shipped back to me with 1607 not 1703. I know that I can disable SMART in the BIOS and install the Creator's update, but I would prefer to not perform a workaround if I can help it. I am also sporting the latest BIOS (302) and all the latest drivers using the ASUS update tool.
The issue with booting, for me, was during a reboot or cold boot I would be stuck at the BSD error black screen, but a normal ctrl-alt-del would not trigger it, so when I was at that error, if I would simply press ctrl-alt-del I could get past it no problem.
Another artifact of the BIOS workaround and the Creator's update, was (at least for me) the inability to use the recovery image anymore. I don't know if it didn't ship built correctly, or if during the upgrade it didn't update it. But I noticed that when I tried to use it, it would get to the 2nd reboot and say that there was an unexpected error and revert back to 1703. I spent many hours digging on forums trying to find a way to update the recovery partition and validate it. And all signs pointed to a non-usable (but not corrupt) recovery partition post update. My thinking is the CU caused the disconnect with the RP, but there is still a firmware issue with the SSD's that needs to be addressed, as the Fall CU is right around the corner and we don't want to go through this again.
I am sitting nice and tight on 1607 with the Spring CU in the ignore list for now until ASUS comes up with an official fix/response.
Also, if there is need to have a test machine, or to test out a BIOS fix I am willing to use my machine. It is just for games, so not production or used for work or anything like that.
Thanks and I hope this helps.
cl-Albert wrote:
Have not been talking to HQ or Bahz about this and not sure if this will help much, but had the chance to check two RMA GL502VS (6th gen. Intel CPU) units running the latest 302 bios and noticed they both had the Samsung 256Gb M.2 SSDs installed with Windows 10 v1703 as in the screenshot below although it looks like they were clean installs rather than upgrades from the original ASUS image (the units were sent in for RMA this way, and didn't do the Win10 upgrades myself), so it doesn't appear all the drives have this issue if that is really the cause or maybe these customers found a way around it.
Both units also had SMART enabled in the bios as below and booted Win10 v1703 fine.
If anyone wants consider sending back their unit for RMA, curious if installing the latest ASUS Windows 10 image on the unit will work any better to upgrade to Win10 Creators Update, but not sure what will happen at this point.
Anyway, looks like it may take more investigation to figure this out. Thanks.
==========
