Cumulative Update KB4074588 Windows 10 v1709 Build 16299.248 - Feb. 13

We clean installed a few hours ago, 16299.248
and there was a strange update on the third attempt (WU).

Under Feature Update (1)

Feature update to Windows 10. version 1709. Successfully installed on 2/20,2018.

No KB #, nothing else.

I also have the problem with this update and I thought I would post what is happening in the interest of trying to resolve it. The update appears to download and install ok according to the information under Settings\Update and Security. It sits there waiting for a restart which when generated appears to run but fails to update anything. WINVER confirms it has not updated and when you look at Control Panel\programs and features\Installed Updates it is sometimes there but with no install date which confirms it hasn't worked.Update and security also confirms it has failed to install.
I found this post on Microsoft answers
We couldn, error - Microsoft Community
and in particular the post from PaulSey on 16th feb suggesting "SC config trustedinstaller start=auto" from Admin Command prompt.

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



This made a difference in as much as I now see numerous blue screens with the "Updating Windows do not turn off" message. There are a number of restarts and it all appears to be doing its thing but alas fails at the final hurdle with no error message other that those mentioned above.
Any suggestions as to what i can check or do to enable the update?
I have run Shawn's batch file which ran ok but didn't help.

So I mistakenly reset her PC Windows 10. Now I'm cooked. Downloaded the recent ISO and will see if it will keep all her old files, plus windows.old. If not it's going to be an all day affair. Any suggestions?

Bree said:

A clean install of Fall Creators Update (version 1709, build 16299) does not show that. That is a standard item in the Update History if you have upgraded to FCU from an earlier version.

I suspect your install media was for an earlier version (1703 or earlier). It would have checked for updates after install and upgraded to 1709. If so, you will have a windows.old folder.

When did you get the install media? If it was before 17 Oct. 2017 then it's an earlier version of Windows 10. To confirm that, right-click on the Setup.exe on the media and look at the Details tab for its Properties. The 'Product version' will be the same as the os build number that it will install, for FCU media that would show 16299.15.

I downloaded manually KB4087256 after and the popup was saying already install. It is not shown in updates list, but Control panel shows it.

For the I SO, it comes from creators tool first release 16299.15. So, maybe the feature update is this one:

KB4087256 Servicing stack update for Windows 10 v1709 - Feb. 13 - Windows 10 Forums

For those having issues, this is what finally worked for me after 22 "failed installs":

1- Downloaded the KB4074588 update from the Windows Update Catalog.
2- Disconnected from Internet.
3- Went to Control Panel ----> Uninstall Programs -----> View Installed Updates
3- Oh, what's that??? Oddly, it showed the update, however, it had no install date. Uninstalled. (It took a few minutes to uninstall)
4- Reboot.
5- Double click the downloaded MSU file that you downloaded in Step 1.
6- Wait forever because this update takes foooooorever to install. (At least it did on this computer, an approx. 12 year old HP w/ an AMD Turion 64)
7- Reconnect to the internet.
8- Viola! (or Presto! if you prefer) The update is now installed correctly.

Optional:
9- Throw laptop in the trash in three weeks and go buy a brand new one and repeat these problems again in 11-12 years on Windows 15. (At least, that is what I'm doing. )

Nevermind. Windows update came up again and starts downloading. Back to step 0. I didn't get the update failed message in the Notification Center, but if I look at installed updates in control panel, it is listed as before without an install date.

You can block the update using http://wushowhide.diagcab and wait until MS figures it all out. Apparently this is not an isolated issue.