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

Hi,

I,ve also tried it for the 7th time to install this update with the new nvidea drivers that came out

Same issue here.  Dell XPS15, i7 Quad Core

I also cannot install the update my system is:

Maybe someone on here can help me with my custom built PC.

 

I attempted to update my Windows 8.0 to 8.1.  Everything seemed ok until it got to one of the final automatic set-up screens.

 

At 24% it just got stuck for a whole day.  So I restarted the PC.  Now there is no way back.  It takes about an hour to get to a maintenance screen - but no safe mode button is on the screen.

 

I am given the option to install Windows 8 or 8.1, but neither work.

 

The SSD appears to be locked if I try to role back to Windows 8.  Windows 8.1 to loops back to the start after about and hour of thinking.

 

I get the  feeling that W 8.1 does not like the Quadro FX graphics card drivers, but I cannot get into safe mode to disable the drivers.

 

Basically I have bricked PC and 256GB SSD is locked.

 

I cannot even manage to get run a clean install from my Windows installation disk.

 

Any help would be appreciated.

 

Bill

Hi,

the only solution to resolve the issue that you are getting is to remove the Wireless adapter, if its a laptop will be a difficult. Desktop I believe you can take it out.

Also  check for the BIOS update

Regards

JA

FYI, I have now tried (as well as lots of other steps reported previously):

1. Removing all non-MS services from startup.

2. Disabling all on-board options but WLAN in BIOS, installed W8.1 upgrade, rebooted, ensured WLAN was also now off, rebooted, same problem.... grrr.

3. NB BIOS is latest.

Considering I have a laptop that is from indusry leader HP, with industry leader Intel hardware, and with MS as the third leg of the triumvirate, I think whatever MS has done with W8.1 is unbelievably poor.

12 days on and still nothing tangible from MS.  I'm very unimpressed.  I think what MS does not appreciate is that we use PCs as machines for work, not as an end in itself.  In other words, "it should really just work" and not require the user to go through hoops from a company that has tens of thousands of employees and yet can't get their core product working right or have the decency to make a proper public statement.  Anyone can make a mistake - we all do - but to hide behind silence is not very professional.

I give up.

There is a method of getting the F8 boot menu options back in Win 8: http://www.bleepingcomputer.com/tutorials/enable-the-f8-key-in-windows-8/

I am pretty disappointed too that there has been no fix or even a real acknowledgement. I've tried various things (disabling hardware, BIOS settings, upgraded AMD drivers, clean boot, CHKDSK, updating drivers from the manufacturer --- nothing works).

Same error.
Same silence from Microsoft -- other than some deleted posts.

Surface Pro with Windows 8 Professional x64, Microsoft Type Keyboard (version 1), Microsoft Bluetooth Mouse. No other devices connected.
All updates installed except optional Bing Desktop and Bing Bar. No question marks or other errors in Device Manager.
RealVNC, Notepad++, Office 2013 Professional, Legacy 7.5, Intermapper Remote Access, Googloe Earth, Mozilla Firefox, Adobe Reader XI installed.

Same error as others, 0xC1900101 - 0x40017...

It is very frustrating. Two machines updated without issue.  A third just will not update.  I have tried literally dozens of times with every suggestion offered.  I was sent a PM by one of the Microsoft engineers with a link to a set of diagnostic tools.  I also received an email from another engineer with the same link.  Since then no further contact.  The problems really don't bother me, but the lack of support and slowness of response is troubling.  Many users began reporting these issues at the preview launch in June, but I never tried installing the preview on anything other than a fresh VM as a test platform.  The update failure I am experiencing now is on a production machine and happens to be my primary machine.  The secondary machine updated easily on the first try.

It just seems strange to me that we are completely unable to drill down and decipher the root cause of the BSOD crash on reboot.  It is also strange that all three were very stable Windows 8 machines, yet the update seems to fail due to a driver issue.  How could a simple incremental update render a working driver buggy?  At this point I have invested all the time I care to trying to resolve this issue.  I will just have to hope that an answer is provided soon. 

Almost 2 weeks and from Microsoft - crickets.