[German]Microsoft has released a new Update KB4039871 for Windows 8.1 machines on August 25, 2017. It's a bit mysterious, what Microsoft intends with this update.
Advertising
I has been informed by a blog reader, who uses a couple of Windows 8.1 machines within a hotel environment (thx Leon). He noticed this night, that some of those machines received update KB4039871 (four systems from eight).
Currently update KB4039871 hasn't been documented by Microsoft. There is no KB article nor an entry within Microsoft Update Catalog. What I found out so far: This update has been flagged as important, but it's still optional and has a size of 271.7 MB (for 64 bit). A restart of Windows is required to install this update.
My best guess is, that this update fixes some issues caused by Monthly Preview Rollup Update KB4034663 (see Microsoft's Windows (Preview) Updates (August 15, 2017)). The size of Update KB4034663 (64 bit) is 271.0 MB.
I should note, that the japanese webite addresses this update also. If we know, that Preview Rollup Update KB4034663 addresses issues within Japanese Input Mode Editor (IME), it makes sense to assume, that the update addresses an issue within this area. At askwoody.com there are similar thoughts.
Currently I recommend not to install this update until more details are available.
Advertising
Addendum: Somebody mentioned, that after installing update KB4039871, the security update KB4034681 was removed from the installed update list.
Advertising
Pingback: Mysterious Windows 8.1 patch KB 4039871 making the rounds @ AskWoody
KB4039871 contains an update for WSUS (Windows Server Update Service).
https://support.microsoft.com/en-us/help/4039871/windows-8-1-windows-server-2012-r2-update-kb4039871
If you install KB4039871 on the WSUS server it fixes indeed the timeout issue from win 10 1607 and server 2016 when you create a reference image with MDT but the latest patches from September seems to supersede this patch and the problem with timeouts is back. If patch KB4038792 is installed, patch KB4039871 disappears and the timeout is back. Uninstalling KB4038792 resolves the issue again