And the fundamental problem in all of this is that the windows 8.1 upgrade failes due to something it detected but the upgrade software/process does not report the problem that was encountered.
bob
"Couldn't update to Windows 8.1 - 0xC1900101 - 0x40017"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
891 answers
Sort by: Oldest
-
Anonymous
2014-12-29T00:06:57+00:00 -
Anonymous
2014-12-29T00:19:44+00:00 And the fundamental problem in all of this is that the windows 8.1 upgrade failes due to something it detected but the upgrade software/process does not report the problem that was encountered.
bob
YES! That is precisely the problem! I have followed this thread and done everything suggested, but the upgrade still fails--but does not tell me why!
-
Anonymous
2014-12-29T01:50:08+00:00 done everything suggested
I don't think so.
<quote>
You need to dig out the logs.
</quote>
-
Anonymous
2014-12-29T04:17:57+00:00 Dig out the system logs? What are we, system programmers? That's what MS should be doing. Reading through system logs to perform what should be a straight forward update is beyond reason for the non-technical user. And as you probably know, the system logs can be misleading and in many cases, are only a starting point to possibly finding answers.
This is not a good recommendation for most users. If it was all that simple, this problem would have been solved a good while ago.
David B.
-
Anonymous
2014-12-29T07:13:42+00:00 Dig out the system logs? What are we, system programmers? That's what MS should be doing.
When MS connect to people remotely I imagine that they will do something like that to understand the symptoms. In this forum we are discussing self-support techniques, so instead of just bleating about the useless clue being seen I think eventually someone who is interested enough will have to do just that: find supplemental clues. When that happens hopefully they will share whatever they learn and maybe even encourage some of the less adventurous to look at the same sources for their specific clues.