It appears this morning I got a reboot prompt from Windows saying that some updates were ready to be applied and just needed to reboot to finish the job. I thought it was odd given it’s not Tuesday, but let the machine perform the reboot. On startup, a notification popped onto the screen saying the update was successful.
Looking into what had been applied, I found the update was caused by KB3035129 which lists the following fixes…
- Reliability improvements for virtual machine live migrations
- Reliability improvements to prevent some system crashes in SettingsSyncHost.exe
- Reliability improvements to prevent possible data corruption
- Increased power efficiency to extend battery life
- A fix for an issue that prevents the new Store (Beta) from appearing on the taskbar
- A fix for an issue that could cause users to remain at the “Please Wait” screen when attempting to sign in with a Smart Card connected
- A fix for an issue that could cause virtual machines (VMs) to lose connectivity to virtual hard drives (VHDs)
- A fix for an issue that could cause error 0x8E5E05E2 when installing apps
- A fix for an issue that could cause a delay when opening a new tab in Internet Explorer
- A fix for an issue that could cause the system to fail to resume from sleep when connected to multiple monitors with some graphics drivers
- A fix for an issue that could cause the Start Menu to be improperly registered and fail to launch
- A fix for an issue that prevents launching XBOX Live enabled games that require sign-in, and would incorrectly result in the message, “To use this app, you need to sign in with the Microsoft account that was used to download it.”
- A fix for an issue that could present the user with the incorrect End-User License Agreement (EULA) during upgrade
It appears to address a lot of show stopper type of issues that showed up in the 9926 build released last week and some VM issues that probably occured internally, which allows users to get a bit more testing done prior to the next Patch Tuesday of February 10th (assuming they keep the same pre-9926 wave of updates). It also happened to include something not listed and not meant for release, which is an altered version of Windows Update which allows users to choose which branch of Windows they want for their Slow or Fast update cadence. As you can see in this image of my Windows Update, I have the choice of pulling my updates from just the fbl_awesome1501 branch.
While that not be a big deal, it appears to make Windows Update attempts to get updates from the branch, which as of today is 9933 for Fast and 9932 for Slow.
The attempt to update fails because the build branch is evidently limited to Microsoft employees according to Gabriel Aul on Twitter…
— Gabriel Aul (@GabeAul) January 28, 2015
Now that Windows Update is stuck trying to get a build from a branch it can’t reach, I guess I have to live with what I have until they unblock the next build they want to share. Most likely on the next Patch Tuesday release.