Windows 10: Windows 10 Anniversary Edition Update - Stubborn 0xC1000101 - 0x20017

Hello, chums

I posted this on answers.microsoft but it's slim pickings I'm afraid. Perhaps you can help:

Hello,



Background: PC is a custom build. (intel i7 Z77 @ 3.5 GHz, Nvidia GTX 970, 16GB RAM) I upgraded from Win 7 to Win 10 without any problems in November 2015. One thing I'll mention now that I'll come back to later: Due to my amateurish build, there are some idiosyncrasies with the disks on the computer. There are 4 HDDs in the tower and one SSD. One of the HDDs is not functional but that has been the case for a while and is not germane to the problem. The system drive is C:/, the SSD. However in Disk Management, the SSD is listed as the final disk, disk 3. Disk 0 is my largest harddrive, a 1TB number. The System Reserved partition is on Disk 0. When I run diskpart -> list volume in the command prompt, the SSD is volume 4. The System Reserved partition is volume 0, and volume 1 is the 1TB HDD where the SR partition resides. I have just noticed that when I go to System Information, the boot device is given as volume 1, as opposed to volume 4, the system drive.





So, the problem:



I used the upgrade assistant to try and upgrade Win 10 version 10586 to the Anniversary Edition, latest build. After downloading the update and running the installation, the system rebooted, went to the black screen with the win10 logo and white circle, rebooted again, went to that screen, then booted Win10 as normal. There was no indication the installation was complete, but nor was there an error message. Ran the assistant again, saw that it wasn't updated, tried again, same thing. Search internet. 'try installing with the Media Creation Tool'. Do that. Upgrade fails again and I get the error quoted above



0xC1000101 - 0x20017

The installation failed in the SAFE_OS phase with an error during BOOT operation



here is the Panther setuperr.log, which hasn't really changed no matter what troubleshooting I try:



2016-09-27 02:09:05, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1066): Result = 0xC1800104
2016-09-27 02:09:05, Error MOUPG CSetupManager::ExecuteInstallMode(735): Result = 0x800705BB
2016-09-27 02:09:05, Error MOUPG CSetupManager::ExecuteDownlevelMode(391): Result = 0x800705BB
2016-09-27 02:09:05, Error MOUPG CSetupManager::Execute(236): Result = 0x800705BB
2016-09-27 02:09:05, Error MOUPG CSetupHost::Execute(372): Result = 0x800705BB
2016-09-27 02:16:23, Error [0x0803b6] MIG Can't retrieve group information for user IIS APPPOOL\DefaultAppPool. NetUserGetLocalGroups failed 0x000008AD
2016-09-27 02:16:26, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2016-09-27 02:16:34, Error [0x0803b6] MIG Can't retrieve group information for user IIS APPPOOL\DefaultAppPool. NetUserGetLocalGroups failed 0x000008AD
2016-09-27 02:16:36, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: "id" attribute is mandatory. void __cdecl Mig::CMXEMigrationXml::LoadSupportedComponent(class UnBCL::XmlNode *,int,class Mig::CMXEMigrationXml *,class Mig::CMXEXmlComponent *)
2016-09-27 02:16:46, Error CSI 00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #82515# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216 (0x00060000), status = [6]"(null)", value = { type: 40972 (0x0000a00c), bytes ( 12 (0x0000000c) ): 65006e002d00550053000000 })
[gle=0x80004005]
2016-09-27 02:17:03, Error CSI 00000002 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #162486# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216 (0x00060000), status = [6]"(null)", value = { type: 40972 (0x0000a00c), bytes ( 12 (0x0000000c) ): 65006e002d00550053000000 })
[gle=0x80004005]
2016-09-27 02:17:09, Error [0x0803b6] MIG Can't retrieve group information for user IIS APPPOOL\DefaultAppPool. NetUserGetLocalGroups failed 0x000008AD
2016-09-27 02:17:13, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2016-09-27 02:18:21, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] Failed to get homegroup members with hr=0x8007000D
2016-09-27 02:18:36, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2016-09-27 02:18:36, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2016-09-27 02:18:37, Error [0x0803b6] MIG Can't retrieve group information for user IIS APPPOOL\DefaultAppPool. NetUserGetLocalGroups failed 0x000008AD



