KB4132216 causes failed installation/uninstallation of CU

[halohalo]

I think the wcp.dll you found in 14393.0 folder is a delta backup. It is not a complete file, so you can't find detailed information. 

[erpdude8]

anyways, I've also used the 14393.2182 of the wcp.dll file and put it into the servicing stack 3022 winsxs folder on another machine (an old Dell e1405 laptop running 32bit win10 v1607 home) and I was able to update that to build 14393.3025 (KB4503267)

-also had to make sure that the windows10upgrade.exe file (from the C:\windows\updateassistantv2\ folder was either renamed to deleted to prevent unwanted forced upgrades to newer win10 versions

 

Edited June 22, 2019 by erpdude8

[erpdude8]

I recently saw this from abbodi in another forum:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Win101607EOS]
"{053DEC44-5C18-418D-BC3A-7D0C1F6838E3}"="{368E1623-5A77-4893-8201-48096DEE4970}"
"{B78F56A2-868B-44B2-A373-DF57A232D4BE}"="{16D54C04-4D80-496D-B3FA-937F0AAAEB37}"

 

adding this reg key & their values may allow installation of new updates on any 1607 edition with KB4132216 & newer servicing stack updates (as if it were operating on intel clover trail cpus)
no need to use modded or older wcp.dll files anymore

edit 8/31 - aww crap (it was too good to be true), this reg hack doesn't work as recent cumulative updates like KB4565511 & KB4571694 still fail to install with "we couldn't complete the updates.  undoing changes" message when attempting to install them on non-LTSB 1607 editions like Home/Pro/Education/Enterprise.
the recent CUs only install successfully with LTSB 2016
 

Edited August 31, 2020 by erpdude8

[halohalo]

Latest CU KB5023697 removes support for Home edition, so it's time to upgrade to a newer version of Windows.

[halohalo]

I don't understand why 21H2 ISO file offers incomplete Japanese IME. Anyway, the Japanese IME in 1607 ISO is compatible with version 21H2.

 

Unlike version 1607, I can't stop BITS and WU from re-enabling by using Microsoft Management Console.

Edited March 24, 2023 by halohalo