Is KB4338818 causing any issues after patch install on Windows 7 and 2008 R2 systems?


  • Is KB4338818 causing any issues after patch install on Windows 7 and 2008 R2 systems?
    Wednesday, July 11, 2018 9:12 AM

All replies

  • Hi Anuj.

    The Microsoft Knowledge Base article 4338818 reports a known issue affecting the network interface controller and suggests a workaround to address it.


    Luigi Bruno

    Wednesday, July 11, 2018 9:36 AM
  • Server 2008R2 with Exchange 2010 SP3 has an issue - Transport Service for Exchange stops working ….. you can restart it but it will time out only a server reboot fixes the issue  …….. if you Telnet to Port 25 you will see it is shut therefore no email flow.

    This is what I have observed from clients with same config as over the weekend I applied the July 2018 update

    wusa /uninstall /kb:4338818

    Tonight I will uninstall the patch, not sure about July 2018 .net updates yet if there is any issues.

    KB4338818 (July 2018)

    Monday, July 16, 2018 1:14 PM
  • Cannot unistall .... Transport Service is in Hung state .... will try again after reboot 

    Monday, July 16, 2018 1:20 PM
  • One Server I have uninstalled the July 2018 update successfully

    Other Server after a reboot does not let me uninstall

    Monday, July 16, 2018 1:35 PM
  • Same here:

    Exchange 2010 SP3 UR22 on Windows Server 2008 R2 SP1 (both with all Patches from July 2018). Transport Service stops responding, reboot of Cas-Server helps to solve the problem and mailflow (Inbound mail from smtp smart host to cas-Server) is working again for some hours. Didn't uninstall KB4338818 until now, but if someone from MS confirmes, I will...

    • Edited by J. Juergen Tuesday, July 17, 2018 8:07 AM
    Monday, July 16, 2018 1:36 PM
  • Yes - this was our issue as well this morning. Thanks!
    Monday, July 16, 2018 4:48 PM
  • I don't have Microsoft Support contract ....... can anyone raise with Microsoft to get a fix or v2 patch. 

    I still cannot uninstall the Secuirty update ... will update when I find a fix. 

    Monday, July 16, 2018 5:22 PM
  • I see a post on the REDDIT thread from a user who had IPv6 disabled on the NIC but still listed in his connectors. He was able to get his server running again by removing the IPv6 references from his connectors and leaving kb:4338818 installed.

    I have not tested this myself. I had already removed kb:4338818.

    If there is no V2 patch I may try this in a few days. I don;t want to run unpatched too long.

    Monday, July 16, 2018 6:35 PM
  • Only Apply the fix  and everything is gonna be alright.

    Here I have applied already and I have no problem so far.

    • Proposed as answer by Joseph__Moody Monday, July 23, 2018 7:17 PM
    Wednesday, July 18, 2018 7:30 PM
  • Still no update from Microsoft .... only solution is to uninstall the patch ..... Microsoft have not even confirmed  the issue !

    Thursday, July 26, 2018 10:33 PM
  • We suffered problems two days after install KB4338818 and KB4338823, one month ago, in Windows2008 R2 with SQL Reporting Service 2008. We sufered issues with Services that consume this report server with intermittent error like "System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted" This issue occurres in two different farm. We applied two, days ago, KB4345459 and kb4338821 and seems issues was solved. Someone find this error?

    Víctor Sesmero

    Wednesday, November 21, 2018 2:34 PM