I have spent an awful lot of time this week searching the internet and trying to troubleshoot this error. I have actually forgotten all the myriad solutions I have attempted but don't recommend the standard ones to me, because I have tried them. Measures I have tried include:



- Mounting ISO to USB and trying to upgrade from that. Get message: 'Compatibility report: The computer started using the windows installation media. Remove the installation media and restart your computer so that windows starts normally. Then, insert the installation media and restart the upgrade'. This was a hiding to nothing.

- I've removed the wifi card

- I tried removing one stick of RAM (the system started with 8GB and around or after the time of upgrading the OS I had made it 16)

- Updated all drivers

- Removed hidden drivers in device manager

- run the installation without Ethernet cable

- Disabled windows firewall

- Removed the hyphen from my Machine's name

- Started a new local account on my PC and tried running the installation from that

- Deleted the DefaultAppPool folder and disabling IIS

- Clean Boot

- Updated BIOS

- Uninstalled CCleaner

- Removed the last vestiges of a McAfee program I had installed

- I formerly had an ATI graphics card in the machine which stopped working, and replaced it with the extant Nvidia card. The old ATI drivers and some folders/software were on the PC. Got rid of that, thought that would really do the trick. No dice.

- sfc

- DISM

- bootrec



You get the picture. As I'm sure you can appreciate, this has been an extremely time consuming process. I need a solution that is a little bit outside the box. Now, during the byzantine search for answers to this problem, I found some talk about partitions but nothing that clearly relates to my problem or that error code given up top. However, it seems this problem is Boot related generally, rather than boot + driver related, which is the default advice people receive when they cite that error code.



Now, I return to the information about my disk management. As you can see from the background info and these attached screenshots of disk management, list volume and system info



Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.



Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.



Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.



my disk system is in a state of slight disarray. Nevertheless, the PC functions perfectly well. From what I remember, when I built this system, the SSD and I think the 1TB HDD were new, and the other drives I moved over from my last PC, also a custom build. I forget exactly what the arrangement was, which disk had the previous version of Windows from the old PC on it, but in any case I managed to install Win 7 on the new system without any problems, and I was then able to upgrade that to Win 10 last year, also with no problems.



Is it possible the presence of the System Reserved partition on my non-system drive is causing this error? I remain increasingly convinced this is the likely cause, but am unwilling to try to fix this issue without seeking further opinion from those who know more about this stuff than I do. Nevertheless, it seems plausible. One of the other things I tried was disconnecting all other hard drives except my system drive (the SSD), and then trying the Win 10 Anniversary Edition update. But, with only the System drive connected (and not Disk 0 as per Disk Management, Volume 1 as per list volume), windows failed to boot, and, as I recall, I got the message after BIOS:



No bootable device - insert boot disk and press any key/restart



On the other hand, I don't understand why the win 7 to win 10 upgrade would be no problem, but an upgrade from within Win 10 to a newer version would be, on the same system. Beyond this, I'm at a loss, and I'm just kind of grimly fascinated at what the cause could be. But actually I am also hugely frustrated.


Incidentally, I tentatively tried to follow this YouTube vid Managing the System Reserved Partition in Windows 7 and Windows 8 - YouTube about relocating the System Reserved partition, but Disk Management wouldn't let me shrink the size of C:/



Please let me know if there's any more information about my system that you need, folks.

:)

 

Windows 10 Anniversary Edition Update - Stubborn 0xC1000101 - 0x20017 error - possible Disk Management issue?

Thanks very much for your input.

Drive A is just the letter that I allocated my largest HDD as there's no floppy drive in the computer and A is easy to remember. The System Reserved partition is still in disk 0/A after the reinstall but before I did the reinstall, I reallocated the boot
files from the System Reserved partition to the system drive using the Command Prompt, going by some instructions I found elsewhere on the internet. This was successful insofar as the computer was able to boot without Drive A attached, but it still did not
fix the update problem (indeed it was at this point that I gave up and resolved to do a clean install). So, the SR partition is still there in Disk Management but it is no longer marked as Active or System in Disk Management. I'm not really sure what the potential
consequences of the current state of the SR partition might be, though.

