New
#10
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.
KB4090914 Servicing stack update for Windows 10 v1709 - Mar. 5 - Windows 10 Forums
Last edited by Brink; 05 Mar 2018 at 23:09. Reason: added link
@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
Last edited by Farvatten; 05 Mar 2018 at 23:59.
Installed quickly on my Dell Inspiron 7559. However, after the restart, I checked Reliability History like I always do after every Cumu Update and it's not showing up in there. It doesn't show up in "Installed Update History" either. The OS Build is correct, though. Not sure what's up with that. Everything seems to be running just fine.
It's downloading! It's automatically downloading! I don't have to go get it manually! I didn't even have to manually check for downloads! I could cry right now.
Well that was fast AND productive....
So, no problems this time logging in after the second attempt at getting this KB4090913 update.
Macrium Reflect - again my hero.
Of note: During that first attempt, during the installation phase of the update just before restart, Windows WAS in the middle of doing Maintenance Tasks at the exact same time. I know this for a fact because I had a visual alert pop up that I've set to notify me whenever Window's removes it's 'out of date' Windows Defender Platform folder where MpCmdRun.exe was last found. ( C:\ProgramData\Microsoft\Windows Defender\Platform\4.12.17007.18011-0) required by a scheduled scan task command I run.
Finally installed on both machines. It got a bit scary at one point; my main machine (only two and half years old) on which I started the download first finished last compared to secondary machine (more than 8 years old). On the main machine, the download went smooth, but after the "restart" it hung at 82% for more than one hour. I was even at some point going to turn it off with the power button when it suddenly finished and gave the lock screen. Ouff!!
Ooooh-KAY?! Now that was a bit of a straaaaange install... Kept on falling back halfway to 1 % en krept on to 64%... Falls back to 1%, then to 54%, falls back again to 1% and finally reaches 100% where it sits for a few seconds... and completes the installation...
WEEEEEIRD!