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-26T11:12:48+00:00

    I couldn't agree more, Brian..............it's the Microsoft chasing of the mighty 'lucre'............it's the American way........don't ya' know?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-26T11:21:24+00:00

    Hi Tenisoy,

    hate to accuse you of naivity...........but many Microsoft users would debate your assertion that Microsoft are a 'reliable' company........the trouble is they've got somewhat of a monopoly and until another I.T. organisation comes along and seriously competes (sorry......Apple......you still don't cut - it). I seems evident to me that they truly don't give a damn about this clear

    failure to publish a 'fix' for this problem.........which must have millions of purchasers of Windows 10 in seething annoyance at Microsoft's  deliberate

    ignorance of a now serious glitch for us........who parted with our money.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-26T14:10:19+00:00

    @swansojb  Apparently my problem is/was a little different.  The Computer which was "hanging" on updates I was dealing with "hung" on a pair of updates.  The 1st one was the one released prior to the one that prompts this thread.  Both updates, no matter what process I went through, including all of your recommendations, was able to get a "completed install" on my system.  It is an "ancient" Acer Z3731-UR21P manufactured very shortly after Windows 7 (X64) was released.  It has an Intel dual-core Pentium E6700 and 4gb of RAM and an Intel Graphics chipset that uses an area in that RAM.

    I ended up "chatting" with Microsoft Support and got a tech to link to me to check things out.  He ended up trashing a huge volume of "Log" files that had accumulated on the 1TB disk I had spinning.  He also performed the same rituals I had already tried twice.  In his final swath through the machine after he convinced himself that Microsoft Update on this machine had something "weird" going on, he disabled the history of updates on the machine, so my Check for Updates screen no longer displays any entries.  The system spec screen shows 1709 with 1629.125 as the version.

    The available downloadable installers, at least in my case, did not "cure" the symptoms, but hopefully a subsequent release will bring back the update history and proceed onward. It was "current" as of about 1/24/2018.  The original install / reboot sequence was "working" by the updates apparently in my case "did not register" at the end of the reboot cycle in a way that the module that does the updating could see that the update was there!  I used a .DLL described in this thread from the console to pull a list of the installed updates and even though the display in "Settings" does not show them, THEY ARE ON THE SYSTEM

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-26T14:15:19+00:00

    Had the same problem with that AMD64 update on and Intel dual Pentium E6700.  I believe this system made by Acer back around 2010 has an AMD chip somewhere in the chipset on the motherboard, but it is not part of the main guts, it may be associated with the virtual USB based touch screen controller.  My machine is an early touch screen All-in-One.

    Was this answer helpful?

    0 comments