Windows 10 Anniversary Upgrade Fails with Error 0x800700c1

Topic

New Reply

I’m running Windows 10 Pro Version 10.0.10586 Build 10586, 64 bit on a Lenovo Thinkpad W541. My Thinkpad has a SSD (drive C:) with Windows and programs on it, but all users files located at drive D:Users[username]….

I made 5 attempts to update my system with the “Windows 10 Update Assistance” which reports the following:
45553-20160914-Windows-10-Update-Assistant-00

After grinding through the whole download/ installing updates process the following dialogue appears:
45554-22019014-Windows-10-Update-Assistant-Something-Wrong

Same result at every attempt.

This is an exceedingly unhelpful error code.

Extensive searches with Google has failed to find an explanation and/or fix for this error, and I’ve trieds a few that have been suggested. I thought of shifting Users back to C:Users and trying again, but 600GB of user data will not fit on the 256GB SSD with the system and program files:(

Any brilliant ides to resolve this issue.

Cheers

BygAuldByrd

Reply | Quote

Replies

I got that same error on my first upgrade to Win 10, because I was logged in as a Standard User, needed to be an Admin account. Are you in an Admin account?

Reply | Quote

I got that same error on my first upgrade to Win 10, because I was logged in as a Standard User, needed to be an Admin account. Are you in an Admin account?

Thanks for your suggestion but all attempts to upgrade where made using an Administrator account.

Also tried:

[*]Clean boot
[*]Stopping all programs that load at startup
[*]Stopping all non-Microsoft Services
[*]Disconnecting all external devices except ethernet, ie no USB sticks, USB HDD, USB Speaker

Still no joy.

BygAuldByrd

Reply | Quote

Have you tried using the Media Creation Tool?

--Joe

Reply | Quote

Have you tried using the Media Creation Tool?

Thanks for the thought.
I hadn’t, so I did the “Update” process using the Media Creation Tool from [HTML]https://www.microsoft.com/en-au/software-download/windows10[/HTML] with the following “highly illuminating” result:

45564-20160915-Windows-10-Media-Creation-Tool-result

And that was it – no indication whatever as to the nature of the cause of the failure:(

Still looking for a solution that doesn’t involve a clean instal.

Cheers

BygAuldByrd

Reply | Quote

…Still looking for a solution that doesn’t involve a clean instal…

Have a look at my post at KB3189866 stuck at 46% download

Reply | Quote

Does Event Viewer give you any details for that failure ?

Reply | Quote

Does Event Viewer give you any details for that failure ?

I have tried searching through the Event Viewer but haven’t noted anything that appears to be related to the Windows 10 Anniversary Update, but then a lot of the descriptions are not particlularly illuminating:(

Cheers

BygAuldByrd

Reply | Quote

The ones that could be relevant will have the date and time stamp of around the time of the failure.

Reply | Quote

I thought of shifting Users back to C:Users and trying again, but 600GB of user data will not fit on the 256GB SSD with the system and program files:(

Move the D:/Users’ ‘Special Folders’ to new folders on D: (one folder per User) and then move the remaining D:/Users folders and data back to their default folders on C:?

Also check that there’s enough (450Mb?) drive space free at the beginning of the disk that W10 can use for a new partition for the Boot/diag files.

Reply | Quote

Hi Sudo15,

I’ve just completed another attempt at Windows 10 Pro Anniversay Update, this time by:

[*]Downloading the Windows 10 Pro 64 bit ISO file from https://www.microsoft.com/en-au/software-download/windows10
[*]Creating a DVD Windows 10 Pro (64 bit) installation disk
[*]Running “Setup.exe” from the DVD

and after about 2 hours came up with the following “amazing” result:

45585-20160917-Windows-10-Pro-ISO-Setup-Fail-Result

I’ve attached copies of:

[*]The Event Viewer > Winodws Logs > System for the duration of the attempted Update.
[*]The WindowsUpdate.log (The relevant period for the Update attempt is 17 Sep 2016 from 10:50 to 13:00).

I can’t see anything in those Logs that point me to the cause of the Update failures.

Are there other more relevant Logs? If so, where do I find them?

Any further suggestions appreciated.

Cheers

BygAuldByrd

Reply | Quote

Hi Satrow,

Thanks for the suggestion, but before I charge off to try it, am I correct in assuming that by “D:/Users’ ‘Special Folders’ ” you mean:

[INDENT]D:/Users/[Username1]/…
D:/Users/[Username2]/…
[/INDENT]

and by the remaining “D:/Users folders” you mean:

[INDENT]D:/Users/All Users/… (which incidentally has a shortcut icon)
D:/Users/Default/…
D:/Users/Default User/… (which incidentally has a shortcut icon)
D:/Users/DefaultAppPool
D:/Users/Public/…
D:/Users/TEMP
D:/Users/[Username1]/…[/INDENT]

I note that on my system drive I already have:

[INDENT]C:/Users/All Users/… (which incidentally has a shortcut icon)
C:/Users/Default/…
C:/Users/Default User/… (which incidentally has a shortcut icon)
C:/Users/Public/…
C:/Users/[Username1 Administrator]/… (only laptop’s user as an Administrator)
C:/Users/[Username1]/… (only laptop’s user as a non-administrator)[/INDENT]

Should I simply overwrite these folders – which doesn’t seem like a good idea to me.

Just wish to be sure I’m understanding your suggestion before I screw up my system.

Cheers

BygAuldByrd

Reply | Quote

Wait for Satrow to confirm those and see if he will accept running this cmd from a Command Prompt (Admin) would do any good and if you would need to create a restore point before running it –

You can copy & paste it to the cmd prompt.

%SystemDrive%Program FilesUpdate ServicesToolsWsusUtil.exe reset

This cmd will reset the WSUS server.

Reply | Quote

Wait for Satrow to confirm those and see if he will accept running this cmd from a Command Prompt (Admin) would do any good and if you would need to create a restore point before running it –

You can copy & paste it to the cmd prompt.

%SystemDrive%Program FilesUpdate ServicesToolsWsusUtil.exe reset

This cmd will reset the WSUS server.

I tried running WsusUtil.exe (after setting a Restore point), however the path you have specified does not exist on my Windows 10 system:confused: And a search of my SSD and HDD did not find WsusUtil.exe:confused:

Cheers

BygAuldByrd

Reply | Quote

Use this as a guide to restoring the Special Folders to their default locations: Windows 7: User Folders – Restore Default Location

Check each folder size first, you may need to move some of the larger files/folders within those to a new location on the D: to prevent them from using up too much SSD space.

This might prevent the risk of freezing that was introduced with AU, though recent changes by MS seem to have reduced this risk anyway (I don’t think they’ve figured out all of the reasons for it yet).

If you have any other default Windows folders moved onto D:, you should also move them back, unfortunately, they won’t have the Location tab in their Properties, so no easy Restore Location (and I’ve never moved anything other than the “allowed” Special Folders, so I don’t have an easy fix for those). <- these might be the real reason for the failure, similarly if you have any apps/programs installed on the D:.

Before you try W10 AU install again, ensure you have all your hardware drivers fully updated and temporarily uninstall anything that runs software drivers/filters at boot, like AV, MBAM Prem., some motherboard/GPU monitoring utilities, etc.

Reply | Quote

Hi Satrow (and all other responders),

Thanks to all for the suggestions and guidance.

I haven’t resolved my problem with Windows 10 Pro AU Update as yet – been heavily engaged on other activities and not had time to devote to this.

I’m wondering, should I make an image of both my System drive (C:) and my data drive (D:), or is it only necessary to do C: – all my data is otherwise backed up.

I’d also note that only my “Users” folder has been move to D:. No other system folders have been moved.

I’m hoping to have time later this week to get back to this issue and will update how I get on.

Cheers

BygAuldByrd

Reply | Quote

I must admit that I wasn’t sure if that cmd was for Win 10 or for a server having done a Google search on ISusInternal:: DisconnectCall failed, hr=8024000C but as nothing else seems to be working, thought it was worth a try.

There’s very little info on that error, other than quite a few also getting that error with updates.

How are you getting on with Satrow’s suggestion ?

Reply | Quote

This may be coming too late, but I had three failures by Windows Update to go to 1607 and had likewise useless error code (0x8024200D, corrupted software download folders, I believe, which I cleared with the MS fix-it tool to no avail). Then forced an upgrade with a downloaded file (via Media Creation Tool) and got an error code which with a Google search got me to a Windows forum with a comment that the code indicated that I had TWO Windows installations on my computer. Like you, I have a new SSD with my Windows 10 OS on it, user files on the old 2 TB HD, but also on the old HD is the OLD Windows 10 installation which I migrated to the Samsung SSD a few weeks ago. Apparently that confuses the AU installer. Unhooked the old HD SATA cable and Win10 AU installed nicely, then reconnected the HD and all’s still well. For whatever it’s worth, that’s my experience. Oh, the last error codes were 0x80073B92 – 0x20009.

Reply | Quote

This may be coming too late, but I had three failures by Windows Update to go to 1607 and had likewise useless error code (0x8024200D, corrupted software download folders, I believe, which I cleared with the MS fix-it tool to no avail). Then forced an upgrade with a downloaded file (via Media Creation Tool) and got an error code which with a Google search got me to a Windows forum with a comment that the code indicated that I had TWO Windows installations on my computer. Like you, I have a new SSD with my Windows 10 OS on it, user files on the old 2 TB HD, but also on the old HD is the OLD Windows 10 installation which I migrated to the Samsung SSD a few weeks ago. Apparently that confuses the AU installer. Unhooked the old HD SATA cable and Win10 AU installed nicely, then reconnected the HD and all’s still well. For whatever it’s worth, that’s my experience. Oh, the last error codes were 0x80073B92 – 0x20009.

Reply | Quote

Maybe I missed this, but have you tried doing the installation with the computer not connected to the internet? I recall reading elsewhere that someone was having troubles with their installation until they did that. They posited that the installation was failing because of trying to get additional updates during the installation. Once they disconnected, the installation went right through.

After what you have been experiencing, I would seriously consider just doing a clean install of Win10AU and go from there. Personally, I had so many problems with updating from Win7 to Win10 that I scrapped everything and did a clean install of Win10 1511. Then, a week and a half after that, AU dropped onto the system. Since then, I have had no problems with my system.

I intend to do my next system doing a clean install of Win10AU (1607) over Win7 from the new ISO I just made using the creation tool.

Reply | Quote

Hi WildcatRay,

While I’d like to do a clean instal, and will undoubtedly have to do it sometime not too soon, that ends up being days of re-establishing my system with its multitude of installed applications.

I’ll try your suggestion of disconnecting the Internet and see if that resolves the issue, using the Windows 10 Pro AU ISO I’ve already created using the Media Creation Tool.

Cheers

BygAuldByrd

Reply | Quote

When you do the repair install with it, disable or uninstall your antivirus first.

Reply | Quote

Hi All,

I’ve just had another go at upgrading Windows 10 Pro v1511 to the Anniversay Update. Success at last:)

Here’s the latest synopsis:

[*]I have my Windows system on Drive C: (a 220GB SSD with 93GB used) and the user profiles at D:Users[Username]… (a 931GB HDD with 604GB used).

[*]Created Windows 10 Pro Anniversary Update using the Media Creation Tool.

[*]Created a System Image and Recovery Disk of drive C:. My drive D: data is already double backed-up.

[*]Following various advice, I attempted to move D:Users[Username]…, (except “Documents”, “Music” and “Videos” – they’re too big) back to the C: drive using the instructions to “Move Users (and possible ProgramData) back to C: drive” from [HTML]http://www.tenforums.com/tutorials/1964-users-folder-move-location-windows-10-a.html[/HTML], but that failed at my first attempt with an inability to run the “Sysprep” process.

[*]Later in the referenced instructions is comment to the effect that “Sysprep” will not run on an upgraded system, so I followed the instructions to modify the Registry Entry at HKEY_LOCAL_MACHINESYSTEMSetup to delete the KEY “Upgrade” and DWORD “Upgrade” and at HKEY_LOCAL_MACHINESYSTEMSetupStatusSysprepStatus and ensure that the DWORDs “CleanupState” and “GeneralizationState” both had a value of 7.

[*]I disconnected my Internet connection, disabled the WiFi and Ethernet adapters.

[*]I did a bit of housekeeping on drive C: by deleting the renaming the following folders (which I after everything else was tried and tested, I deleted them):
[INDENT]$GetCurrent
$SysReset
$WINDOWS.~BT
$Windows.~WS
Windows10Upgrade[/INDENT]

[*]Before trying again, I killed “Windows Defender” and “Malwarebytes Anti-Malware” and all other running applications.

[*]Attempted yet again to move D:Users[Username]… back to the C: drive and this time it worked, but as part of the process I had to create a New User and needed to enter my Windows 10 Pro Product Key. This time it worked without any issues.

[*]While still logged in as my “new user”, I then attempted the Windows 10 Pro Anniversay Update yet again :crossfingers:

[*]After a number of reboots I was able to logon with my usual Username and Password.

[*]So I typed “Winver” into the “Run” dialogue and found that I now had Windows 10 Pro version 1607 installed.

Wonders will never cease — it worked:fanfare: Hooray:clapping:

Oops:confused: What’s this, some of my setup has been changed and now I have to try and find my way around the changes that have been made in Windows 10 Pro Anniversary Update and set things up again the way I like them:(:

Cheers

BygAuldByrd:cheers:

Reply | Quote

Congrats, BygAuldByrd.

FYI: Win10AU is notorious for changing many a user personalization/customization back to their Windows defaults as well as “removing” programs like Classic Start which tweaks the Start menu to look/act like Win7’s Start menu. Might be a side effect of “Windows as a service” or whatever the new tagline is.

Reply | Quote