It occurred to me that the curious labelling of the disks was from a mistake I made when building the computer and attaching the SATA cables, as the order of the disks essentially seems to be the wrong way around. I could change it all over, but as the PC
is largely functional I'm kinda reluctant to at this point.

As of now there's only one partition marked Active on the computer (the C:/ drive/system partition that Windows is installed to, the SSD)

The reinstall did indeed clear up a lot more space on the SSD.

Thanks again for your tips

 

Windows 10 Anniversary Edition Update - Stubborn 0xC1000101 - 0x20017 error - possible Disk Management issue?

no solution was forthcoming and so I had to do a clean install, which was not ideal and has had unintended consequences.

For more information, look at a reply to a duplicate of this question I asked on a separate forum:

Windows 10 Anniversary Edition Update - Stubborn 0xC1000101 - 0x20017 - Windows 10 Forums

the short of it is that this essentially seems to be a bug present in the Anniversary Edition update.

This would ordinarily be fine, I would have no problem waiting for a version of the update that resolves the problem. Except that Microsoft effectively forced me into updating in order to run some software that I spent a non-negligible amount of money on
in their own store - there was a claim that an OS update was required but it was a wholly unconvincing, and something that as far as I can remember is unprecedented in my 20+ years of PC gaming. It was simply a transparent attempt to force a number of Win10
users into an OS update, which again would be fine, if the update worked for me. And so, a vicious circle. Not good enough, Microsoft. Besides the money spent on the software that I could have got refunded, even though I shouldn't have had to, I easily spent
24+ hours trying to remedy this problem which Windows support channels simply did not know how to rectify, if they knew of its existence in the first place. Again, and I can't stress this enough, that's not good enough for a situation that should have been
avoidable - bugs happen, forced OS upgrades to use products from a storefront linked to the OS need not.

 

I have had a similar problem on my Dell Vostro 1720 notebook. You can see my thread from about a week ago here. After working with this for many days and reading everything I could find, I have come to the conclusion that this error is not necessarily caused by driver conflict, and further that it is not likely that a solution or workaround can be found. I could be wrong, of course, but I stopped spending time on trying to find a solution. I really wanted the new version of Edge on this computer so I could install browser add-ons, but... Oh well.

Edit: I found an interesting post here. You and I have vastly different systems, but apparently the same type of issue. The solution in this post would not apply to either of us, but the following description excerpted from his post describes almost exactly what I observed happening with my system.

In my case, the "boot screen momentarily flash on the screen" looked like a white box outline with a fairly thick border on a dark background which was approximately 1/3 to 1/2 the size of the full screen, but there wasn't any other discernable detail, and it was very momentary. Did you get the same visual cue?

My conclusion from reading this discussion is that there is some bug/anomaly in the Anniversary Update package (obviously different than the one described in the referenced discussion) that was not present in the previous two Windows 10 updates (original and 1511), and that is causing this error.

 

Exactly the same, so much so that I thought you must have been going by something I described in my original post but I double checked and realised I hadn't. Basically between the two boots I mentioned there was a flashed screen with the outline of a window running in safe-mode-style low resolution, taking up about 1/2 the screen or more. It was on screen for a split second.

I remember reading something about it potentially being CPU related in my research but I wasn't willing to dick around with my CPU, so I ended up biting the bullet and doing a clean install, which was not ideal at all and has lead to problems of its own (lost one of my hard drives - showed up as unallocated in Disk Manager and had to buy 3rd party software to recover the data on it, naively didn't think to backup as I wasn't expecting an OS install to effect the hardware in that way, especially when it wasn't on the system drive). Ahh, the joys of Windows. Unbelievable.


Incidentally, my reason for wanting to update to AE was to run Forza Horizon 3, available exclusively from the Windows Store. A silly and inane reason to be sure, but hey. I bought it, without realising I had to update Windows when I did so, and then the store wouldn't let me download it as I did not have the latest OS. I haven't had to update an OS before to run a new game unless the OS in question has been about 8 years old, but then I haven't had to buy a game digitally through a digital storefront intrinsically linked to the OS before.