Error 0x80070bc2 when Windows 10 update trying to install KB4048955 for version 1709

Anonymous
2017-11-21T15:00:06+00:00

Windows 10 home, new computer with CPU Intel 8700K working well, version 1709 installed.   

I noticed that windows update gives error 0x80070bc2 when trying to install 2017-11 Cumulative update for Windows Version 1709 for amd64-based systems KB4048955 (and before KB4043961) ... getting a sort of a loop as it requires a restart to finish installing but at any restart gives the same message and does not install.  

Tried various things such as sfc scan, dism, troubleshooting windows update, manual install etc.  Nothing works.  Other updates such as KB4048951 and KB4051613 installed correctly in the last few days.  Can someone help?

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-27T06:57:08+00:00

This seems to have worked for me:

  • Right-click on Windows key and select Command Prompt (Admin).
  • Type the following commands in Command Prompt window. To execute them, press Enter after each one. 

SC config wuauserv start= auto

SC config bits start= auto

SC config cryptsvc start= auto

SC config trustedinstaller start= auto

  • Finally, restart your PC and try to install the update that was previously returning the 0x80070bc2 error.

Was this answer helpful?

900+ people found this answer helpful.
0 comments

226 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-04-29T01:34:51+00:00

    After going through all of the recommended solutions i was left with no other option except an in-place upgrade of windows to resolve this.

    i believe that the trigger of the issue was caused by my setting the anti-virus heuristics on my chosen anti-virus product (Webroot) to maximum, a setting they recommend for systems that you suspect have an as-yet unknown attack taking place.  This causes additional tracking and protection of system dlls.  In my case i set multiple machines to max because i believed it to be a good idea...

    Machines which i have not altered the settings on have continued to complete all of their upgrades without issue.

    I reduced the heuristic settings on the AV to normal and did the in-place upgrade and everything is running smooth again.

    Webroot does offer screen tips as to when to use each heuristic setting, I chose not to read the screen tips and just set everything to max.... because I could,  i shot myself in the foot with this one.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-04-27T01:55:28+00:00

    Hello 

    The Commands When i Enter in Command Prompt , It Shows ACCESS DENIED .

    Is There Any Other Way Around ??

    Thanking You

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-04-25T07:22:16+00:00

    This seems to have worked for me:

    • Right-click on Windows key and select Command Prompt (Admin).
    • Type the following commands in Command Prompt window. To execute them, press Enter after each one. 

    SC config wuauserv start= auto

    SC config bits start= auto

    SC config cryptsvc start= auto

    SC config trustedinstaller start= auto

    • Finally, restart your PC and try to install the update that was previously returning the 0x80070bc2 error.

    Thanks for the tip, this worked for me, it took 2 to 3 MS stating it is updating my laptop and then a couple of days later all is good.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-04-23T14:24:25+00:00

     update history still says that the update has failed. 

    With the same code?  If so, you will need to dig into the diagnostics to find what is really failing.  As I indicated if it is during an "apply" phase our tools are unclear.  Maybe you would get something in the Windows Error Reporting section of the msinfo32 tool.  E.g. I don't think it would be in either ReportingEvents.log or even WindowsUpdate.log but it might be in a piece of CBS log (probably not the most current piece).  Otherwise it would probably be in some (unclear) Events log.  What I have suggested people can try in this case is simply find out what has changed and list the files in that order.  Then depending on when that was (especially in the case of a CBS log) you will have to be wary about whether you are looking at clues from failures that happened during a rollback.  E.g. unless you can simply stop a rollback (perhaps with a boot menu) and look at the diagnostics then you need to be aware that common files won't be related to just the issue that caused it.

    FYI

    Robert Aldwinckle

    Was this answer helpful?

    0 comments