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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-08T15:55:01+00:00

    The more basic problem is that the error codes and their meanings are not documented.  Also I ran a trouble shooter which said the Windows Update had a problem and did not give enough information to get to the next step.  Coupled with the criminally negligent policy of forced restarts regardless of whether anything is open or active leads me to believe that a major shakeup in Windows management is needed.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-08T16:28:48+00:00

    Clark,

    I don't see this as, "criminal negligence". I'm in Week 6 of the MS Windows 10 Upgrade to the Fall Creators Edition. I have chatted with 5 different MS Support Techs. The last one did a "Clean Install". I lost one of two Mozilla Thunderbird email address', the three associated Address books, three years of Archived emails, and, all the many dozens of saved Favorites in my MS Edge and Mozilla Firefox browsers. Now the recently installed Win 10 Upgrade is stuck: it can't upgrade itself. So MS Support advises I remove and reinstall the Windows 10 Fall Creators Update.

    That's nor criminal but it's damn poor product management and customer relations. This Upgrade wasn't market ready.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-10T03:36:27+00:00

    another big THANK YOU for this fix!!!

    only issue may be if those services should not be on auto, but on manual or on demand for future updates... i noticed my system acted weird when i rebooted after turning those to auto, system rebooted then i couldn't get windows update to start then BAM it went to the update screen and went to 28% then rebooted.. everything seems ok now on 2nd reboot, but i wonder if putting those on auto may make all future updates instantly install/restart the system without warning..

    only service i saw that was set 'differently' for my wifes PC (which installed the update fine) was the wuauserv(windows update service) was set to Auto Triggered on my system, and manual triggered on wifes. I went on and changed it on my system back to manual triggered..

    rest were all the same

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-01-12T11:25:35+00:00

    I am the person who started this post. 

    I am happy someone solved the problem with the fixes suggested recently.

    I did not, even if I tried all solutions suggested here and elsewhere..

    Now my error has evolved into the following, as I guess the new cumulative critical update replaced the old.

    Error messages are variable but it is a few days it is 0x8000ffff

    2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892) - Error 0x8000ffff

    2018-01 Security Update for Adobe Flash Player for Windows 10 Version 1709 for x64-based Systems (KB4056887) - Error 0x8000ffff

    If anyone can help or has other ideas, please write.

    I am thinking to do an in place upgrade with the same version using the media creation tool but am a bit reluctant.  For the moment I updated everything else and using a VPN to minimise Meltdown risk.

    One more thing.  Cannot complete sfc / scannow as it says a repair is pending after restart (this is a loop).

    Tries the DISM command (DISM /Online /Cleanup-Image /RestoreHealth) even with an outside image of 1709 created with media creation tool but did not solve, stops at 87%.  Maybe someone can read into that.

    Was this answer helpful?

    0 comments