none
KB4103718 causing NIC Disconnection and on Windows 7 SP1 and Windows Server 2008 R2. Also Bug check 7B issue on Windows Server 2008 R2

    Question

  • Team,

    KB4103718 is installed on our multiple clients Windows 7 SP1 and Windows Server 2008 R2 systems and it is causing NIC Disconnection issue. Additionally, on some Windows Server 2008 R2,  this patch fails and after reboot it gives Bug check error 7B.

    Can you please provide us assistance on this on priority.


    Thursday, May 10, 2018 12:43 PM

Answers

  • Hi,

    KB4103718 still clarified that it would affect the network interface controller after this update. I'm sorry to tell you that the known issue is likely to persist. There's no clear clarification from official. I'll trace it, if any update, I'll post here.

    Highly appreciate your effort and time. Nice day!

    Best regards,

    Michael 


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Sunday, June 3, 2018 8:30 AM

All replies

  • Hi

    Thanks for your question.

    Due to this update KB4103718 currently comes on this month, there aren’t much feedback and cases so that we couldn’t troubleshoot this issue affected NIC disconnection. I’d suggest you uninstall this update and rollback previous system state to see if it could be resolved.

    Furthermore, as for the servers 2008R2 those got the bug check code 7B, we could try the following article to see if it works.

    System stopping with a BugCheck code 7B (INACCESSIBLE_BOOT_DEVICE)

    https://blogs.technet.microsoft.com/noboot/2017/10/02/system-stopping-with-a-bugcheck-code-7b-inaccessible_boot_device/

    How to troubleshoot the stop error 0x0000007B?

    https://blogs.technet.microsoft.com/asksbs/2008/03/29/how-to-troubleshoot-the-stop-error-0x0000007b/

    Reference link:

    https://support.microsoft.com/en-us/help/4103718/windows-7-update-kb4103718

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

    Hope above information can help you.

    Highly appreciate your successive effort and time. If you have any questions and concerns, please feel free to let me know.

    Have a nice day!

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com



    Friday, May 11, 2018 2:44 AM
  • Thank you for the response.

    For NIC Disconnection issue, there more than 5000 client's Windows 7 systems affected.


    Friday, May 11, 2018 10:03 AM
  • What is your approach to solving this? System restore point, reinstalling NIC drivers after update, or have you found something scripted to help?
    Friday, May 11, 2018 4:01 PM
  • Our client's approach is either uninstall the Patch before rebooting or Reinstalling NIC Drivers after update and reboot.
    Friday, May 11, 2018 5:04 PM
  • Hi - currently experiencing same issue in regards to server 2008 receivning 0x0000007b error on boot. Have you had any luck on repairing this?
    Saturday, May 12, 2018 1:43 AM
  • Microsoft has acknowledged that Network driver are getting intentionally uninstalled after installing this May Update for their some customer and they are investigating the cause of this issue.

    For details check: https://support.microsoft.com/en-us/help/4103718/windows-7-update-kb4103718

    • Proposed as answer by Jin Chen Monday, May 14, 2018 5:32 AM
    Sunday, May 13, 2018 10:36 AM
  • Hi,

    I'll consult official that if it could be resolved. Thanks for your sharing solution as it would be helpful to others.

    Highly appreciate your effort and time. If there is anything else we can do for you, please feel free to post in the forum.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, May 14, 2018 5:37 AM
  • This is the 3rd month in a row that the monthly update has caused NIC disappearance, downtime, and $$$.  When is Microsoft going to provide an update on how to prevent this from happening next month when the monthly rollup goes out???
    Monday, May 14, 2018 1:28 PM
  • in my case it failed to install 6 times with non-descriptive useless "Code 1" , and coincidentally wifi nic can't connect to 5G wifi without any logical technical explanation - just "couldn't" and that's it , while ton of other devices could, but is still able to connect to 2.4G wifi..
    Wednesday, May 16, 2018 3:05 AM
  • Hi,

     we are also facing the following error when we try to install the May month windows update on windows server 2008R2.

    >>

    018-05-23           01:45:49:838     1132      62c        COMAPI              -------------

    2018-05-23        01:45:49:838     1132      62c        COMAPI              -- START --  COMAPI: Install [ClientId = wusa]

    2018-05-23        01:45:49:838     1132      62c        COMAPI              ---------

    2018-05-23        01:45:49:838     1132      62c        COMAPI                - Allow source prompts: Yes; Forced: No; Force quiet: No

    2018-05-23        01:45:49:838     1132      62c        COMAPI                - Updates in request: 1

    2018-05-23        01:45:49:838     1132      62c        COMAPI               - ServiceID = {261E2284-7508-4691-9E21-0CC763B72B10} Third party service

    2018-05-23        01:45:49:838     1132      62c        COMAPI                - Updates to install = 1

    2018-05-23        01:45:49:838     1132      62c        COMAPI              <<-- SUBMITTED -- COMAPI: Install [ClientId = wusa]

    2018-05-23        01:45:49:838     720       818        Agent    *************

    2018-05-23        01:45:49:838     720       818        Agent    ** START **  Agent: Installing updates [CallerId = wusa]

    2018-05-23        01:45:49:838     720       818        Agent    *********

    2018-05-23        01:45:49:838     720       818        Agent      * Updates to install = 1

    2018-05-23        01:45:49:838     720       818        Agent      *   Title = Security Update for Windows (KB4103718)

    2018-05-23        01:45:49:838     720       818        Agent      *   UpdateId = {6D4E4854-06D0-4BE0-B56E-EED9EE1BB70F}.501

    2018-05-23        01:45:49:838     720       818        Agent      *     Bundles 2 updates:

    2018-05-23        01:45:49:838     720       818        Agent      *       {F8C55D76-CAD1-4BFC-9ABC-F24065CC3409}.501

    2018-05-23        01:45:49:838     720       818        Agent      *       {C84D2990-1308-4209-BB1A-FC6EAB1DD63F}.501

    2018-05-23        01:45:50:385     720       818        Agent    WARNING: failed to calculate prior restore point time with error 0x80070002; setting restore point

    2018-05-23        01:45:50:385     720       818        Agent    WARNING: LoadLibrary failed for srclient.dll with hr:8007007e

    2018-05-23        01:45:50:385     720       818        Handler Attempting to create remote handler process as PM-3\Unisys in session 1

    2018-05-23        01:45:50:416     720       818        DnldMgr             Preparing update for install, updateId = {F8C55D76-CAD1-4BFC-9ABC-F24065CC3409}.501.

    2018-05-23        01:45:50:416     2076      82c        Misc      ===========  Logging initialized (build: 7.5.7601.17514, tz: -0700)  ===========

    2018-05-23        01:45:50:416     2076      82c        Misc        = Process: C:\Windows\system32\wuauclt.exe

    2018-05-23        01:45:50:416     2076      82c        Misc        = Module: C:\Windows\system32\wuaueng.dll

    2018-05-23        01:45:50:416     2076      82c        Handler :::::::::::::

    2018-05-23        01:45:50:416     2076      82c        Handler :: START ::  Handler: Command Line Install

    2018-05-23        01:45:50:416     2076      82c        Handler :::::::::

    2018-05-23        01:45:50:416     2076      82c        Handler   : Updates to install = 1

    2018-05-23        01:45:50:448     2076      82c        Handler   : WARNING: Command line install completed. Return code = 0x00000001, Result = Failed, Reboot required = false

    2018-05-23        01:45:50:448     2076      82c        Handler   : WARNING: Exit code = 0x8024200B

    2018-05-23        01:45:50:448     2076      82c        Handler :::::::::

    2018-05-23        01:45:50:448     2076      82c        Handler ::  END  ::  Handler: Command Line Install

    2018-05-23        01:45:50:448     2076      82c        Handler :::::::::::::

    <<<<

    Could you please help us in solving this problem. Any suggestions.

    Thanks- Kiran

    Wednesday, May 23, 2018 11:30 AM
  • Hi Michael,

    Today, I have checked support URL for KB4103718 (https://support.microsoft.com/en-us/help/4103718/windows-7-update-kb4103718) and found Microsoft has now removed Known issue  which was initially Acknowledged for Network Drivers Uninstallation after installing the update. They have removed it without any update on the support URL for this issue.

    Need confirmation, whether Microsoft has  fixed this issue or not?

    Can you please confirm this with your officials?


    Friday, May 25, 2018 9:02 AM
  • Hi,

    KB4103718 still clarified that it would affect the network interface controller after this update. I'm sorry to tell you that the known issue is likely to persist. There's no clear clarification from official. I'll trace it, if any update, I'll post here.

    Highly appreciate your effort and time. Nice day!

    Best regards,

    Michael 


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Sunday, June 3, 2018 8:30 AM