"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

891 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-12-08T20:19:34+00:00

    I tried it twice--it didn't work and took all day and I lost almost everything--but went to systems restore and got everything back--BUT NOW I STUPIDLY TRIED TO GET WINDOWS 8.1 AGAIN AND THIS TIME I LOST EVERYTHING AND CAN'T GET SYSTEMS RESTORE BACK--SO WHAT DO I DO????????  HELP!!!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-12-08T20:05:37+00:00

    Wi-Fi, Bluetooth and Card readers were found to be common factors associated with this error. We recommend as a troubleshooting step disabling the drivers for Wi-Fi, Bluetooth, and Card readers, if they exist, to help resolve this issue.

    Other known drivers that have been shown to cause this error:

    · Drive-encryption software. Make sure your computer is not running any drive-encryption software and decrypt the drive before updating to Windows 8.1.

    · Check for and uninstall any desktop utilities that may be running. Uninstalling IObit or Intel Desktop Utilities (including Extreme Tuning software but excluding Managed Engine) has been observed to resolve this issue

    regards,

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2013-12-07T13:42:19+00:00

    WOW. page 56 and how many months later we are still dealing with failed installs. What, is Microsoft seeing we are fixing it ourselves and just brushing fixing the actual code under the rug?

    Very good idea Sorein, that would definitely help. As far as developing our own program to decode it, most likely near impossible, as you would have to have a Microsoft error code dictionary. And don't punish the developers too hard. The real fault most likely lies in Microsoft trying to shove this out too soon before the developers were finished.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2013-12-07T13:28:41+00:00

    That seems to be a good contribution to our struggle of getting stubborn Windows 8.1 installed. It points out that there might be some data on what went wrong. Also in that folder (C:$WINDOWS.~BT) one can find a number of error.log files. Unfortunately they are too cryptic (and frugal) for even people with some PC experience to figure out what was wrong. We can only hope this:

    1. Either Microsoft redesigns the error logs. Is would be very simple to generate something like this:
    • engage driver XXX - success
    • engage driver XXY - success
    • engage driver XXZ - failure
    • Windows instalation halted. etc
    1. Or experienced users try to courteously design some widget to interpret the error logs and the crash dump files.

    Otherwise, this fight to cheat Windows 8.1 into getting installed is becoming stupid. Of course, there are multitude of configurations, but this installation is very poorly designed. That shows the increasing incompetence of the younger generations of programmers.

    These installation errors occur mainly because some software or hardware component is not to the liking of Windows 8.1. -  a driver, some registry entry, a video/sound card, an external device (disk, USB).... It really is not hard to modify the installation kit towards pointing exactly to the device in question.

    Sometimes, suspending/removing the problematic item will let Windows 8.1 get installed and reapplying the item will generate no new problem. Other times, reapplying that item will lead Windows 8.1 into a BSOD, so that item might be used never again.

    My particular case was an older SB Live (sound card). Windows 8 already had a problem with that. I could only identify that because of the BSOD type: BAD_POOL_HEADER. Removing the sound card, allowed Windows 8.1 to install, but replugging it made Windows 8.1 not start. I "cheated" both Windows 8 and 8.1 with an adapted 3rd party driver (kX Audio Driver).

    Was this answer helpful?

    0 comments