Windows 8.1 Install Error 0xC1900101-0x20017

I tried most things that people here suggested and none were the problem with my Asus u43jc laptop. 

Things that didn't work:

Running msconfig and disabling all non Microsoft services

Disabling wifi, ethernet drivers in device manager (I also disabled audio and logmein drivers)

Installing the latest nvidia graphics drivers. 

Installing all required and optional windows updates.

Other things I didn't pursue: 

1. I have a ssd and had various windows installation and other issues with it. 
2. I didn't mess with any system devices in device manager.

Just thought I'd share so others avoid wasting time.  I'm not gonna bother with 8.1 again until January, hopefully this nonsense has been fixed by then.

@Dominique Gauthier,

If you bought a Windows 8.1 or Windows 8 product key, you can download and install Windows from this page. You'll have the option to install Windows now, later, or using media with an ISO file.

http://windows.microsoft.com/en-us/windows-8/upgrade-product-key-only

I have been suffering this error since the RTM was released and I had resigned to wait it out until reading the threads here.

I haven't posted as I had no problem installing the RTM on both x86 and x64 Laptops and Desktops and thought the error code message on the one computer was due to the fact it is an old Black MacBook Core Duo which I assumed was the major cause of the failure of 8.1.

I had upgraded the Bootcamp Windows 7 to Windows 8 flawlessly on the MacBook last December and thought the RTM x86 of 8.1 would be flawless as well.

Wrong!

Since I couldn't get the RTM to install I just waited until the Windows Store Update was released and began to try to update which resulted continuously in the dreaded 0xC1900101-0x20017 error.

Today I succeeded in updating to Windows 8.1 x86 using the Windows Store.

I can confirm it is a driver issue as the install finally succeeded after removing additional programs and drivers.

I suspect it is the Magic Iso / Magic Disc drivers but I can't positively state this because I also removed the Intel Desktop Manager software at the same time so it may as well be just the Intel Desktop Manager Drivers.

After removing these drivers I ran MSCONFIG and disabled all the Services including the Microsoft Services. I then used Task Manager and disabled all the Startup items.

I then rebooted, went to the Windows Store after the reboot, and started the Windows 8.1 Update again  for the 8th or 9th time.

I trully expected the dreaded 0xC1900101-0x20017 error but amazingly after the restart Windows 8.1 fully installed and I am posting this using 8.1.

This is definitely a Driver Conflict Issue and if I can get it running on an old MacBook with all the additional inherent Bootcamp issues you can as well without resorting to a Refresh wipe.

Hopefully it is the Magic Iso /Magic Disc or Deamon Tools ( or perhaps the Intel Desktop Manager) drivers that are causing the issues so let us know if this works for you so we can put this error to bed once and for all.

If not then the only solution is a methodical step by step uninstall of suspected drivers.

My problem when I disable all the services is that windows store can't connect to internet to load the install. How did you manage?

If installing from Windows 8, begin with step 1.

 

1. Reset pc
2. Open Windows Updates
3. Install important updates
4. Install optional updates
5. Go to Windows > Software Distribution and delete contents of the folder (do not delete folder)
6. Run Disk Cleaner
7. Clear Windows Store cache files

Press Windows Flag key + R

Type WSreset.exe

Press Ok

8) Download Windows 8.1

Before wiping PC, simply download update and turn off wifi or internet connection before installation begins as recommended by Ricard2798. It worked! (At least for me). And, does not require reinstallation of programs with all the problems of getting special reinstallation numbers from software providers, etc. as would a PC Reset.

I am surprised Microsoft has not discovered the problem and simple fix, if that is the problem. There are a whole raft of people out there having this same problem. I had to chuckle when folks using Fusion 6 (whatever that is) were told by Microsoft that it must be a Fusion program problem.

A Fix? THIS WORKS! (At least for me). I had tried everything else (other than wiping PC with a PC Reset as apparently recommended by Microsoft (?). In my case, after downloading, but before installing, turned off wifi, let it install (which it did), and then turned back on wi-fi. Did a WSreset.exe earlier without success, but that might have helped perhaps. None of the other stuff, including disabling/safe boots, etc. worked.

I am surprised that Microsoft would mislead people into wiping their entire computer instead of actually looking at a log to find a less invasive fix. Thank you for your help Ricard!