"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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2013-11-23T08:44:24+00:00

    Trying to look for log files, I ended up searching in the directories C:$Windows.~BT\sources\Panther

    and C:$Windows.~BT\sources\Rollback

    I could not really find an indication in the log files, but in 'setupact', which seems to keep track of the process, I found repeated occurences of "Arch=AMD64", such as in

    Source OS: Host SKU Info: Edition = 'ProfessionalWMC', Edition Type = 'Complete', Product Name = 'Windows 8 Pro with Media Center', Arch = amd64, StationType = Client Workstation, Stage type = Staged Image

    which is strange, because my PC runs on an i7 3930, which is an EM64T architecture.

    Does the upgrade process mess up the CPU types? I know this seems weird, but in the absence of any other useful information...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-11-22T13:46:12+00:00

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-11-22T13:42:47+00:00

    Feel just the same.

    They have to be aware of the problem so why no 'Official' comment?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-11-22T08:54:04+00:00

    You are missing the point, we should not need to do this it is Microsoft problem not ours. thanks for the help anyway. We just want Microsoft to say something about it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2013-11-22T08:38:43+00:00

    That's just the way I feel about it Kev.

    Was this answer helpful?

    0 comments