"Couldn't update to Windows 8.1 - 0xC1900101 - 0x40017"

After trying everything described here (except a clean install, because I wanted to keep my applications) I looked into a crash dump file (in C:$WINDOWS.~BT\Sources\Rollback) using windbg.exe (no idea why I haven't done that earlier ...). This told me what the probable crash candidate was: The ueye GigE camera driver. AND: This was correct. After uninstallling the ueye software including the drivers the update went through. 

Maybe that helps at least some of you ...

This is very interesting -- thank you for sharing. I found several files/drivers it mentions -- how were you able to tell which one was faulty? I see several pieces of software it mentions which could be problematic.

This is great information and could be helpful for anyone that is crashing during the upgrade.

   Does anyone know if there are other log files created by the Windows 8.1 upgrade? My system doesn't blue screen so no dump files are created. It just finishes the install and then goes to a black screen with mouse and never makes it to a desktop. As others have said, upon reboot, it rolls back and throws the error on this thread.

   Has anyone found other logs because if I could find the driver causing it, I could work around that issue. I tried to read all of this long thread but I could have missed it, so I apologize if this has already been covered.

Thanks for the hint. my Minidump directory is empty. so it could'nt help.

looking around in the log files, i found in Panther\setuperr the following lines;

Failed to get image properties for syswow64\drivers\asio.sys: 0x80070003

Failed to get image properties for syswow64\drivers\asupio.sys: 0x80070003

Failed to get image properties for syswow64\drivers\asusfilter.sys: 0x80070003

These 3 are, as it seems, typical ASUS drivers, I believe for monitoring purposes.

Did anybody else come across this? is this meaningful?

My motherboard is an Asus Sabertooth x79 with an i7 3930...

thanks

I also wasn't able to upgrade to Windows 8.1 on my new Dell XPS12 (got it in late October). 

After reading your comment, I decided to try to uninstalled Displaylink drivers (removed Core Software and Graphics) and try my luck.... and bingo, it worked. 

After the upgrade to Windows 8.1, I reinstalled DisplayLink (v7.4) and will need to update other glitchy drivers (touchpad for sure, and maybe others as they appear).

Thank you for you post with the suggestion of removing DisplayLink.

Wow, that is sweet that it worked. I just tried it on mine and it didn't. However, I am thinking that I might try a few of the other troubleshooting suggestions like wsreset, etc.

Did you have the latest Windows 8 drivers from DELL or had you started to put on some of the Windows 8.1 drivers from DELLs site?

I like a lot of Windows 8/8.1 but I really don't like the dumbing down of the F8(Safe Mode) system or the obscuring of the details of the patch install. I really which that Microsoft would give techs a complicated key sequence to press so we could watch what was going on behind the scenes. It might give us a chance to see what was failing and concentrate on that.

At least the rollback seems to work. 8^D I'll post back if I get it to work.

Thank you Lasse -- I went through the translated version. I cannot find DMP files in the same place (or any in Windows~BT -- so must be a different problem than what you may have. I do have some LOG files in there which it would not open up -- but I sitll think there may be something interesting in there. Thanks for the help anyway.

Sorry, I can't really say much more. I googled how to analyze Microsoft crash dump files and found this: http://blog.this.at/post/2007/10/23/How-To-Crash-Dump-analysieren-(Oder-Wer-ist-schuld-an-dem-Bluescreen).aspx (in German, but I gues there is something similar in English). Then I couldn't find a memory dump file in "C:/minidump/", so I searched the whole drive for *.dmp files and the only one was in "C:$WINDOWS.~BT\Sources\Rollback". It then told me only one "probably caused by ..." canditate. Thats it.