July's Patch Tuesday came and went last week, bringing along a slew of security and bug fixes. But Microsoft is following up a week later with another set of cumulative updates for three Windows 10 releases (via Neowin).
The Windows 10 April 2018 Update, Fall Creators Update, and Creators Update are all picking up a similar batch of fixes this evening. If you're on the latest version of Windows 10 (version 1803), you'll see KB4345421, pushing the build number up to 17134.166 with the following fixes:
- 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.
Meanwhile, if you have a machine still running the prior version, the Fall Creators Update (version 1709), you'll get KB4345420, bumping the build up to version 16299.550 with the same set of fixes as the April 2018 Update. The Creators Update is similarly seeing KB4345419, moving to version 15063.1208 with the same fixes, minus the DHCP failover fix.
For each release, there are known issues to check out with everything except for the new Creators Update build. For more, you can check out Microsoft's full release notes. Otherwise, each cumulative update should be available via Windows Update now.
Dan Thorp-Lancaster is the Editor in Chief for Windows Central. He began working with Windows Central as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl. Got a hot tip? Send it to email@example.com.
17134.167 looks to be the current version.
As much as I appreciate Microsoft pushing out these updates as soon as possible, it's really going against the concept of "Patch Tuesday" for businesses.
Desperate situations call for desperate actions.
I'm from 17134.167 to 17134.166?! No! I'm still on 167. Why this 166 no?
looks like I have also 1734.167
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.