"Couldn't update to Windows 8.1 - 0xC1900101 - 0x40017"

Anonymous
2013-10-17T13:29:23+00:00

I have downloaded the Windows 8.1 update from the store but cannot get it to install. Each time I try, I get to the point where it is "getting my devices ready", then the PC restarts to a blue screen with error message. It then tries to recover the installation, fails, then restores Windows 8. When the system boots up after this, I get a message saying:

"Couldn't update to Windows 8.1

Sorry, we couldn't complete the update to Windows 8.1. We've restored your previous version of Windows to this PC.

0xC1900101 - 0x40017"

There is n o explanation as to why the update could be completed. Any ideas how to resolve this?

Windows for home | Previous Windows versions | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

891 answers

Sort by: Newest
  1. Anonymous
    2013-12-06T16:04:55+00:00

    This sounds interesting, so I ran the setup again and eventually the windbg.exe points to "disk.sys"!! I guess there is a kind of incompatibility with my SanDisk SDSSDH2256G disk drive?? The driver "disk.sys" is manufactured by MS and I have no idea on what to do next. 

    Thanks MS for helping us!!!

    if you have a solid state express drive it may be the driver for that, or an incompatibility with the program that manages it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-12-06T02:56:13+00:00

    UPDATE:

     

    Following a suggestion from one of your colleagues on a similar thread, I tried running a clean boot and installing the upgrade from there. Again, this had no effect.

    Hi Martin,

    What is a clean boot? You've solved this issue?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-12-05T19:18:05+00:00

    This sounds interesting, so I ran the setup again and eventually the windbg.exe points to "disk.sys"!! I guess there is a kind of incompatibility with my SanDisk SDSSDH2256G disk drive?? The driver "disk.sys" is manufactured by MS and I have no idea on what to do next. 

    Thanks MS for helping us!!!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-12-04T19:43:57+00:00

    I had this problem to, but after i attempted to install the update, and i got the same problem as you had, my computer performance dropped extremely. I used to play games at maximum graphics but unless i put my graphical settings on minimum i cant even play anyting. I even had a hard time typing this text and browsing for this question due to the lag. Please help!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2013-12-03T15:24:31+00:00

    After trying everything described here (except a clean install, because I wanted to keep my applications) I looked into a crash dump file (in C:$WINDOWS.~BT\Sources\Rollback) using windbg.exe (no idea why I haven't done that earlier ...). This told me what the probable crash candidate was: The ueye GigE camera driver. AND: This was correct. After uninstallling the ueye software including the drivers the update went through. 

    Maybe that helps at least some of you ...

    This is very interesting -- thank you for sharing. I found several files/drivers it mentions -- how were you able to tell which one was faulty? I see several pieces of software it mentions which could be problematic.

    This is great information and could be helpful for anyone that is crashing during the upgrade.

       Does anyone know if there are other log files created by the Windows 8.1 upgrade? My system doesn't blue screen so no dump files are created. It just finishes the install and then goes to a black screen with mouse and never makes it to a desktop. As others have said, upon reboot, it rolls back and throws the error on this thread.

       Has anyone found other logs because if I could find the driver causing it, I could work around that issue. I tried to read all of this long thread but I could have missed it, so I apologize if this has already been covered.

    Was this answer helpful?

    0 comments No comments