none
Problem with upgrade to "Creators Update" on NVMe disk RRS feed

  • Question

  • Hi,
    I'm successfully running Windows 10 x64 Version 1607 (Anniversary Update) installed on Samsung EVO 960 NVMe SSD disk. I'm using UEFI boot on my ASUS H170 Pro Gaming motherboard. I made a clean install couple of months ago. No problems sofar.

    Now I'm trying to upgrade to Creators Update (Version 1703) via Windows Update. The update alsways canceles at the first boot. i am getting the error code 0xC1900101 - 0X20017 ("Installatin was not successfull. In the phase SAFE_OS a error occured at BOOT" - or similar, translated from german).

    I already installed the newest UEFI 3401 from ASUS and contacted their support - they say it is a software problem, i should contact Microsoft.

    Here are the setup logs:

    setupact.log https://1drv.ms/u/s!AnenyNJLzYYFkFshrgBJAS1YVXXi
    setuperr.log https://1drv.ms/u/s!AnenyNJLzYYFkFnAXA84quO_xv2g

    Any ideas?
    thx Franz Stadler

    Sunday, May 7, 2017 7:13 AM

Answers

All replies

  • Hi Franz Stadler,

    Have you updated the latest BIOS and drivers in your mother board?
    You can download from here:
    https://www.asus.com/us/Motherboards/H170-PRO/HelpDesk_Download/
    _____________
    Ashidacchi
    Monday, May 8, 2017 2:47 AM
  • Hi Ashidacchi,

    yes, the latest BIOS/UEFI and drivers from the mother boards vendor ASUS support site https://www.asus.com/us/Motherboards/H170-PRO-GAMING/HelpDesk_Download/ are installed on the system.

    Monday, May 8, 2017 5:08 PM
  • Hi Franz Stadler,

    I've browsed two log files that you shared.
    And I suspect if motherboard BIOS prohibit from being changed.

    Have you changed something in BIOS settings, especially related to password, protection, booting, etc?  Try to restore BIOS settings to default.

    # I recommend to make "Fast Boot" [Disabled].
    ___________

    Ashidacchi



    • Edited by Ashidacchi Tuesday, May 9, 2017 3:00 AM
    Tuesday, May 9, 2017 2:58 AM
  • Hi, 

    I just notice these errors: 

    2017-05-06 08:29:34, Error                 CONX   Failed hashing for syswow64\drivers\asio.sys, 0x80070003
    
    2017-05-06 08:29:34, Error                 CONX   Failed hashing for [syswow64\drivers\asio.sys] 0x80070003
    
    2017-05-06 08:29:34, Error                 CONX   Failed hashing for syswow64\drivers\asupio.sys, 0x80070003
    
    2017-05-06 08:29:34, Error                 CONX   Failed hashing for [syswow64\drivers\asupio.sys] 0x80070003
    Please see that The genuine AsUpIO.sys file is a software component of Asus PC Probe by ASUSTeK. If you have Asus PC Probe installed on the PC, please also make sure to update it to the latest version from Manuafacturer's support site. 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 10, 2017 9:35 AM
    Owner
  • Hi,

    Kate Li has done a nice work, I believe. I just remember "Asus PC Probe II", which is bundled with AsusTek mother board via CD-ROM.
    I'd like to add to Kate Li's comment, you should uninstall "Asus PC Probe".
    ___________
    Ashidacchi
    Wednesday, May 10, 2017 9:47 AM
  • Hello Ashidacchi, Kate Li,

    thank you for your help! Today i found time to try your suggestions.

    1) Disabled "Fast Boot" -> No Help :-(
    2) Uninstalled ASUS SW ("AI Suite 3" and "ASUS Boot Setting"). Cleaned file system and registry from Asus objects. 

    So asio.sys and asupio.sys are nowhere on the system. -> No Help again :-(
    Although this 2 sys files are nowhere on the system, i observed in the next update attempt that the "Failed hashing" errors are still listed in setuperr.log! I think they are part of the installation media. And this errors are maybe not the real problem.

    I think the real problem is related to the following errors:
    2017-05-12 19:29:22, Error                 IBSLIB Failed to export alterations to firmware. Status: c000000d[gle=0x00000003]
    2017-05-12 19:30:47, Error                 IBSLIB Failed to export alterations to firmware. Status: c000000d[gle=0x00000003]
    2017-05-12 19:31:12, Error                 IBSLIB Failed to export alterations to firmware. Status: c000000d[gle=0x000000b7]
    2017-05-12 19:33:56, Error                 IBSLIB Failed to export alterations to firmware. Status: c000000d[gle=0x00000002]
    2017-05-12 19:34:12, Error                 IBSLIB Failed to export alterations to firmware. Status: c000000d[gle=0x00000002]
    But i cannot find anything about them?
    Friday, May 12, 2017 6:39 PM
  • Hi Franz Stadler,

    Please consult User's Manual of your mother board.
    https://www.asus.com/us/Motherboards/H170-PRO/HelpDesk_Manual/

    And read especially Boot related sections.
    ___________
    Ashidacchi
    Sunday, May 14, 2017 3:19 AM
  • Hello @all,
    as there was no solution to find, i gave up and did clean install instead of upgrade.

    Anyway thanks for the help and the solution trials!

    Franz

    Friday, June 16, 2017 11:43 AM
  • Hi,

    I'have same problem. I can't reset with Windows 10 PRo Creator  : 0XC00000bb

    Installation Windows is new and all components too  : X299_Deluxe, I9 7900x,  GTX 1080 Ti, 960 PRo 1TB NMVe,  4x 16Gb Corsair 3000 LED.

     I pass 2 days to try resolve...

    No probleme with 1607
    Friday, July 28, 2017 4:35 PM
  • try to:
    1. change legacy mode, instead of UEFI, in BIOS settings. 
    2. do a Disk Cleanup including System files.

    Ashidacchi


    • Edited by Ashidacchi Saturday, July 29, 2017 4:10 AM
    Saturday, July 29, 2017 4:08 AM
  • I got the exact same problem. 

    What i've tried so far:

    - update BIOS

    - update SSD firmware

    - update SSD driver

    - changed UEFI/BIOS settings several times including default settings

    - tried installing windows 10 with media creation tool

    I still get the error code on reboot when i attempt to install either the creators update or windows itself (upgrade option)

    Any other helpful ideas?


    • Edited by eskiim0 Sunday, September 10, 2017 1:58 PM
    Sunday, September 10, 2017 1:56 PM
  • Got it. Don't use a Creators Drive whatever. Tried it.

    In BIOS, just select "Windows Boot Manager" as your primary boot, not the name of your drive (e.g. Samsung 950, etc.). You would THINK that putting the drive name tells it to look for that drive, but it doesn't. Putting "Windows Boot Manager" sorts it. Updating like normal now.

    Have an MSI X99 Krait edition Mobo.

    :)

    JM

    Monday, December 18, 2017 11:00 AM