"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 No comments

891 answers

Sort by: Oldest
  1. Anonymous
    2015-06-15T20:36:31+00:00

    my motherboard is P9x79PRO, it seems to be the culprit, I yet to try disable the wireless in BIOS, what is this wireless issue you mentioned, do you happen to have the source? cheers.

    It was on one of the many pages I looked at, but it does not appear to be the case as I disabled it in the BIOS and I still received the error.

    Others had success, but I am not sure what they system specs were.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-06-15T20:40:06+00:00

    I was able to find the dmp file, but unfortunately it did not provide any useful information:

    On Sat 6/13/2015 3:30:42 AM GMT your computer crashed

    crash dump file: C:\Windows\Minidump\setupmem.dmp

    and how did you find that minidump? how to enable it? I didn't find any solution for enabling that despite the fact I got minidump enabled in the system.

    It was somewhere in the hidden folder for the update, on my system it would be in one of these folders as setupmem.dmp   C:$Windows.~BT\Sources\Panther 

    I tried the upgrade a few more times and they did not create a dmp file and the previous one appears to be gone now.

    I disabled everything I could in the BIOS, disconnected all but the Primary Drive and moved it to the Intel SATA channel and it still refused to complete the upgrade.

    I don't understand why it shows the mouse cursor twice during the upgrade process (each before a reboot).

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-06-15T23:01:39+00:00

    I don't understand why it shows the mouse cursor twice during the upgrade process (each before a reboot).

    That could be a clue.  Do you have Touch?  You wouldn't need your mouse then.  In fact, I'm not sure but you might not need it at all anyway, especially if you can get Mousekeys working and have a full keyboard (or at least a real Numeric keypad) to run it.  Or if you have another mouse you could try using it instead.

    BTW you may find some easier to interpret clues in the *.log files in that same Panther directory.

    Good luck

    Robert


    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-06-15T23:42:29+00:00

    I too have a P9X79 Deluxe motherboard.  I was finally able to install 8.1 from a complete reinstall of Windows 8.0, something I was resisting for a long time.  My point though is I reinstalled with whatever Version 8 had to offer in drivers - non of my own Asus, NVIDIA, Intel, etc. drivers were used.  I also disconnected all non-essential peripherals before the reinstall.  Once Win 8 was reinstalled, I installed 8.1 (as an update) without a problem. I then hooked up all left-out peripherals and installed all my own drivers.

    I agree, its a pain, especially when you have a boat load of programs that have to be reinstalled afterward, but there is something to be said about unloading accumulated junk and non-essentials.

    Anyway its over for now and it worked.  Hope this gives you hope.  Until next time.

    David B.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-06-16T12:30:12+00:00

    I checked setupact.log and found the code 0x40017 at the very end of this large file, but I don't have a clue where to look for the error, I search 'error' through the log file couldn't find anything interesting.

    now I wonder how can I send this file to Microsoft.

    Was this answer helpful?

    0 comments No comments