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-02-07T14:37:53+00:00

    "....this fixed my problem and allowed my updates to go through. Perhaps Microsoft should 'e' mail all users of Windows 10 about this successful guide to fixing the problem."

    Yes, I agree. Microsoft should Post it's Fixes to the Upgrade problems. Put your reputation online, Microsoft. Stop hiding behind surrogates.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-07T11:09:02+00:00

    Hello Steve,

    Brilliant.........Well done........this fixed my problem and allowed my updates to go through. Perhaps Microsoft should 'e' mail all users of Windows 10 about this successful guide to fixing the problem. Thanks mate........I am truly grateful for this great 'fix'.

    John Evans

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-06T16:00:03+00:00

    Thanks, SteveMat, but this is Microsoft's work. I'm not a computer tech nor am I on the Microsoft payroll. I and many others are involuntary Beta Testers. In accepting a Free Windows 10, we agreed to be monitored by Microsoft. MS has forgotten an axiom of business: "A satisfied customer may tell 1, 2 or 3 others. A dissatisfied customer tells 9.".

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-06T13:46:42+00:00

    For folks having problems using the Command Prompt to set service to Automatic, you can use the GUI.

    1. Right-Click on the Start Button (or tap and hold) and choose "Computer Management"
    2. Hit the + next to "Services and Applications"
    3. Select "Services"
    4. Find each of the below Services and make note of their existing values if you want to put them back

          Windows Update

          Background Intelligent Transfer Service

          Windows Modules Installer

         Cryptographic Services (this was already Automatic on my Surface)

    1. One at a time, double-click on each of the above Services and change the "Startup type" to Automatic
    2. Reboot
    3. Run Settings / Windows Update / Check for updates

    I had already done a lot of the other troubleshooting steps (deleted SoftwareDistribution folder, rand SFC and DISM commands, Manually run the .MSU).  Was not until I set the above services to Automatic did the latest CU install.

    1. Following steps 1-4, you can set Services back to their default values.  You can probably leave these @ Automatic.  WU is supposed to start these up when needed but that is not happening for whatever reason.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments