"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-11-16T16:17:27+00:00

    What's interesting about all this is that MS shortened its development life cycle to attempt the one year deployments like their competitors.  It would appear to me that they aren't equipped to handle this.  8.1 is not ready for prime time, it fails on a very large number of devices, and even after you spend days trying to get it installed, and even resorting to customer support (like I did), it fails on other fronts (I ended up reverting).  I especially loved the part where installing SideWinder drivers caused the PC to infinitely reboot - THEIR OWN PRODUCT.

    On the older PCs running 8, it just flat out wouldn't allow installation.  A service pack changing hardware requirements?  What's wrong with you Microsoft??  

    Anyhow, I've been running it on my Yoga 13, and am fairly happy on that front, but I did notice a decrease in 3D performance from the HD4000.  

    8.1 is a slight improvement on some of the UI and disk fronts, but overall, this is a massively botched release.  This is perhaps the worst I have seen come out of Microsoft, and I've been with their products a REALLY long time.  If they can't fix their stuff by the next release (and if the trend continues like this), I may have to go back to 7, or if they ever find a way to make Linux the dominant gaming platform, I may have to do what I swore I'd never do: move (at least for my gaming PC).

    This sucks, Microsoft.  Sorry, but this unacceptable on every front.  I think Windows ME had a better launch... seriously.

    Kudos to their die hard support, but as far as attempting a one year release cycle?  F-A-I-L.  Microsoft has lost their way in a way I never would have expected...  

    You win Microsoft... I give up.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-11-16T15:49:50+00:00

    <sigh>

    Just tried again: after one month no miracle cures.

    -Cleaned up drivers (updated everything I could get my hands on)

    -did a clean boot.

    -disconnected logitech g19 keyboard & replaced with a generic one.

    No result. Anyway to get decent error handling in this upgrade so the can get a clear diagnosis?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-11-15T20:03:04+00:00

    Sad part is that Microsoft is huge and this is still ongoing.

    Just kind of looks VERY bad on their PR department.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-11-15T12:09:18+00:00

    I also have a Ralink RT3290 and have the same error. Im on a HP Envy Ultrabook 4

    Was this answer helpful?

    0 comments
  5. Anonymous
    2013-11-15T06:29:47+00:00

    even i installed all the updates and reoved the softwares that were not suggested by windows upgrae assistant.............!! but still amgetting the same error

    my system is HP pavillion e001ax

    with amd a10 quad core 2.5 ghz processor

    ati readon dual graphics

    8gb ram

    Was this answer helpful?

    0 comments