While the whole Windows world was watching the Build keynote yesterday (you can see a 9-minute condensation of the three-hour presentation on The Verge), Microsoft pushed seven surprise patches out the Automatic Update chute.
They're all marked "optional," so you won't get them unless you go into Windows Update and check them, but they're in addition to the 34 optional nonsecurity patches released last Tuesday.
The patches appear to be innocuous and seem to mostly pave the way for Windows 10. Here's the list, along with the official descriptions:
- KB 3003729 -- April 2015 servicing stack update for Windows 8 and Windows Server 2012
- KB 3020369 -- Update 2819745 installation fails on a read-only domain controller (RODC) in Windows Server 2008 R2
- KB 3021910 -- April 2015 servicing stack update for Windows 8.1 and Windows Server 2012 R2
- KB 3045645 -- Update to force a UAC prompt when a customized SDB file is created in Windows
- KB 3046480 -- Update helps to determine whether to migrate the .Net Framework 1.1 when you upgrade Windows 8.1 or Windows 7 (presumably to Windows 10)
- KB 3048043 -- Screen flickers or becomes blank when you drag tiles on the Start screen in Windows
- KB 3048097 -- Compatibility update for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: April 2015
Did you notice that if you compare that list with the patches released on April 21, all seven are re-releases?
A word to the wise: KB 3046480 contains a new version of ntoskrnl.exe, the primary Windows kernel file. Kernel patches are notorious for causing hiccups. (t/h GT)
I haven't seen any problems reported with any of those patches, but apparently something wasn't working right. The one April 21 patch that did have publicly reported problems -- KB 3022345 fails to install with error 800F0922 -- isn't included in this crop of re-releases.
It's an old magician's trick: distraction.