Those on the latest Windows 10 April 2018 update will see KB4345421 and note a build number of 17134.167. It should roll out automatically, but a manual download is available here.
“The fixes primarily target networking issues, from DCHP Failover server issues to SQL Server TCP failures and more. Here’s the full log: Addresses an issue that may cause some devices running network monitoring workloads to receive the 0xD1 Stop error because of a race condition after installing the July update. Addresses an issue with the DHCP Failover server that may cause enterprise clients to receive an invalid configuration when requesting a new IP address. This results in a loss of connectivity. Addresses an issue that may cause the restart of the SQL Server service to fail occasionally with the error, ‘Tcp port is already in use’. Addresses an issue that occurs when an administrator tries to stop the World Wide Web Publishing Service (W3SVC). The W3SVC remains in a ‘stopping’ state, but cannot fully stop or it cannot be restarted.”
1709 and Known Issues
As you can see, these fixes are quite niche, but will greatly appreciate to those they impact. The Fall Creators Update’s KB4345420 contains the exact same fixes but also introduces some additional bugs. You should be aware that 16299.550 causes a very minor issue with localized language and Device Guard. Non-English platforms may also display ‘&’ and ‘.’ in English, causing the following issues:
“Cannot use ‘&’ or ‘.’ operators to invoke a module scope command across language boundaries. “‘Script’ resource from ‘PSDesiredStateConfiguration’ module is not supported when Device Guard is enabled. Please use ‘Script’ resource published by PSDscResources module from PowerShell Gallery.”
KB4345419 is for the Windows 10 Creators update and contains all the fixes other than the DCHP Failover, which wasn’t a problem on this version.
