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

226 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-02-21T12:20:02+00:00

    After three months of attempts, I decided to do what I wanted to avoid, an in-place upgrade, which efficiently repaired my version of Windows 10.  It is a very good technique, I was reluctant doing it as it is a new computer.

    W10 went back to normal operation.

    I am happy the post I opened helped many people without clean installs or other drastic solutions.  

    I thank all the people who contributed with solutions.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-21T12:06:34+00:00

    This solution solve the issue for me thank!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-20T02:17:41+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.

    For those who have trouble typing or getting syntax errors: If you just copy and paste all 4 lines starting with "SC" into the Command Prompt (with Administrative authority) the first three lines will execute. Check that all ended in Success. Then just press the enter key to execute the final SC instruction and if its successful too. Then two restarts should do it for you.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-19T20:43:47+00:00

    I'm guessing there is no space after "start=" and "auto" but I have not tried it.

    I was able to use the system management console to check and modify the parameters others have suggested, and my "problem system" is now functioning properly with all pending Windows 10 updates installed.  There are some anomalies in the pages under 'update" in the Windows 10 UI  Windows Settings, Update & Security,  list of installed updates, but they do not appear under the dialog which allows you to select and uninstall updates where everything is listed correctly with install dates that make sense to me.

    My problems began with a problematic update dealing with Adobe Acrobat Reader in November of 2017.  Apparently I may have had an instance of Adobe Reader DC installed that was not correctly recognized as my default reader, or the fact that I had set it as my default caused an "issue" with Microsoft's efforts to insure that some threat identified in the "standard reader" that they have tried to "take over" from Adobe in recent browser wars between Edge, Chrome, and Firefox.  I'm still somewhat vague about what that update was trying to accomplish.  It was superseded in February 2018 with more Adobe related changes.

    Was this answer helpful?

    0 comments No comments