|
There are isolated problems with current patches, but they are well-known and documented on this site. |
.Updates may fail to install and you may receive Error 0x80073701 Installation of updates may fail and you may receive the error message, “Updates Fail
[See the full post at: Patch Lady – 1903 Error 0x80073701]
Susan Bradley Patch Lady/Prudent patcher
This is caused by the multiple releases of July D-Week update KB4505903 in Release Preview Ring
the first version of this update “18362.263” contained some updated components (particulary swenum.inf and ufxchipidea.inf)
but then in later versions they removed these two components
August update KB4512508 also don not contain those components
the issue occur if the user ran Update Cleanup (via disk cleanup or manually with DISM tool) after installing the 18362.263 version of KB4505903, which removes and replace the inbox RTM version of the components with updated ones
later when he try to install other versions or August update, they fail because neither the system have the RTM components, or the new updates have the updated components
the issue seems to occur in x64 only
there is an easy fix for this, but it’s for a little more experienced users
as for Microsoft, the fix is also really easy, just release new cumulative update that contain updated version of the missing components
they don’t even have to update the actual binaries
By the way, the root cause of this issue is the new servicing type of 1903 cumulative updates
if you don’t know, 1903 CUs are service pack alike, they directly update inbox CBS packages with new versions, depending on the updated components
this means, whenever Update Cleanup is executed (whether through disk cleanup, DISM tool or the scheduled Task “StartComponentCleanup”), the inbox CBS packages that have newer versions will be removed completely, and the active cumulative update will become the new base
all updates actually become permanent, including the .NET or Adobe Flash
—
another by the way, the ResetBase feature (introduced with Windows 8.1) was disabled in Windows 10 since first version 1507, which prevent removing the superseded RTM components
but now with the new CU type in 1903, it bypass this fail-safe restriction
FYI, 1903 was shipped with a bug caused by this CU type, which occur when integrating new CU into updated WinPE images
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-1903-dear-microsoft-please-remember-to/e9e9e28a-c3f6-4e24-a900-f48a85b20431?tm=1558465537818
but they fixed that with SSU KB4498523
I am impacted although error codes I got differ – see the below blurp from this post onwards:
Care to share what’s this possible tweak to get this resolved?
And yes, I do clean component store regularly, so this explanation is quite feasible.
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
