Microsoft’s July 2018 patch mess – put update install on hold

[German]Another short patchday summary for administrators in business environments. July 2018 patchday (July 10, 2018) is proving more and more a disaster – currently every administrator should consider whether and which updates he releases for installation. 


The clever administrator only releases updates for servers and clients manually if it is clear that's save to be installed. I provided an overview of the updates of July 3 and 10, 2018 in various blog posts (see link list at the end of the article). But that is not the end of the story, patchday is the beginning of a process that I guess has developed to a little disaster. Here is a summary of what an administrator should have taken note of – it's part II of my article July 2018 Patchday issues, KB4018385 pulled – Part I.  

Re-Releases in Microsoft Update Catalog

I was already informed on July 12, 2018 that Microsoft has released a massive flood of re-releases of updates in the Update Catalog.

Just for the records: Patchday was July 10, 2018 – and on July 12, 2018 (see also this article by Woody Leonhard) a flood of 'updates' dated July 13, 2018, arrived on Microsoft Update Catalog. That's more than crazy.

Update issues documented within the blog

During the last days I have spent, besides writing the patchday articles, documenting some more serious problems caused by the July 2018 updates. Here are the links to the respective.


.Net Framework: Update KB4340558 drops error 0x80092004?
DHCP-Bug in Update KB4338814 (Windows 10 Version 1607)
July 2018 Patchday issues, KB4018385 pulled – Part I

Blue screen bingo with July 2018 updates

Susan Bradley has published an overview of the July 2018 patches and known issues on (I've already been tweeted). It's not nice what we read there.

Update KB4338819 for Windows 10 V1803

Update KB4338819 for Windows 10 V1803 has two know issues, that Microsoft has added to its kb article:

  • After installing this update on a DHCP Failover Server, Enterprise clients may receive an invalid configuration when requesting a new IP address.  This may result in loss of connectivity as systems fail to renew their leases.
  • After installing this update, some devices running network monitoring workloads may receive the 0xD1 Stop error because of a race condition.

There is no workaround for either bug. Microsoft is working on a solution and hopes to make it available in mid-July 2018.

Update KB4338825  for Windows 10 V1709

Update KB4338825 for Windows 10 V1709 has four known issues documented now from Microsoft. In addition to the two points I already mentioned in the blog article Patchday: Windows 10-Updates July 10, 2018, the DHCP and 0xD1 stop errors mentioned for KB4338819 have also been added.

Update KB4338826 for Windows 10 V1703

Update KB4018126 for Windows 10 V1703 drops a blue screen 0xD1 mentioned at update KB4338819.

Update KB4338814  for Windows 10 V1607

Update KB4338814 for Windows 10 V167 has the DHCP-Bug (see DHCP-Bug in Update KB4338814 (Windows 10 Version 1607)) and the stop error 0xD1 mentioned at KB4338819.

Update KB4338829  for Windows 10 V1507 (LTSC)

Update KB4338829 for Windows 10 (RTM)drops a blue screen 0xD1 mentioned at update KB4338819

Susan Bradley has raised other issues for Windows 7 and Windows 8.1 updates in the table in this article

Stop July 2018 update rollout recommended

If you go through the above and the rest of my blog posts for July 2018 updates, it becomes clear that Microsoft has a massive quality problem with these updates. One of my sources told me not to roll out updates for Windows Server 2008 R2 because of quality issues (I know the source of the information without being able to disclose it). I'm going to extend that warning: Think about stopping July 2018 update rollout to your machines.

Similar articles:
Adobe Flash Player Version
Microsoft Office Patchday (July 3, 2018)
Patchday: Windows 10-Updates July 10, 2018
Patchday: Updates for Windows 7/8.1/Server July 10, 2018
Patchday Microsoft Office Updates (10. Juli 2018)
Microsoft Patchday: Other Updates July 10, 2018

Cookies helps to fund this blog: Cookie settings

This entry was posted in Update, Windows and tagged , , . Bookmark the permalink.

3 Responses to Microsoft’s July 2018 patch mess – put update install on hold

  1. Karl Wester-Ebbinghaus says:

    There is a correlation between a new Windows release output (RS5 1809), summer and bad quality updates.

    As a specialist for WSUS and holder of MSCA certificates for Windows Servers and Office 365 I recommend to never release updates automatically on WSUS or Office 365 since March 2017 without a waiting period of at least 2 weeks and prior release to an evaluation group.

  2. Brad says:

    Since this is the second time in 12 months this has happened, I'm changing our policy today to manual updating. We use GFI for Windows updates which it applies automatically. GFI can't tell the difference between a regular cumulative update and a delta for it, especially when they are released the same day. Add to that yet another July patch, and the result is completely hosed component stores on many Win10 clients here. I'm having to go in with DISM and remove the mess manually…waaaay too time-consuming. Since Microsoft can't seem to ever get this right, we're going to wait on all updates until the dust settles (sorry to everyone else in the MS customer QA department)

Leave a Reply

Your email address will not be published. Required fields are marked *