Windows 10: Cumulative Update KB4090913 Windows 10 v1709 Build 16299.251 - Mar. 5

UPDATE 3/13: Cumulative Update KB4088776 Windows 10 v1709 Build 16299.309 - Mar. 13 - Windows 10 Forums

Source: https://support.microsoft.com/en-us/...build16299-251


Direct download links for KB4090913 MSU file from Microsoft Update Catalog:

*Arrow Download KB4090913 MSU for Windows 10 v1709 32-bit (x86) - 377.2 MB

*Arrow Download KB4090913 MSU for Windows 10 v1709 64-bit (x64) - 688.8 MB




Tip How to Turn On or Off Push Notifications for New Windows 10 Builds from TenForums.com

 

Cheers Brink, all installed and no nasty surprises - very quick one. Bit out of band being late Monday night ((UK) time

:)

 

Windows Update error code 0x80070032

Try installing 16299.251 update manually:

https://www.tenforums.com/windows-10-news/10550...

 

USB Thumbdrive

Install KB4090913 and see if that fixes it:

https://www.tenforums.com/windows-10-news/10550...

 

Downloading now. *Party

 

...and it is named as if it were a February update:
'2018-02 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4090913)'

 

Fast and smooth. All went well here!

 

My x86 machine downloaded to 100% then restarted the download before successfully installing. Checking the update history shows two failed installs (error 0x80240034) and a third successful one.

Microsoft | Windows Update error code list

My x64 machine had no problems, installed on first attempt. But after the install SuperFetch did go mad for about five minutes with 100% disk activity. All calm and working well now *Smile

 

Yup. . . you're right. . *Wink





Interesting. . .

 

This caught me by surprise as just finished a Ryzen 5 1600 build and when rebooting after sorting out the lan drivers it installed the update, must have downloaded at light speed!
Other two PC's I've had to go look for it.

 

My guess, it's an out-of-band urgent fix that was planned to be released at the end of Feburary, but when the timescale slipped they forgot to rename it *Biggrin

 

After what was a quick download and install and after rebooting, then logging in, but before the desktop, I got these spastic Window's handholding screens.

First it was just a black screen with 'Hi' that flickered on an off.
then a more steady, 'We're getting everything ready'
then it returned to 'Hi' again,
then a blue fading in out of 'This might take several minutes'
then 'Making sure your apps are good to go'
then 'It's taking a bit longer than expected, but we'll get there as fast as we can'
then back to the 'Hi' again where it would repeat this sequence of messages,
sometimes skipping back to the 'Hi' screen again before getting to the last of the sequence

Eventually after an hour of this looping, and against Window's 'advice', I pressed and held down the power button.

Logging in again there were no screen messages as before, and everything appears fine - update reported as successful, sfc /scannow comes up clean.

Event Log shows it got stuck looping 900 times on this the first time:

Failed with 0x2 retrieving AppModel Runtime status for package windows.immersivecontrolpanel_10.0.1.1000_neutral_neutral_cw5n1h2txyewy.

 

Those screens are normally only seen at the first sign in of an existing user after a Features Update, that is to say after an upgrade like the one from 1703 to 1709. Each account will see this once after a features update. It's also seen at first sign in of a newly created user account. It's called the 'First sign-in animation', more on that here...
Turn On or Off User First Sign-in Animation in Window 10

If (like me) you have many accounts on the PC then it's possible for a little used account that the first sign in may be long after the features update. I have checked a number of my accounts, and none of the show the 'Hi' etc. screens after this cumulative update. Were you signing in with your usual account? If not (and you hadn't used the account for some time) that may explain it (though not the errors).

 

I got KB4090913 and KB4090914. What's up with that?

Edit: servicing stack update issued today.

*Arrow KB4090914 Servicing stack update for Windows 10 v1709 - Mar. 5 - Windows 10 Forums

 

@Bree, thanks for the feedback.

Honestly when I first saw these screens I thought somehow 1803 was coming in early. I was dreaming of course.

I only have one account, the one I used. Looking further into the event logs I saw other weird issues. Multiple explorer.exe faults, the user account couldn't be found in the registry, and worst of all Windows Activation failed. Running the Activation troubleshooter it said a valid digital license for this PC running Windows 10 Pro was found. It then suggested I install Windows 10.

I have a pretty good sense of humor, so I thought 'Yeah, that's what I'll do'

So I've just re-imaged from last nights Macrium backup, which shows I am indeed activated for Windows 10 Pro and glutton for punishment that I am, I've requested the update again just to see what happens.

oops, gotta go...it's asking for a restart..

I'll keep you posted.

Thanks,
Geoff