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: Newest
  1. Anonymous
    2018-05-15T11:07:01+00:00

    Were you running with Administrator privileges? I was running the PowerShell (Admin) but I was also logged on as a system administrator. Did you use the Services dialogue to see if the four services were still running?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-05-13T16:45:56+00:00

    Get 'Access denied' error

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-05-12T22:41:39+00:00

    I was having a similar problem with Win 10 v. 1709 trying repeatedly to install KB4103727 and failing. I followed the instructions I found on page 1 of this thread, namely, stop the services Background Intelligent Transfer Service (BITS), Cryptographic Services (CryptSvc), Windows Installer (msiserver), and Windows Update (wuauserv), renaming the directories C:\Windows\SoftwareDistribution and C:\Windows\System32\Catroot2 to <x>.old versions. Then restart the services that were previously stopped. Then restart the system and re-try the update.

    But I found a few wrinkles, which may just be because of the difference in the version when those instructions were originally written and now. I used PowerShell (Admin) to issue the "net stop" commands for the services, and it said the commands completed successfully. But I couldn't rename the directories. They were still in use. I used the Computer Management -> Services and Applications -> Services screens to find that some of the services had restarted themselves. I tried using the Services screen to right-click and Stop the services. This worked, except for CryptSvc. That one kept restarting immediately and wouldn't release Catroot2. So I opened its Properties dialogue and changed its status to Disabled. Then Stopped it. It DID NOT restart. I was then able to rename Catroot2. Switch CryptSvc's status back to Auto(Delayed), started it and the other three services, and restarted the computer.

    After the restart, I went into Settings -> Update & Security. Finally, I saw the "Check for Updates" button. I checked the "View installed update history" and found absolutely nothing listed (of course not, the history was in the directories that I renamed). I clicked on Check for Updates, and it began loading Feature Update 1803! That's success, because I didn't want to update 1709 anyway.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-05-11T23:28:12+00:00

    Update 1803 solved all problems with this issue.  Nothing else worked.  Thank you Microsoft.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments