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-06T02:13:22+00:00

    Thanks, Zundap Man. I'm taking a break from MS Updates until Feb 16. Actually it will be a bit longer. I'll be away from my computer until Feb 19. I'm not impressed by the MS Update process. My computer was commandeered by MS for the "installation" of the Fall Creators Update. That was on November 17, 2017. My PC was running fine. I was happy. I slept well at night. That has all changed. My PC is broken by dozens of failed updates and all I look forward to..., is more updates. Those tactics would be rejected by customers in any other business. Here's the latest. The MS Support Tech who performed the "Clean Install" that deleted my personal property gave me Office 2018 Professional Plus. I had been using Office 2003. I liked Office 2016, especially Outlook 2016. I bought software to transfer my remaining Mozilla Thunderbird files to Outlook 2016. About that time two bad viruses appeared and Intel decided to replace or patch the BIOS to save me from those nasty, virulent viruses. Well the first patch wasn't enough so Intel issued another BIOS. My digital Registration Key (PKEY) for my new Office 2016 was lost. Microsoft won't give it back or fix it. So none of Office 2016 works and I'm back to Mozilla Thunderbird minus my address books and archived emails and Office 2003. Ain't America Great??

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-05T23:57:59+00:00

    Microsoft should bring back the FIX -IT  program,to correct problems like this.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-05T18:57:40+00:00

    @NeuroShock  I've had similar "issues" and believe the problem is that the instructions posted earlier were for Windows 8.1, not the latest Windows 10.  One of the unfortunate aspects of the way Microsoft has maintained their forums is that there are a lot of people who tend to ignore the context of a specific post.  When threads get as long is this one, it can be a PITA

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-04T19:05:49+00:00

    Nope. Does NOT work for me.

    I have 5 desktops and 3 laptops in our home all running Windows 10 home. 2 laptops and 2 of the desktops all have this problem currently.

    If I try to enter any of the commands in the instructions that many ppl say are working I simply get an error message:

    A positional parameter cannot be found that accepts argument 'start= auto'

    Please realize I HAVE read this entire thread and several ppl have pointed out that the syntax must be correct for the start= auto portion.

    I have entered it every way possible. No spaces whatsoever before and after the equal sign, spaces before AND after the equal sign and a space before OR after the equal sign.

    All variations produce the same basic error but with whatever syntax variation I used in the error message.

    I am logged into windows as an Administrator and have verified my Administrator privileges. I also chose the Windows Power Shell with Administrator privileges.

    It reminds me so very completely of an old auto-update snafu we had with Windows Vista not too long after its release. Frustrating.

    Please message me or email me if you are reading this and find a solution to this.

    Thanks,

    NeuroShock

    ******@n0spamgmail.com

    Was this answer helpful?

    0 comments