"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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-10-22T14:53:01+00:00

    Has there been any official update by Microsoft on this?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-10-22T14:57:44+00:00

    I was running into the same problem with my Lenovo W520. After many unsuccessful attempts to update to 8.1 from 8 I was able to upgrade.

    I tried installing all Windows Updates, all Lenovo updates, and even the NVidia drivers from their website (which wasn't part of Windows Update). Everything failed until I enabled the integrated video card (disabling optimus and the Nvidia card) on the BIOS. I then rebooted and was able to upgrade to 8.1

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-10-22T15:16:07+00:00

    NVIDIA users ---

    Can you check your nvkflt.sys file and see which version it is?  Does it match the version of the NVIDIA drivers that you have installed?

    You can check this by navigating to C:\Windows\System32\Drivers in Windows Explorer.  Find nvkflt.sys and hover over it to get some information, you should be able to see the version number on the first line.

    The version should match the version of the NVIDIA drivers that you have installed.

    Mine shows as 320.00 (or 9.18.13.2000), which is OLDER than the current version of the NVIDIA drivers I have installed (320.96).

    I've confirmed that newer drivers do indeed come with a newer version of this file, but for some reason is is not being installed properly.  I've updated my drivers two or three times since 320.00, and again I am currently running 320.96.

    If you try to upgrade the NVIDIA drivers to the 325 series or later, but nvkflt.sys is not updated, you'll get a BSOD (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED blaming nvkflt.sys).  I believe this is [at least part of] what is messing up the Windows 8.1 upgrade for me, as it will try to install a 325-series driver during the setup process.

    Having discovered this, I haven't tried to fix it yet, I won't have time to do that until this evening, but I was wondering if anyone else noticed this version discrepancy.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-10-22T15:32:16+00:00

    Not that I'm aware of.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2013-10-22T16:29:26+00:00

    I have the same error on my hp dv6-7012tx. Whats interesting is that the install process has a compatibility check and it doesn't show any errors. If its indeed the problem with the drivers it should have been shown at the time of the compatibility check and that would have saved us  lot of time. For the past two days all i have done is go through various forums and try everything hoping that it would work. They said the problem was with Nvidia drivers. I updated to R331 but still no use. When someone releases a product that's consumed on such a large scale care must be taken so avoid these kind of painstaking experience for the early adopters. This is really shame on microsoft.

    I guess I'll have to wait so that they release a stable version(the same error existed for consumer preview also i read elsewhere, if they didn't correct the bug for a preview I guess we really wil have to wait for a long time)

    Was this answer helpful?

    0 comments