[German]Update KB4487006 released by Microsoft in February 2019 for Windows 10 V1607 and its server counterpart KB4487006 causes some servers to crash with blue screens.
Update KB4487006 for Windows 10 V1607
I had blogged about this update in the blog post Windows 10 Updates (Feb. 19/21, 2019). The cumulative update KB4487006 for Windows 10 V1607 is only available for Windows 10 Enterprise and Education – and Clovertrail chipset machines – and raises the build to 14393.2828. This update contains a long list of bug fixes listed in the KB article.
Known issues with the update
When I published the blog post, Microsoft had not mentioned any known issue within the kb article for this update. However, when I wrote this blog post, I noticed that Microsoft has now added the following information to the Known Issues section.
|For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update. Additionally, if you do not follow the best practices (Link https://blogs.technet.microsoft.com/scvmm/2018/12/21/system-center-virtual-machine-manager-fails-to-enumerate-and-manage-logical-switch-deployed-on-the-host/ deleted), a stop error may occur in vfpext.sys on the hosts.||
|After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.||Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart. If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled. Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device.|
|After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.||Set the domain default “Minimum Password Length” policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.|
|After installing this update, Internet Explorer 11 may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
||Create unique user accounts so that two people don’t share the same user account when logging on to a Windows Server machine. Additionally, disable multiple RDP sessions for a single user account for a specific Windows Server. Microsoft is working on a resolution and will provide an update in an upcoming release.|
|After installing this update, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.||Ignore the error. Microsoft is working on a resolution and will provide an update in an upcoming release.|
|In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off. The faulting driver is win32kbase.sys.||Microsoft is working on a resolution and will provide an update in an upcoming release.|
Some bugs like startup issues with Lenovo and Fujitsu notebooks have already come to my attention with other Windows 10 updates. But I don’t read anything about a BlueScreen in the list of known issues. In this German comment blog reader Toni even writes:
Tatsächlich sind bei uns einige v1607 mit einem Bluescreen, für den win32kfull.sys ursächlich war, gegen den Baum gelaufen. Die Installation von KB4487006 löst das Problem. Danke für den Hinweis!
He says: In fact, some of our v1607s [machines] ran into a blue screen caused by win32kfull.sys. Installing KB4487006 solves the issue. So we’re good? Doesn’t really look like it, then you have to read between the lines at Microsoft.
Windows Server 2016 may be affected by blue screens
At Askwoody I came across the article here. Woody Leonhard interprets the above text as:
In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off. The faulting driver is win32kbase.sys.
Microsoft’s text is the nice paraphrase of a BlueScreen (BSOD) where the system crashes and reboots (if this option is active). In this Technet thread, some users have reported that their servers are affected by this BSOD. Since this is an optional update, it should be hidden on Windows Server 2016. Under WSUS it doesn’t seem to show up (see) or it has to be released explicitly anyway. Any of you affected?
Cookies helps to fund this blog: Cookie settings