Couldn't Update to Windows 8.1 – 0xC1900101 – 0x40017Couldn't Update to Windows 8.1 ? 0xC1900101 ? 0x40017Some users are still struggling to update to Windows 8.1, with more and more errors experienced during the downloading or the installation process.
Now a number of consumers are reporting problems with the Windows 8.1 setup, just after the point when it is supposed to get devices ready for the new operating system.
An error reading "Couldn't update to Windows 8.1 - 0xC1900101 - 0x40017" is displayed all of a sudden, with the installer then restoring the previous version of Windows.
I'd recommend that anyone running the update to 8.1 make sure the system files and the component store files are not corrupted which is a very common and ongoing problem with Windows 8. The link shows which commands to run.
That 0x40017 error is what I got when trying to update from Windows 8 to 8.1 preview. My upgrade from Windows 7 to Windows 8 went almost flawlessly. Big time issues with the 8.1 preview install. None of those clean install, refresh the store solutions worked for me nor many others reporting the same problem on the Microsoft Community. Microsoft sent me a note to pass them an error log which I did but never heard back. I was being told on the forum that this error is memory related and I likely had bad memory (hardware) and to do a 24 hour memory test. No thanks. Nothing wrong with my system memory and two other guys I know with the exact same system were getting the same error. We all have bad memory LOL.
I always keep my drivers up to date. I noticed from device manager that at the time of the preview a suggested update to my raid controller was a driver over three years older than the driver I had. The driver I had was the recommended one from the Intel site. Out of curiousity I tried to update or maybe "downdate" to the Microsoft recommended driver from device manager. On reboot Windows 8 hung exactly like the preview and I had to use a restore point. Sent a note to Microsoft that the preview problem might be driver related. At least I see they are mentioning driver bugs now as a possible reason. Never heard back but I am glad to report the 8.1 final release update went flawlessly for me. So seems my problem was sorted out but I see that error code remains an issue for others even in 8.1 final. I feel their pain. Brink should go over there and help them.
Well, I got an error code on one of my W8 tablets. I uninstalled a couple of programs that were very old. I thought they might be the problem. Who knows? I then used CCleaner to clean up registry and other stuff. Then the upgrade worked just fine. So, what did I do that made it "take" the second time? No clue. Sumpin' did.
I had a 0xC1900101-ox30018 error code. As others have said, many codes these days just tell you that something went wrong. I looked over the programs I had loaded and decided to remove a couple that the upgrade might not like. Upgrades are tricky sometimes.
I also download the latest CCleaner and did a total clean and registry fix/clean. Then tried it again. This time the upgrade did just fine. So, something I did allowed the upgrade to progress all the way!
So, now I will try to install the older programs and see if they play nicely with 8.1.
I also have this problem , also when I update ( try to ) to Windows 8.1 , it crashes at the part where it says "getting started" with the circle with the dots what spin around as to show that its loading but when it gets around 35% , it just crashes and I have to manually restart my PC So annoying!!
Please help! - BTW , I don't have Windows 8.1 Preview ... Is that needed?
Many Thanks ,
Windows 8.1 Error: We Couldn’t Update System Reserved Partition
Windows 8.1 Error: We Couldn?t Update System Reserved PartitionWindows 8.1 was initially supposed to be available via seamless update from the Store, but it turns out that the whole migration to a new OS is becoming more like a serious problem for users worldwide.
This time, consumers are reporting issues with the system reserved partition, as the Windows 8.1 installer displays an error after launching the compatibility check.
The error code is OXC1900104, according to one of the users who posted on Microsoft’s support forums, but no other details on how to fix it have been provided.