Jump to content

KB4132216 causes failed installation/uninstallation of CU


halohalo

Recommended Posts

The latest servicing stack update KB4132216 causes failed installation/uninstallation of CU on Windows 10 Home.

 

Installation of KB4284880 failed at 99%. Installation and uninstallation of KB4103720 also failed at 99%.

The latest Flash Player security update is compatible with KB4132216.

Link to comment
Share on other sites


I'm afraid you will have to uninstall KB4132216 (the hard way) and install previous SSU - KB4093137, halohalo.

However, on my Win10 v1607 Pro system, I have KB4093137 SSU installed and newer updates like KB4103720 & KB4103723 complete 100% successfully.

Use wushowhide.diagcab to hide KB4132216 and newer servicing stack updates.

Edited by erpdude8
Link to comment
Share on other sites

Official 1607 ISO file contains KB3199986 SSU, and it is compatible with KB4103720 and old Flash Player security update.

 

Anyway, I solved the problem by replacing the latest wcp.dll with old one. The installation of KB4284833 is successful.

 

Link to comment
Share on other sites

  • 2 weeks later...

be careful halohalo.

June 2018 updates KB4284880 & KB4284833 (and later CUs) include the windows10upgrade.exe file stored in the \Windows\UpdateAssistantV2\ folder and may run at anytime and unexpectedly upgrade your v1607 home system to newer release w/out any user intervention when KB4023814, KB4023057 & KB4056254 updates are installed.

do not be caught unaware of this "sneaky" trick by Microsoft

block/hide the KB4023814, KB4023057 and KB4056254 updates using wushowhide.diagcab or WUMT (Windows Update Minitool)

also delete the windows10upgrade.exe file or the entire UpdateAssistantV2 folder from the Windows folder after installing either KB4284880 or KB4284833 update

Edited by erpdude8
Link to comment
Share on other sites

Install KB4132216, then find the latest wcp.dll and change its ownership and permissions. Copy old wcp.dll to replace the latest one, then restore the ownership and permissions.

 

I am using Windows 10 x86, so there is only one wcp.dll (x86) in KB4132216.

Edited by halohalo
update information
Link to comment
Share on other sites

  • 4 weeks later...

I kinda hate having to change ownership & permission of files/folders back and forth so another alternative is to integrate/slipstream the KB4284880, KB4103720 or higher cumulative update onto installation media as discussed in this MDL forum thread.  Slipstreaming those updates and performing an "offline" install of Win10 home/pro x64 on my PC with the KB4132216 & higher CUs already integrated seems to work around the problem.

I may consider installing a "higher" edition of Win10 v1607 like education or LTSB, overwriting my Win10 v1607 pro OS.

Edited by erpdude8
Link to comment
Share on other sites

  • 6 months later...

a follow-up on this:

a slightly better solution (rather than just manually changing file permissions to replace that wcp.dll file) is mentioned on this Tenforums page:

https://www.tenforums.com/windows-updates-activation/123949-w10-1607-cumulative-updates-installs-successfully-only-until-2018-06-a-10.html#post1574275

Edited by erpdude8
Link to comment
Share on other sites

  • 3 months later...
On 5/14/2019 at 11:04 PM, halohalo said:

Since kb4494440, kb4498947 replaces kb4132216. 

The KB4494440 cumulative update has been superseded/replaced by KB4505052, which includes the gov.uk fix for v1607

like KB4494440, KB4505052 also requires the KB4498947 servicing stack update

anyways, I'm using LTSB 2016 on some of my older PCs

Edited by erpdude8
Link to comment
Share on other sites

I don't even install updates anymore, i just update my wim, re-create an iso and also copy it to my usb installation stick.

Can't remember the last time a hotfix actually reached 100% on 10 without the stupid failed configuring updates message....

i have several computers and they all do that if i try and install an update the normal way via the .msu so i don't bother anymore. (and that's on an unmodified installation) i.e. not tinkered with....

updates failing to install for me was pretty rare on xp, vista, 7 and 8. i started having failed updates more often starting with 10 th1.

 

 

Link to comment
Share on other sites

  • 3 weeks later...
On 5/27/2019 at 1:38 AM, RanCorX2 said:

I don't even install updates anymore, i just update my wim, re-create an iso and also copy it to my usb installation stick.

Can't remember the last time a hotfix actually reached 100% on 10 without the stupid failed configuring updates message....

i have several computers and they all do that if i try and install an update the normal way via the .msu so i don't bother anymore. (and that's on an unmodified installation) i.e. not tinkered with....

updates failing to install for me was pretty rare on xp, vista, 7 and 8. i started having failed updates more often starting with 10 th1.

 

 

new cumulative updates for 1607 from May 2019 onward fail to install 100% on non-LTSB editions of Windows 10 v1607 (Home, Professional, Education & Enterprise), RanCorX2.

v1607 Home/Pro went EOL (out of support) April 2018 and v1607 Education & Enterprise went EOL on April 2019

Microsoft secretly added some safeguards in these big cumulative updates like the newly released KB4503267 June 2019 security update, that will not complete on many v1607 editions except LTSB 2016 (and get blocked until newest servicing stack update is installed)

1st attempt of KB4503267 - failed to install; got "This update is not applicable to your computer" when running the msu file (running Win10 v1607 Education edition [NOT Pro]) - found out that this new cumulative update requires a newer Servicing Stack update KB4503537 which I did not install.

2nd attempt for KB4503267 - installation went through after installing KB4503537 before KB4503267, rebooted and when it got to 100%, it then said "We couldn't complete the updates.  Undoing changes" [GAH  :angry:]

I'm gonna clean install Win10 LTSB 2016 on top of my Win10 v1607 Education OS, overwriting it on that test computer so I can install the newest 1607 updates 100% without failure.

Edited by erpdude8
Link to comment
Share on other sites

Just like KB4494440, KB4503267 also requires the same SSU. Apparently Education edition is blocked by wcp.dll.

 

However, if you check update.mum in CU, you will find that Education edition is not completely blocked.

Link to comment
Share on other sites

On 6/23/2018 at 5:24 PM, halohalo said:

Official 1607 ISO file contains KB3199986 SSU, and it is compatible with KB4103720 and old Flash Player security update.

 

Anyway, I solved the problem by replacing the latest wcp.dll with old one. The installation of KB4284833 is successful.

 

 

actually halohalo, the education & enterprise editions of win10 v1607 are not completely blocked by newer wcp.dll files from KB4498947 & KB4503537.

however installation of KB4494440 & higher CUs will not work with very old wcp.dll files like build 14393.0 - installation will say "the following updates were not installed" and installation will end prematurely w/out updating any files (yup, these new CUs require newer wcp.dll files - at least the ones from 2018).  but if I replace the wcp.dll files in the newer servicing stack folders with build 14393.2182 from KB4093137, the recent CUs like KB4494440 and the one from June 2019 like KB4503267 will proceed & install without failure - I did this on another test machine but running win10 v1607 enterprise edition, not the education edition like on my other pc

v14393.2182 of the wcp.dll file is the last one without the "supported edition checking" functions

screen shot of win10 v1607 enterprise (non-ltsb) build 14393.3025 (KB4503267)

 

winver-win10enterprise-v1607-kb4503267.png

Edited by erpdude8
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...