window 10 update for KB4074588 OS Build 16299.248 with error code 0x80070bc2

(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...

When installing manually, the installer reports that the update is already installed, which is definitely not the case. With me only helped:https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/getting-error-0x80070bc2-doing-cumulative-update/24e80681-eb22-4439-8677-638fce437186?page=7Post from 5.February 2018

tried what you said and now get the same error message as with command prompt. 

If you are entering  sc.exe  you would not be seeing a message that starts with  Set-Content...   So, what is the exact message that you are seeing now?   Note that you could enter  sc.exe  -?   to see the syntax and help for the cmd shell's SC command.  You would be seeing an error message if you were not using an elevated shell (AKA running with Administrator authority).   You didn't show us the PowerShell window's title so it is possible that what you did show us is someone using a user level PowerShell command line which had only reached the  %windir%\System32  directory manually (instead of by getting that by starting a shell via right-click Run as Administrator, for example).

I see now that you are saying you are getting "Access denied".  The most likely reason is that you are not using an elevated shell.  However, it is also possible that you are being explicitly inhibited from using the  sc.exe config  command.  See what you get from  sc.exe  qc  trustedinstaller   instead.  That is just a query and would not require the authority to issue any changes; apparently it could even be done by a normal user, who knew?  At least it would verify if you could use the sc.exe command.

FYI

Robert

---

Thanks.  The query worked so I am not being blocked from the SC command.  This is what I got back

[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: trustedinstaller

        TYPE               : 10  WIN32_OWN_PROCESS

        START_TYPE         : 2   AUTO_START

        ERROR_CONTROL      : 1   NORMAL

        BINARY_PATH_NAME   : C:\WINDOWS\servicing\TrustedInstaller.exe

        LOAD_ORDER_GROUP   : ProfSvc_Group

        TAG                : 0

        DISPLAY_NAME       : Windows Modules Installer

        DEPENDENCIES       :

        SERVICE_START_NAME : localSystem

I assume that this means that Auto start is already on.

Download it manually from the Microsoft Update Catalog at the following link then manually install it:

http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4074588

See instructions how to manually install the update:

https://www.groovypost.com/howto/manually-install-standalone-cumulative-updates-virus-definitions-windows-10/

I found the same solution done a slightly easier way on this site http://www.freefixer.com/b/kb4074588-update-fails-install-0x80070bc2-windows-10/#comment-2729

(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...

Thanks a lot, Paul, for your work and wonderful solution - it worked like a charm.

I still wonder why on Earth does Windows keep releasing faulty updates...

Dragos ...

it  works ! thank you!

YES!  It set off a long cycle of checking for updates, downloading this one again, installing it and then various restarts, but got there in the end.  Took at least 30 mins.  Just don't panic if you try it and nothing useful seems to be happening for a while.

(Right-clicking on this update in the installed update list gives a MS message that the "failure to install" messages may not be right - so was this update installed all the time?  Can I be sure that it is now?  Talk about Schrodinger's cat.....)

We are aware some customers are experiencing this issue and it is being investigated.

If you have not already done so, please go to the Feedback Hub and submit this issue. The diagnostic information collected by the Feedback Hub will assist in the investigation.. 

For more information on Feedback Hub, see our support article and YouTube video

Paul...

Hi John,

If you are unable to install specific cumulative updates, you can download them manually or directly. Visit this site: Microsoft Update Catalog and search for this specific KB update that doesn’t installed yet on your computer.

Once you’ve found it, start downloading. Before you attempt to install it, we would also recommend to turn off your anti-virus temporarily and get a stable Internet connection.

Let us know if the installation gets successful.

Thanks. I tried this step. It is not working. The Windows Update utility keeps listing KB4088787 as available as an update and when I go the through the installation, it fails. 

I have tried manually installing it as another site had recommended. It goes through without any errors. However, when I list all the installed KB's using the 'dism' command, KB4088787 is not listed, and the KB is offered again for installation.

I find it quite frustrating that all I get is a failure message but no details on why it failed. Scanning the Internet, it looks like MSFT is claiming that it is not aware any such issues with this KB. I could let them know if I knew how to contact them.

Now MSFT is warning that in about another week, my Windows 10 version would be obsolete and it would get no more updates.

Is there a solution? If MSFT obsoletes the current version and does not help with updating to the latest version, should all the affected parties pursue a legal avenue?

I have no trustedinstaller service......

(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...

Thank you very much..this solution has worked for me,

Ivan....

After 4 weeks of not being able to update my Dell XPS 27 AIO, and reading through hundreds of suggestions, this solution actually worked! The system rebooted 4 times and the process took about 20 minutes. But the end result is that the latest Cumulative Update successfully installed. Thank you Paul Sey! You are a genius!....Norm

(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...

Thank you very much..this solution has worked for me,

Ivan....

You literally saved me from throwing a brand new Surface Book 2 which I was preparing for a client down the stairs! After numerous failed update attempts your advice saved the day (and maybe even the weekend!).

So thanks a lot, if I could buy you a Belgian beer,  I would immediately!

Thanks SO MUCH Paul for your instructions.   It worked great for me.

I probably tried to do the Windows update called:  "2018-02 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4074588)" ... at least a dozen times or more ... and it simply would not update on one of my Dell laptop.  This update ... updated just fine on my HP desktop PC, and my other HP Laptop, but would not update on my Dell laptop.  :-(

So... after following your instructions... (on my Dell laptop) ....

When the "Restart" finally occurred ... it said something like ... downloading or updating Stage 2 of 2.

It took about 10 to 15 minutes for me ... but it finally updated my system successfully ... from OSB 16299.192 to OSB 16299.248.

I am so happy I googled for help on this, because I was about #50 in the que to get help from the online Microsoft Support.

Thanks again Paul !   :-)

--- Tom

         START_TYPE         : 2   AUTO_START

I assume that this means that Auto start is already on.

Yes.  Either one of your previous attempts worked or you didn't need this workaround after all.  FWIW mine still says DEMAND_START  but so far I have not had a problem with updates, especially not a problem with the network connection.

BTW thanks for sharing your resolution.

On the 3rd attempt to install the update it worked.

tried what you said and now get the same error message as with command prompt. 

If you are entering  sc.exe  you would not be seeing a message that starts with  Set-Content...   So, what is the exact message that you are seeing now?   Note that you could enter  sc.exe  -?   to see the syntax and help for the cmd shell's SC command.  You would be seeing an error message if you were not using an elevated shell (AKA running with Administrator authority).   You didn't show us the PowerShell window's title so it is possible that what you did show us is someone using a user level PowerShell command line which had only reached the  %windir%\System32  directory manually (instead of by getting that by starting a shell via right-click Run as Administrator, for example).

I see now that you are saying you are getting "Access denied".  The most likely reason is that you are not using an elevated shell.  However, it is also possible that you are being explicitly inhibited from using the  sc.exe config  command.  See what you get from  sc.exe  qc  trustedinstaller   instead.  That is just a query and would not require the authority to issue any changes; apparently it could even be done by a normal user, who knew?  At least it would verify if you could use the sc.exe command.

FYI

Robert

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

Set-Content : A positional parameter cannot be found that accepts argument 'start=auto'.

If you want to use PowerShell you need to be aware that sc is an alias for its Set-Content cmdlet (as clearly implied by the message you get).  Workaround is to enter the full sc.exe program name.  When you are entering cmd shell command lines in PowerShell it is also often a good idea to use PowerShell's command line escape string --% between the program name and its arguments; however, in this case there should be no confusion caused by not doing so.

FYI

Robert Aldwinckle

---

Thanks for the Power Shell info.  I tried what you said and now get the same error message as with command prompt.  I was trying Power Shell to see if it made a difference.  Turning antivirus off does make a difference :-(

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

Set-Content : A positional parameter cannot be found that accepts argument 'start=auto'.

If you want to use PowerShell you need to be aware that sc is an alias for its Set-Content cmdlet (as clearly implied by the message you get).  Workaround is to enter the full sc.exe program name.  When you are entering cmd shell command lines in PowerShell it is also often a good idea to use PowerShell's command line escape string --% between the program name and its arguments; however, in this case there should be no confusion caused by not doing so.

FYI

Robert Aldwinckle

(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...

I get Access is denied when executing -SC config trustedinstaller start=auto.  I tried twice to make sure I was opening the Command Prompt as an administrator.

I tried using the Power Shell and get the following:

Windows PowerShell

Copyright (C) Microsoft Corporation. All rights reserved.

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

Set-Content : A positional parameter cannot be found that accepts argument 'start=auto'.

At line:1 char:1

• SC config trustedinstaller start=auto

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

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

PS C:\WINDOWS\system32>

(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...

I get Access is denied when executing -SC config trustedinstaller start=auto.  I tried twice to make sure I was opening the Command Prompt as an administrator.

See my reply to PaulSey - his solution worked.  (This is another case of MS putting out a defective product to its customers - do they not trial these updates first?)

Awaiting restart  after restart nothing happen  Update & security and you see the message Status:Awaiting restart not going windows event not updating

It worked for me too.  Many thanks!

I also have the same question.

I've tried eight times now to install this.  Same message each time: " installed pending restart", but that doesn't work.  Have tried all the suggested solutions: installing manually, the update Troubleshooter, Update Catalog etc.  Stuff it.  Looks like another MS update that is not fit for purpose.  Am going to walk away from this until MS do their job properly and reissue a version that works.  Life is just too short to waste time on this sort of thing.

I have the same error 0x80070bc2, now 8 times. 

PS>net helpmsg (0xBC2)

The requested operation is successful. Changes will not be effective until the system is rebooted.

Have you tried rebooting without any interferers present?  You may have to uninstall them, not just disable them.  It may help to have a boot menu to try to make changes between the update phases (or at least to try to see what is going on.)

HTH

Robert Aldwinckle

@ Johann Eva 

Winver shows Version 1709 (Build 16299.248) so this is ok.

I have the same error 0x80070bc2, now 8 times.  I tried the manual update but, like another user, got the message that the update is already installed.  But when I check, it gives the version as 16299.192 so 19299.248 is not installed.

We would like to confirm if you already updated Windows to its latest version. Is this thread you're pertaining already helped you completely or not? Can you tell us the status?

If you need more help, you can contact us again. We are just here for you.