Upgrading from Win10 1909 and 20H1 to 20H2

355 views
Skip to first unread message

Kurt Buff

unread,
Jun 18, 2021, 7:09:51 PM6/18/21
to ntsys...@googlegroups.com, patchma...@googlegroups.com
All,

I've got about 200 out of about 750 machines that showing failure to
upgrade to 20H2. Most are 1909 ad failing on KB3012973, but a few are
20H1 and failing on 4562830 (enablement). We're using WSUS for MSFT
patching.

I thought I saw discussion on this, but can't find it.

I harvested logs from one machine after struggling with it for a few
hours using PSWindowsUpdate. It was showing the 2021-05 cumulative
update for 1909 and the upgrade to 20H2. I finally got it to accept
just the 1909 cumulative update and it rebooted and was happy.

Then I tried again with the upgrade, and it failed, as shown in the
log snippet below. Per this page the error is that the update needed
to be downloaded again:

https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-error-reference

0x8024200D WU_E_UH_NEEDANOTHERDOWNLOAD The update handler did not
install the update because it needs to be downloaded again.

That seems weird to me, so anyone with an explanation will earn my thanks.

I'll have the machine available again next week to try again, but I'd
love to figure this one out.

Kurt

2021/06/18 16:21:29.1278643 8920 4900 DownloadManager Preparing
update for install, updateId =
2953778C-4998-4B0A-A507-961D1DA7E327.201.
2021/06/18 16:21:29.1284214 5712 1912 Handler * START *
Windows Setup Install
2021/06/18 16:21:29.1284261 5712 1912 Handler Updates to install = 1
2021/06/18 16:21:29.1326690 5712 1912 Handler Loaded state.
m_dwState now: Setup360_CompatToolPhase1(5)
2021/06/18 16:21:29.2402490 5712 1912 Handler Starting
Windows Setup with command line =
C:\WINDOWS\SoftwareDistribution\Download\3ba5dbf844de5ea1b30752de5e4c0b02\WindowsUpdateBox.exe"
/ClassId 1b100dca-d859-4c1f-af71-d9c2dd343ab0 /ReportId
{2953778C-4998-4B0A-A507-961D1DA7E327}.201 /PreDownload /Update
/ClientId ad7a5af5-f092-49cb-8fb2-93da18d214fc /CorrelationVector
iTV7kKSlvUWfIFz0.3.0.0.3"
2021/06/18 16:21:29.2402534 5712 1912 Handler Registering
WinSetup COM server as CLSID {1B100DCA-D859-4C1F-AF71-D9C2DD343AB0}
and APPID {DC721921-F0F8-4798-B1F3-26D808957CC3}
2021/06/18 16:21:29.2426207 5712 1912 Handler Successfully
registered WinSetup COM server as CLSID
{1B100DCA-D859-4C1F-AF71-D9C2DD343AB0}
2021/06/18 16:26:24.7275295 8920 6004 IdleTimer Activation
callback for PDC handle 000001BBA777A0C0 received (Reason: 100).
Renewing activation...
2021/06/18 16:27:29.4111138 5712 1912 Handler Installer
completed. Process return code = 0x00000000, result = 0x00000000,
callback pending = True
2021/06/18 16:27:29.4112592 5712 1912 Handler State changed.
was: Setup360_CompatToolPhase1(5), now:
Setup360_Phase2DownloadRequest(7)
2021/06/18 16:27:29.4120079 5712 1912 Handler Saved state.
m_dwState: Setup360_Phase2DownloadRequest(7)
2021/06/18 16:27:29.4124787 5712 1912 Handler *FAILED*
[8024200D] Method failed [CUHWinSetupHandler::Install:763]
2021/06/18 16:27:29.4124807 5712 1912 Handler * END *
Windows Setup Install
2021/06/18 16:27:29.4133244 8920 4900 DownloadManager Install failed
because the update 2953778C-4998-4B0A-A507-961D1DA7E327.201 was not
complete; mark update as not downloaded.
2021/06/18 16:27:29.4137144 8920 4900 Agent *FAILED*
[8024200D] Method failed [CAgentUpdateManager::InstallUpdate:11561]
2021/06/18 16:27:29.4164718 8920 4900 Handler Loaded state.
m_dwState now: Setup360_Phase2DownloadRequest(7)
2021/06/18 16:27:29.4199002 8920 4900 Agent Install
updates CallerId = <<PROCESS>>: powershell.exe
2021/06/18 16:27:29.4199966 9704 5944 ComApi Install
ClientId = (null)
2021/06/18 16:27:29.4200015 9704 5944 ComApi Install call
complete (succeeded = 0, succeeded with errors = 0, failed = 1,
cancelled = 0, unaccounted = 0
2021/06/18 16:27:29.4201113 9704 5944 ComApi Reboot required = False
2021/06/18 16:27:29.4201211 9704 5944 ComApi Exit code =
0x00000000; Call error code = 0x80240022
2021/06/18 16:27:29.4201230 9704 5944 ComApi * END *
Install ClientId = (null)
2021/06/18 16:27:29.4201582 8920 5920 Agent WU client
calls back to install call {C4253BDB-C6B1-4198-9647-909F2DC88589} with
code Call complete and error 0
2021/06/18 16:27:29.4204569 9704 11028 ComApi Install call
complete (succeeded = 0, succeeded with errors = 0, failed = 1,
cancelled = 0, unaccounted = 0
2021/06/18 16:27:29.4204655 9704 11028 ComApi * END * All
federated installs have completed. ClientId = (null) (cV =
iTV7kKSlvUWfIFz0.3.1)

Michael B. Smith

unread,
Jun 18, 2021, 7:17:01 PM6/18/21
to ntsys...@googlegroups.com, patchma...@googlegroups.com
Susan B is the expert at these, but what I generally do is one of two things:

[1] tell Intune to take care of it (and it does a great job of it), or

[2] download the enablement patch to a file share, then d/l it locally and install it using either cmd.exe or PS.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CADy1Ce7y18HJ_1Tb_pwHoM4dXRcGYaSej-cSGExzb8XtaiNvRw%40mail.gmail.com.

Kurt Buff

unread,
Jun 18, 2021, 8:29:23 PM6/18/21
to ntsys...@googlegroups.com
No InTune licensing or infrastructure.

Wil have to try the latter, though that is a small minority of the
machines in question..

Thanks,
Kurt
> To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/baf1123327754e0e90929714d7851c15%40smithcons.com.

don.l....@gmail.com

unread,
Jun 18, 2021, 9:01:06 PM6/18/21
to ntsys...@googlegroups.com, patchma...@googlegroups.com

It seems that the update consists of several parts and not all parts were able to be downloaded?

 

DownloadManager Install failed because the update 2953778C-4998-4B0A-A507-961D1DA7E327.201 was not

complete; mark update as not downloaded.

 

Maybe this is due to a dependency, or a DynamicUpdate piece?

 

DonP

 

From: Kurt Buff
Sent: Saturday, 19 June 2021 9:09 AM
To: ntsys...@googlegroups.com; patchma...@googlegroups.com
Subject: [ntsysadmin] Upgrading from Win10 1909 and 20H1 to 20H2

 

All,

--

Micheal Espinola

unread,
Jun 19, 2021, 1:35:48 AM6/19/21
to ntsys...@googlegroups.com
This isn't going to help, but I've encountered this same thing- but thankfully only on a handful of systems. I couldn't figure it out (always resulted in that same error) and had to resort to using a Media Creation Tool-based upgrade.

I hope and look forward to you figuring this one out 

--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CADy1Ce7y18HJ_1Tb_pwHoM4dXRcGYaSej-cSGExzb8XtaiNvRw%40mail.gmail.com.


--
Espi

Dee Arnold

unread,
Jun 19, 2021, 1:49:34 PM6/19/21
to ntsys...@googlegroups.com
I had this problem, with an 0xc190012e error. I had to go to C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS and rename setupconfig.ini to .OLD, then run updates again.

On Sat, Jun 19, 2021 at 12:47 PM Dee Arnold <De...@tsta.org> wrote:
##################################################################################### Only the individual sender is responsible for the content of the message, and the message does not necessarily reflect the position or policy of the Texas State Teachers Association or its affiliates.

Kurt Buff

unread,
Jun 19, 2021, 2:01:06 PM6/19/21
to ntsys...@googlegroups.com
That's certainly worth a try. Thanks for the tip, and I'll let the
hist know if it works.

Kurt
> To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CADsSk9%2B_PpzEbRkO925qVo5qJb2AbaoyfE676ay%3DG0gBpw4eEg%40mail.gmail.com.

Kurt Buff

unread,
Jun 23, 2021, 2:53:57 PM6/23/21
to ntsys...@googlegroups.com
That file - even that directory - isn't present.

Will keep looking.

Kurt

On Sat, Jun 19, 2021 at 11:49 AM Dee Arnold <dee....@gmail.com> wrote:
>
> To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CADsSk9%2B_PpzEbRkO925qVo5qJb2AbaoyfE676ay%3DG0gBpw4eEg%40mail.gmail.com.

Kurt Buff

unread,
Jun 23, 2021, 4:31:14 PM6/23/21
to ntsys...@googlegroups.com
Unknown to me. I'm trying several things, including something I saw
somewhere regarding exporting the SystemCertificates reg tree from a
known-god machine and importing it onto the non-updating machines.
That approach seems less than optimal, as it seems as if the certs
that each machine gets from our internal CA is stored there, and the
cryptic reference I found didn't specify further which portion of the
tree to export.

That reg tree start at HKLM/SOFTWARE/Microsoft/SystemCertificates.

Kurt
> To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/68BC2FB9-6375-4C64-8A75-93F1A883A682%40hxcore.ol.

Markus Klocker

unread,
Jun 24, 2021, 1:10:41 AM6/24/21
to ntsys...@googlegroups.com
Did you try to run setupdiag.exe on a failing client?
Maybe there is a hint.
Most of the time in my cases it is an outdated AV which blocks the upgrade.
Some have a driver related block which can be solved by updating.
I also have machines which suddenly upgrade after cleaning out all of
the old CU and .NET crap:
Warning this takes a long time!!!
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
This cmd gets rid of all superseded packages on the machine.
You can take a look at that first by running "Dism /Online /Get-Packages
/Format:Table".
Sometimes it helps to delete "C:\Windows\SoftwareDistribution\Download".

All in all there is no fitting simple cure but maybe you find something
helping here.

    Markus
Reply all
Reply to author
Forward
0 new messages