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
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

207 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Monkey57 3,535 Reputation points
    2018-01-12T16:06:26+00:00

    Please see:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/after-installation-of-kb4056892-boot-failure-after/6c015632-2a45-4725-a882-f231f8c88f36?auth=1

    On an Auto restoring AMD processored device:

    Even though KB4056892 is showing hidden by the Hide/Show troubleshooter ... I went ahead & used DISM to remove the Staged Package from this 1709 x64 system.

    from an elevated command prompt ran:

    dism /get-packages /Online

    pertinent results at the end:

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6

    State : Installed

    Release Type : Security Update

    Install Time : 1/12/2018 12:01 PM 

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    State : Staged

    Release Type : Security Update

    Install Time : 1/12/2018 3:12 AM

    16299.192.1.9 I am afraid of so I removed it.

    back in the elevated command prompt i ran (copy all the bolded text as one line, command may be wrapped when displayed on MC;  if your results from the previous DISM command are the same):

    dism /Online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    pertinent results at the end:

    Processing 1 of 1 - Removing package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    [==========================100.0%==========================]

    The operation completed successfully.

    Windows Update Completed successfully, downloaded some defender updates, and left no pending updates.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-13T17:30:20+00:00

    Dear Argel,

    Thanks for the response but I have not yet tried your suggestion described in the Article.  Do you have a list of the 7+ steps that this procedure specifies?  Frankly, I'm afraid to blindly follow a procedure with unknown steps.  My fear is I'll be trapped in a complete re-install with no exit.

    Again, thanks for your response.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-13T17:43:45+00:00

    See page 2: the steps are listed by Wojciech Bossak (dated January 11, 2018): from the cmd line, 4 sc... steps, plus reboot. They are similar to but not exactly the same as a Windows Update reset sequence that I'd seen earlier. 

    These steps worked for me, after a month of trying seemingly everything else.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-13T17:53:22+00:00

    Thank you!

    These steps solved the problem.  For the first time in over a month I could see evidence of Windows Update working, taking more than many hours over various phases of activity and progress. The initial part of that time was a blank screen - several hours. I left it alone figuring there were many problems to correct and hooks to set straight, Finally I was rewarded with status information/progress reports from most of that time, with several reboots initiated automatically.

    Brilliant!

    Much appreciation from TacoMonster.

    Was this answer helpful?

    0 comments