Getting error 0x80070BC2 doing Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892)

Anonymous
2018-01-07T00:42:04+00:00

This update has failed 21 times+. I have run trouble shooter and it is green.

Everything looks good until after the reboot. Stuck in a bad loop.

Event log:

Installation Failure: Windows failed to install the following update with error 0x80070BC2: 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892).

Any help would be appreciated.

Moved from: Windows / Windows 10 / Install & upgrade

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2018-01-11T09:31:02+00:00

PLEASE FIX THIS.  This update has failed over 20 times.

Surely at least one Microsoft employee is smart enough to fix this problem.  A simple call to any of the people suffering from the problem would allow this one employee to see what's wrong.

EXTREMELY UNHAPPY.

Hi

open CMD as administrator, an type one by one:

SC config wuauserv start= auto [Press Enter]

SC config bits start= auto [Press Enter]

SC config cryptsvc start= auto [Press Enter]

SC config trustedinstaller start= auto [Press Enter]

reboot system

Hope this helps!

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments

207 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-02-26T15:14:14+00:00

    PLEASE FIX THIS.  This update has failed over 20 times.

    Surely at least one Microsoft employee is smart enough to fix this problem.  A simple call to any of the people suffering from the problem would allow this one employee to see what's wrong.

    EXTREMELY UNHAPPY.

    Hi

    open CMD as administrator, an type one by one:

    SC config wuauserv start= auto [Press Enter]

    SC config bits start= auto [Press Enter]

    SC config cryptsvc start= auto [Press Enter]

    SC config trustedinstaller start= auto [Press Enter]

    reboot system

    Hope this helps!

    This is the fix!  Anyone having this annoying issue just do as the quoted instructions post and no more problem.

    Thanks for the info!  Fixed same issue on two different clients by only setting the Windows Modules Installer service (trustedinstaller) to automatic and restarting immediately. No need to change the default startup behavior of the other listed services.

    Could this issue be related to this?

    The TrustedInstaller service changes the default service startup type of Manual (3) to Automatic (2), when it encounters an update that has to process a transaction after a restart.   When the value is set back to Manual before the restart the transaction that has to be applied after restart cannot be applied.  This transaction will be pended. It will block all other update installations that might come up.

    https://support.microsoft.com/en-us/help/968440/when-set-to-manual-trustedinstaller-service-fails-to-install-updates

    And that is really old.. from Vista!  

    Don't see how is MS going to fix this without manual intervention from the user, cause this issue blocks all the newer update installations, if that's the related issue.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-19T13:24:35+00:00

    DON'T DO THIS! I got stuck on a perpetual loop and had to force a shutdown to get out of it.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-17T10:54:26+00:00

    According to my computer my licence is licensed to “Windows User”

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-17T06:23:39+00:00

    MAJOR FIX:  When installing this update be sure you are logged in with the user account that owns your W10 license.  Use winver to check to see which user owns the license.  

    NOTE: If you had to manually install the original upgrade to windows 10 you are likely to be affected if you are having this current upgrade issue.

    Was this answer helpful?

    0 comments No comments