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
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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?
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.
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
I've tried this now over 10 times. I was hopeful, that the new Nvidia Drivers would solve the issue, but no.
I've updated bios two times, I've updated all drivers in my computer, I've tried clean boot, chkdsk/r, disabling all non essential devices, uninstalling all nonessential software.
I think it would be time for MS to acknowledge this problems and fix the update.
It's amazing.... ten days and no announcement... MS have failed with your costumers and have no respect with them.. I give up… I won’t try again until new windows release… Sorry, I’ve never considered before to use Apple because of cost but maybe this time have arrived..
For the last week I have been having the same problems as have been listed here and tried just about all the suggestions mentioned in the various posts. Out of frustration I lugged my desktop ( a bits and pieces machine) up to the room where my modem/router is and connected it by Ethernet cable and disabled the wireless connectors, I also connected my old cabled mouse and keyboard and disconnected my wireless mouse/keyboard. HEY PRESTO the update worked after nearly 20 attempts using the wireless connection it work first time with the wired connection. The strange thing is all the wireless connections worked 100% after the update finished ( It does take a long time) without having to update any drivers and a Dell printer which had always refused to work with Windows 8 installed perfectly in Windows 8.1 just by plugging in the USB connector. I hope this experience might be of help to someone but why the install wouldn't work over a wireless connection when all the drivers were correct puzzles me.
Thanks for the heads up - which wasn't the first time I have read about this approach.
I'm glad it worked for you - unfortunately, it made no difference to me. I disabled the wireless adapter and booted, updated and rebooted with a live LAN connection to no avail. Same error.
MS, this problem seems to have been around for months, as identified in posts concerning the preview version. I ask what has been asked before - what is the point of trialling software if you do not rectify the problems that are reported ahead of the release version?
I have now:
3, Tried older and newer Intel graphics drivers (note, I only have an Intel graphics board, not a dual graphics system).
None of these approaches has improved on the situation.
MS I have to say you have delivered an almighty CU in your implementation, and what really riles is the fact that this has been known (through the Preview version) for months.
Much more of this and I will be joining the queue for a Mac.
One hitch I had with the AMD HD 7600 series beta drivers is that I lost overscan after the upgrade. This problem is fixable with a simple registry hack found here: