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: Oldest
  1. Anonymous
    2018-04-14T03:09:08+00:00

    Basically, those commands, manually restart the services for the updates, helping them to install.

    There are microsoft fixit tools you can run which do the same thing :)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-04-14T10:50:56+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.

    I spent the last week trying to restart my PC with this update (14 failed attempts!): 

    April 10, 2018—KB4093112 (OS Build 16299.371)

    Windows key + X and then press the shortcut key <A> is alternative to first rule. Checked build number* correct build!  Thank you #DevonBasson! 

    * To find out which version of Windows your PC is running, press Windows logo key  + R, type winver, then select OK.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-04-16T18:13:15+00:00

    I had two "Requires a restart to finish installing" issues (Adobe Flash Player security updates KB4088785 and KB4093110) and also some loop issues (cumulative updates). This fix works for me and it seems to be fine. But i needed a lot of restarts.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-04-16T20:12:53+00:00

    I had two "Requires a restart to finish installing" issues (Adobe Flash Player security updates KB4088785 and KB4093110) and also some loop issues (cumulative updates). This fix works for me and it seems to be fine. But i needed a lot of restarts.

      I too have been through some "sieges" with this error.  They seem to tend to occur on older computers driven by impatient users who have not checked their automatic update settings and who finish what they are doing and shut down quickly.  The Adobe update back in November of 2017, the first one of a series of several, was the worst offender.  Just today, I updated a newer portable that had not been online in a week or two, and got the error followed by installation of a Windows 10 cumulative update that apparently "cleared up" the problem without anything more than a simple restart.

    Was this answer helpful?

    0 comments No comments