We couldn't finish installing updates (KB4074588), error 0x80070bc2

Anonymous
2018-02-15T03:44:33+00:00

Hi.

I'm unable to install the latest windows update 2018-02 Cumulative update for Windows 10 version  1709 for x64-based Systems.

The error is 0x80070bc2

It says updates are available, awaiting restart. When I restart it fails. "We couldn't finish updates.." Then says updates are available, awaiting restart. I restart again and it fails again. Over and over.

I tried using windows update troubleshooter, the tool performed its fixes but it had no effect.

Is there a solution to this?

Thanks

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-02-16T20:08:03+00:00

(Update - 2/17 Editing for clarity based on feedback)

If you are currently experiencing the 0x80070bc2 error while attempting to install KB4074588, please try this:

  1. In the search box on the taskbar, type cmd.
  2. Right-click Command Prompt in the search results and select Run as administrator.  (Select Yes, when prompted by the User Account Control.)
  3. In the Administrator: Command Prompt window, type the following command and press Enter:

SC config trustedinstaller start=auto 4. Restart the PC.

In some cases, a second restart may be required. If you look under Settings > Update & security and you see the message Status: Awaiting restart, restart the PC a second time to complete the installation.

Paul...

Was this answer helpful?

0 comments No comments

119 additional answers

Sort by: Newest
  1. Anonymous
    2018-02-20T11:57:44+00:00

    ok. for me it worked on x32 tablets with intel atom bay trail.thank you

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-19T23:14:09+00:00

    La risposta al comando è:

    PS C:\WINDOWS\system32> SC config trustedinstaller start = auto

    Set-Content : Impossibile trovare un parametro posizionale che accetta l'argomento 'start'.

    In riga:1 car:1

    • SC config trustedinstaller start = auto
    • 
      

        + CategoryInfo          : InvalidArgument: (:) [Set-Content], ParameterBindingException

        + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetContentCommand

    I couldn't really understand I only speak English,reading it I think u went into command prompt, and the dism command didn't work I got the same,i tried to download it manually that didn't work either all in all I must have tried over 30 times to download it and I ran all the trouble shooters nothing worked,even the tek bloke from Microsoft couldn't get windows update to work,he said it had stopped working he then did a reinstall,problem solved its ok now so I suggest a reinstall.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-19T23:10:19+00:00

    questa è la risposta al comando

    PS C:\WINDOWS\system32> SC config trustedinstaller start = auto

    Set-Content : Impossibile trovare un parametro posizionale che accetta l'argomento 'start'.

    In riga:1 car:1

    • SC config trustedinstaller start = auto
    • 
      

        + CategoryInfo          : InvalidArgument: (:) [Set-Content], ParameterBindingException

        + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetContentCommand

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-19T23:05:49+00:00

    La risposta al comando è:

    PS C:\WINDOWS\system32> SC config trustedinstaller start = auto

    Set-Content : Impossibile trovare un parametro posizionale che accetta l'argomento 'start'.

    In riga:1 car:1

    • SC config trustedinstaller start = auto
    • 
      

        + CategoryInfo          : InvalidArgument: (:) [Set-Content], ParameterBindingException

        + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetContentCommand

    Was this answer helpful?

    0 comments No comments