Microsoft fixes July 2018 updates for Windows 7, Windows 8.1, and Server

Martin Brinkmann
Jul 17, 2018
Windows, Windows 7, Windows 8
|
12

A lot of things went wrong on the July 2018 Patch Day on July 10, 2018. System admins and users flocked to forums and support sites to report all kinds of issues starting with installation issues and ending with issues that caused certain features to work incorrectly.

Microsoft published KB4345421 for Windows 10 earlier today that addresses issues on Microsoft's newest operating system.

Updates for Windows 7, Windows 8.1, Windows Server 2008 R2, and Windows Server 2012 R2 are now also available.

KB4345459 for Windows 7 and Windows Server 2008 R2

KB4345459, Improvements and fixes - Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1, includes quality improvements according to Microsoft.

The following changes are listed on the Knowledgebase website:

  • Addressed issue in which some devices may experience stop error 0xD1 when you run network monitoring workloads.
  • Addresses an issue that may cause the restart of the SQL Server service to fail 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.

Admins and users can download the update from the Microsoft Update Catalog website. The update has a size between 23.9 and 43.7 Megabytes.

KB4345424 for Windows 8.1 and Windows Server 2012 R2

KB4345424

KB4345424, Improvements and fixes - Windows 8.1 and Server 2012 R2, addresses the same issues that KB4345459 addresses.

You can download the update from the Microsoft Update Catalog website. The update has a size between 24.1 Megabytes and 39 Megabytes.

KB4345425 for Windows Server 2012

KB4345425

You may have guessed it already, KB4345425, Improvements and fixes - Windows Server 2012. fixes the same issues as the other updates mentioned above.

It is available as a direct download on the Microsoft Update Catalog website. The update has a size between 25.4 and 40.9 Megabytes.

.NET Framework updates

Microsoft released .NET Framework Updates as well. While KB4340558 and KB4340557 have been updated. The known issue about error 0x80092004 being thrown still exist though according to the release notes.

It is possible that Microsoft did not update the description yet and that the issue is resolved. Any feedback on that is much appreciated.

Closing Words

The  July 2018 patches introduced quite a few issues; several of the issues were not listed initially on the support pages but were added retroactively to the pages. Another reason to wait with the installation of updates to make sure that they don't introduce issues of their own.

Now You: What was your experience with the July 2018 Patch day? (via Born)

 

Summary
Microsoft fixes July 2018 updates for Windows 7, Windows 8.1, and Server
Article Name
Microsoft fixes July 2018 updates for Windows 7, Windows 8.1, and Server
Description
Microsoft release updates for Windows 7, Windows 8.1, Windows Server 2008 R2, and Windows Server 2012 R2 on July 17, 2018.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Tutorials & Tips


Previous Post: «
Next Post: «

Comments

  1. sohannin said on August 8, 2018 at 9:39 pm
    Reply

    This seems to affect all kinds of network related apps like Oracle db listener, Manage Engine Desktop Central, self-made windows services using tcp/ip.

  2. A different Martin said on July 19, 2018 at 5:59 am
    Reply

    Starting the Friday after this month’s Patch Tuesday, I used WSUS Offline Update to download and install *security-only* updates (not quality rollups) on five Windows 7 x64 systems and one Windows 10 x64 system. (I don’t know offhand what build the Windows 10 system is, other than that it’s not the latest one.) On the Windows 7 systems, I had to deselect C++ Runtime and .NET Framework updates in order to get WSUS Offline Update’s download stage to run to completion instead of throwing a fatal error and aborting.

    At any rate, all of the updates installed fine, Belarc Advisor says all six computers are up to date security-wise, I haven’t had any problems on my own computer, and I haven’t heard any reports of problems on the other computers so far. Knock on wood…

  3. Anonymous said on July 18, 2018 at 7:21 pm
    Reply

    Dear Martin!

    Do we need to install KB4338823 before KB4345459 or is it enough to install only KB4345459 to a Windows 7 64 bit system, that has no 2018 July updates installed on it? With one word: does KB4345459 replace/supersede KB4338823?

    Thank you very much for your help!

    1. Martin Brinkmann said on July 18, 2018 at 8:01 pm
      Reply

      When you check the Update Catalog listing and there the package details, you see which updates KB4345459 replaces.

      https://www.catalog.update.microsoft.com/Search.aspx?q=KB4345459

      It does not replace https://support.microsoft.com/en-us/help/4338823

      1. Anonymous said on July 19, 2018 at 12:06 pm
        Reply

        Yes, I also checked the package details in Microsoft Update Catalog, but I found contradictory information on these sites:

        https://www.reddit.com/r/sysadmin/comments/8y5wev/exchange_server_2010_mail_flow_issues_after/
        In a comment, I found this:
        „Microsoft has released an updated patch, KB4345459 as a replacement for KB4338823”

        https://www.askwoody.com/patch-list-master/
        Next to KB4345459 we can read, that it replaces patch from 7/10.

        After all these, what is the truth? I think these are reliable sources, that’s why I asked you if you have any specific experiences.

        An other strange thing for me, that in Catalog we can see, that KB4338823 was last updated on 17 July while KB4345459 earlier on 16 July, so how can an older package be either a replacement or a patch to a newer released package?

        Is it possible, that the newer release (7/17/2018) of KB4338823 does no longer contain the bugs (or contains the fixes), which were in the old version (7/10/2018) of the package?

        It’s so good that Microsoft does never communicate the changes exactly…

      2. EP said on July 19, 2018 at 7:30 pm
        Reply

        mr anonymous, read the comments here about KB4345459 from the askwoody site:
        https://www.askwoody.com/forums/topic/microsoft-just-released-27-new-security-patches/

      3. Anonymous said on July 20, 2018 at 8:23 am
        Reply

        Thanks for the information.

  4. Mike said on July 18, 2018 at 4:55 am
    Reply

    This totally fixed an issue I was having that just started recently. On Windows 7 x64, both utorrent, and qbittorrent, when exiting the program, its process would hang, and never end. Forcing end task in task manager, did nothing, only rebooting would get it to end. This update fixed it.

    I assume it was related to, “The W3SVC remains in a “stopping” state, but cannot fully stop or it cannot be restarted.”

  5. dark said on July 18, 2018 at 2:22 am
    Reply

    Classic Shell is back btw as Classic Start. :)

    https://github.com/passionate-coder/Classic-Start

  6. Jonnyredhead said on July 17, 2018 at 10:52 pm
    Reply
  7. Henk van Setten said on July 17, 2018 at 10:40 am
    Reply

    “It is possible that Microsoft did not update the description yet and that the issue is resolved. Any feedback on that is much appreciated.”

    The issue appears to be not resolved yet. Just tried re-downloading and installing KB4340558 on Windows 8.1 x64. Resulted in an aborted installation with the very same 0x80092004 error as before.

    1. Pavel said on July 18, 2018 at 12:08 pm
      Reply

      On Windows 2012 and 2012 R2 Servers the same issue is present still

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.