none
march 2018 Windows Update removes Virtual Network adapter, creates new default one

    שאלה

  • Good morning,  Not sure if this is the best forum to ask, but couldn't really see anything specific for windows updates.

    We have just had a bunch of our DMZ servers go offline.  What is happening is that when the March 2018 updates applied and the machine rebooted it deleted the primary network adapter and created a new default one.  This of course had no default settings for IP address or gateway etc.  I did find that there was a previously known issue with Virtual Environment and network cards as per the following.

    https://blogs.vmware.com/apps/2016/06/rush-post-microsoft-convenience-update-and-vmware-vmxnet3-incompatibilities.html

    This seems to be exactly the same issue as we have just experienced.  Is it that the March 2018 update contains the previous updates that caused this issue, and if so why has it not been resolved since reported back in 2016.

    Is anyone else experiencing the same issue?  Is there a way to mitigate the problem?  All our machines have VMXnet3 cards and we will not want to manually reconfigure all of our Servers network adapters again.

    Thanks in advance.

    יום רביעי 14 מרץ 2018 11:55

כל התגובות

  • Hi,

    Having the same problem, looks like it is caused by kb4088878. Only 2008R2 servers affected.
    Looking forward to hearing from MS regarding this.

    Thanks.

    יום רביעי 14 מרץ 2018 12:13
  • We have same problem on more than 30 Windows Server 2008 R2 servers.

    After reboot the oldest adapter was activated without TCP/IP settings instead the latest adapter that has correct TCP/IP settings:


    יום רביעי 14 מרץ 2018 12:21
  • Hi,

    Having the same problem. Only 2008R2 servers affected.
    Also looking forward to hearing from MS regarding this.

    Thanks.
    יום רביעי 14 מרץ 2018 12:33
  • Hi,

    Having the same problem, looks like it is caused 2018-03 Security Monthly Quality Rollup, KB4088875. Only 2008R2 servers and Windows 7 Professional affected.
    Im waiting news
    Regards
    יום רביעי 14 מרץ 2018 12:59
  • I had the same happen.  I have raised a support call with Microsoft: Support request

    118031417809579

    יום רביעי 14 מרץ 2018 13:04
  • It's not just the vNIC that is affected.

    From a conversation I just had with VMware, it apparently resets the PCI bus which winds up re-enumerating some of the virtual adapters. Some of the devices come up fine, others don't

    A couple of the systems I have, have multiple drives on multiple luns running paravirtualization interface got re-hashed as well as the NICs. As such the MS SAN policy wouldn't let the drive come on automatically, had to go in and 'Online' the specific volumes in question and then rebooted to assure it stayed up. I will need to go in and disable that specific policy during my next maintenance window so if the volumes get re-hashed again I don't have to worry about them coming online properly.

    -GP

    יום רביעי 14 מרץ 2018 14:35
  • This happened to all of our clients as well, I believe this also affected our Server 2012 servers and not just 2008. We had to go through the physical NICs and reset all drivers manually.

    • נערך על-ידי GROOVYJOSHCLARK יום רביעי 14 מרץ 2018 16:19
    יום רביעי 14 מרץ 2018 14:44
  • Same here, also see the problem
    יום רביעי 14 מרץ 2018 14:58
  • only VMware affected or also HyperV?

    • נערך על-ידי MirandaVeracruz יום רביעי 14 מרץ 2018 15:34
    יום רביעי 14 מרץ 2018 15:34
  • Confirming that we are seeing this issue with KB4088875 with VMWARE Win7 Clients.
    יום רביעי 14 מרץ 2018 16:19
  • Just curious if anyone is seeing issues with "KB4088876" since it is the 2012 rollup?
    יום רביעי 14 מרץ 2018 16:41
  • I have seen no reports of 2012 having issue.  Just 2008 R2 and Windows 7.  We were able to recreate the problem easily enough.  It is definitely 88878 or 88875 causing problem. 
    יום רביעי 14 מרץ 2018 17:04
  • I had this issue today.  Here's what I know from 2 different servers running 2008.

    Server Motherboards  - Intel S5520HC and S5500HCV

    Both servers network card drivers were gone.

    Windows update history showed:

    KB4056564, KB4087398, KB4089187, KB4089229, KB4089344, KB4089175, KB4090450

    I reinstalled network drivers and set the static IPs back to correct settings and all was fine.

    Hope this helps someone.

    יום רביעי 14 מרץ 2018 17:57
  • Same issue. 10+ 2008 R2 physical servers with dual network interfaces.  The interface we were using was disabled and the interface that we weren't was enabled. Had to reverse this and re-enter static IP info. This affected software that was bound to the interface as well.

    I wrote earlier about having issues with 2012, but I think this was unrelated.  I just updated a different 2012 server manually and I haven't seen any issues.

    • נערך על-ידי Javitzso יום רביעי 14 מרץ 2018 19:14
    יום רביעי 14 מרץ 2018 18:47
  • Glenn,

    Are you facing the problem only with server 2008 (32 and 64 bit) also ? Based on the blog it seems everyone is facing the problem only with server 2008 R2, can you please confirm.

    יום חמישי 15 מרץ 2018 06:14
  • Same issue on our Vmware VM's .

    Why isn't microsoft responding / doing a rollback on this update?


    יום חמישי 15 מרץ 2018 07:42
  • Is this a regression??

    My WSUS is even beeingb rebooted as I type!

    Gr...

    יום חמישי 15 מרץ 2018 07:55
  • Hi,
    Microsoft product team is working on the issue actively. 
    No ETA can be offered for now, but we will keep eyes on tracking the issue closely, if there is further significant update on this issue, we will update you ASAP accordingly.
    Best regards, 
    Wendy

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

    יום חמישי 15 מרץ 2018 07:57
    מנחה דיון
  • Microsoft confirmed they are getting Network Connectivity Issues post installation of these KB 4088875 and 4088878 patches. A new Ethernet virtual Network Interface Card (vNIC) may be created with default settings in place of the previously existing vNIC, causing network issues after applying this update. Any custom settings on the previous vNIC are still persisted in the registry but unused.IP address settings are lost after applying this update.

    They recommended not to install these two patches until the permanent resolution is rolled out by MS.

    Microsoft is actively working on a resolution and will provide an update in an upcoming release.
    No ETA can be offered for now, but we will keep eyes on tracking the issue closely, if there is further significant update on this issue, it will be updates ASAP.

    Hope this will help everyone. Please remember to mark the replies as answers if they help.

    יום חמישי 15 מרץ 2018 10:00
  • Could you please share with us the link we find the Microsoft confirmation, thank you.
    יום חמישי 15 מרץ 2018 10:28
  • Please see the following.  (Note known issue 1)

    https://support.microsoft.com/en-us/help/3125574/convenience-rollup-update-for-windows-7-sp1-and-windows-server-2008-r2

    and

    https://blogs.vmware.com/apps/2016/06/rush-post-microsoft-convenience-update-and-vmware-vmxnet3-incompatibilities.html

    We have found that the script from Known issue 1 must be run from local machine to take effect.  I have rolled out a package from SCCM applied to all our 2008R2 servers and windows 7 Workstations. Hopefully this will mitigate the issue.

    Hope that helps.

    • הוצע כתשובה על-ידי neildotwilliams יום חמישי 15 מרץ 2018 10:58
    יום חמישי 15 מרץ 2018 10:43
  • Don't know if this is the right place, but we are experiencing a same issue on desktops (not virtual) with Windows 7. The following network adapters seem to be having their network adapters removed. Unable to perform a rollback of the driver, because it is gone.

    Affected NIC's:
    Intel 82579LM Gigabit
    Intel 82578DM Gigabit
    Intel I219-LM

    Found an event under Event viewer > Applications and Services Logs > Microsoft > Wired-AutoConfig > Operational with the ID 15513:

    A network adapter was removed from the system. Network Adapter: Intel(R) 82578DM Gigabit Network Connection Interface GUID: \DEVICE\GUID


    יום חמישי 15 מרץ 2018 10:54
  • VBS deployed and seems to be working for us also.
    יום חמישי 15 מרץ 2018 10:57
  • server 2008 64 same same.

    יום חמישי 15 מרץ 2018 11:22
  • We are having issues, several Window's 7 PC's being affected but not all, none of the servers have been affected yet

    (Were a IT Support company so cover thousands of PC's and Servers)

    Microsoft keeping me in a job again....

    יום חמישי 15 מרץ 2018 11:30
  • We have also encountered this on server 2008, and windows 7 but not virtual. We installed on sample systems so not affected a great deal as yet.  But the 1 device was 11 miles away!

    • נערך על-ידי Neville Chilton יום חמישי 15 מרץ 2018 12:02
    יום חמישי 15 מרץ 2018 12:02
  • i had the same problem around 50 + server window 2008 R2 enterprise Lost IP after this KB4088875 . New adaptor assigned with no IP and we dont have dhcp enabled so server went offline.

    Aany solution so far ?? as of i manually assigned the ip with local accounts.

    • הוצע כתשובה על-ידי Hemant.Deep יום חמישי 15 מרץ 2018 14:20
    יום חמישי 15 מרץ 2018 14:04
  • as of now just  2008 R2 and Windows 7.
    יום חמישי 15 מרץ 2018 14:13
  • Hi Lumia,

    Please Do below for your issue  :-

    Remove Hidden Network Devices

    Configure the IP on new Adapter [VMNET3 if Virtual]

    Accept the change while configuring the network adapter IPs

    That's it

    Enjoy , You server will be live and no need to reboot.

    

    • הוצע כתשובה על-ידי Hemant.Deep יום חמישי 15 מרץ 2018 14:15
    יום חמישי 15 מרץ 2018 14:14
  • Thanks Hemant. 
    יום חמישי 15 מרץ 2018 14:19
  • Uninstalled the updates.

    Rebuilt the network.

    Rebooted. OK. Rebooted again and back to FUBAR,

    Keep testing.

    יום חמישי 15 מרץ 2018 14:31
  • lol - I m manually re-ip-addressing and Enterprise network -- 110 vms went down. #fk
    יום שישי 16 מרץ 2018 05:20
  •  As such the MS SAN policy wouldn't let the drive come on automatically, had to go in and 'Online' the specific volumes in question and then rebooted to assure it stayed up. I will need to go in and disable that specific policy during my next maintenance window so if the volumes get re-hashed again I don't have to worry about them coming online properly.

    -GP

    sanpolicy=onlineall may be appropriate for your environment.
    יום שישי 16 מרץ 2018 16:13
  • Add me to the list.  I had a 2008 R2 VM that I patched today and had the exact same problem.  I am supposed to patch production this weekend and I have put the brakes on until this is resolved..
    יום שישי 16 מרץ 2018 17:02
  • I have the same issue on physical and virtual 2008 R2 servers. I also got a blue screen caused by ntoskrnl.exe (Bug Check String: SESSION_HAS_VALID_POOL_ON_EXIT) on my physical 2008 R2 Terminal server in 36 hours after March 2018 updates had been installed. The server has new version of ntoskrnl.exe 6.1.7601.24059. The server was very stable before March 2018 updates. MS makes havoc.
    יום שישי 16 מרץ 2018 22:20
  • MS officially acknowledged the issue in the update:

    https://support.microsoft.com/en-us/help/4088875/windows-7-update-kb4088875


    • נערך על-ידי Andrej Trusevic שבת 17 מרץ 2018 11:12 bad link
    שבת 17 מרץ 2018 11:11
  • Why hasn't Microsoft pulled 4088875 from WSUS until it is fixed? And also, what was the point of the "preview" 4072511 release last month (in February), which didn't have this issue? Isn't that the whole point of the preview releases, to make sure $#@% like this doesn't happen?

    I have an account with Microsoft Premier Support via my day job, and they are getting an earful from me on this failure.

    • נערך על-ידי __Jim__ שבת 17 מרץ 2018 22:54 context
    שבת 17 מרץ 2018 22:24
  • This is the 2nd (or is it 3rd?) time MS has done this over the last few years, where it's effectively killed my box. I was going to Thank MS for forcing me to move to 2016 - which I did, but there were so many problems with lack of performance as compared with 2008 on the same old hardware, I can't explain it. So, that's one weekend gone. I rolled back to a previous image prior to these updates (and all is well again and fast performance) and just won't apply any until all of this is all resolved. Or, perhaps until I have time to setup a spare box to see why performance was so bad for 2016 (and I do have 2016 on a VM for a while - for other purposes, and its been fine).

    Edit; FWIW, I use DriveSnapshot for backup/restore. The smallest nicest backup app that just works - and saved me many times.


    • נערך על-ידי mahacker יום ראשון 18 מרץ 2018 09:23
    יום ראשון 18 מרץ 2018 08:42
  • Just curious if anyone is seeing issues with "KB4088876" since it is the 2012 rollup?
    I've had this issue on Windows Server 2012 R2 Clusters (KB4088876). All NIC config was wiped out and the vbs script provided by MS didn't fix it. Removing and addind new vNICs didn't work either as the config details were still in the OS. Tried removing ghost devices in Device Manager but no joy.

    What worked was  manually removing the vNIC config in the OS based on the GUID and re-configuring the networks.
    Remember to disable the Cluster Service before doing all this.

    The registry keys are below.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\ {4D36E972-E325-11CE-BFC1-08002BE10318}
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Adapters
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces

    Hope this helps.

    -TheBatman-
    יום שני 19 מרץ 2018 04:03
  • Probably worth mentioning that this isn't just happening on Server / VM's or Virtual NICs. This update has entirely removed the network adapter on our Dell Optiplex 7010's. We caught two stations that got the updates early and thankfully we deployed the network driver installer remotely to machines that didn't lose network connectivity yet. We're expecting about 60-80 workstations to lose network connectivity in the next day or so.


    • נערך על-ידי Not Hagedoorn יום שני 19 מרץ 2018 13:17
    יום שני 19 מרץ 2018 13:16
  • I had the same issue on two physical 2008 R2, SP2 servers, exactly the same updates were installed
    KB4056564, KB4087398, KB4089187, KB4089229, KB4089344, KB4089175, KB4090450

    Seems NIC drivers were installed with the updates and my previously statically set NIC was found to be on DHCP. Changing it manually prompted a "an inactive NIC already has this IP address..." to which I just accepted the settings and resolved the issue. Luckily only two machines.

    Neither the KB4088875 or KB4088878 updates were installed. I've opened a ticket with Microsoft.


    • נערך על-ידי MajorChew יום שני 19 מרץ 2018 14:47
    יום שני 19 מרץ 2018 14:38
  • We applied KB4088876 to several VMWare 2012 R2 servers on Friday with no issues.  Didn't know about the potential problem until this morning.  Dodged a bullet, I guess.  

    יום שני 19 מרץ 2018 16:17
  • Probably worth mentioning that this isn't just happening on Server / VM's or Virtual NICs. This update has entirely removed the network adapter on our Dell Optiplex 7010's. We caught two stations that got the updates early and thankfully we deployed the network driver installer remotely to machines that didn't lose network connectivity yet. We're expecting about 60-80 workstations to lose network connectivity in the next day or so.



    I also received a report this morning regarding ~ 13 physical Windows 7 computers having their secondary NIC settings wiped out and needing to be re-configured. That was from a sample size of 247, so not common. The updates were tested on a group of the computers beforehand, but since none of them lost their primary NIC settings, the issue wasn't detected.
    יום שני 19 מרץ 2018 17:36
  • We note that affected vmxnet adapters with default names. If adapters were renamed it still working after reboot.
    יום שלישי 20 מרץ 2018 07:14
  • I had this issue as well.  We are very careful to check for existing issues prior to updating our servers, but unfortunately I didn't see any blogs or announcements from Microsoft before we sent this out to all of our servers on 3/15, and our test round didn't raise any flags.  We wound up having to reconfigure the static IP settings on over 200 servers.  Fun!

    יום שלישי 20 מרץ 2018 15:52
  • ...I also got a blue screen caused by ntoskrnl.exe (Bug Check String: SESSION_HAS_VALID_POOL_ON_EXIT) on my physical 2008 R2 Terminal server in 36 hours after March 2018 updates had been installed...

    My 2008 R2 remote desktop servers also started blue screening with SESSION_HAS_VALID_POOL_ON_EXIT after installing the March updates.  I don't see this listed in the known issues section of the patch notes, but Microsoft has acknowledged it in the Server 2008 version of the patch. (KB4089344)

    I don't think this is caused by ntoskrnl.exe.  I think the problem file is Win32k.sys.

    יום שלישי 20 מרץ 2018 18:20
  • I can confirm that both update KB4088875 as KB4088878 cause the same network issues.  :(

    Posted an article about this on my own site to spread the news...
    http://www.ictstuff.info/no-network-after-installing-kb4088875-on-windows-2008-r2-or-windows-7/

    -\O_o/-

    יום שלישי 20 מרץ 2018 20:23
  • Same issue here.

    SESSION_HAS_VALID_POOL_ON_EXIT and rebooting numerous times during the day.

    Am uninstalling now.  

    יום שלישי 20 מרץ 2018 22:42
  • Have also had the joy of this latest security update feature from MS.

    Luckly all VMs and all running DHCP so got new IP addreses, only alerted by the polling software that was looking for servers on different IP addresses.

    Time to accelerate the retirement of 2008 R2 ;-)

    יום רביעי 21 מרץ 2018 07:33
  • I think Microsoft should fix that immediately !

    Windows server 2008 R2 is used in many environments and it's the most popular ms server OS.

    We need urgently the security march patches for server 2008 R2 !

    Sincerely I don't understand MS, it seems it's more focused on consumers people rather than on professional environments.... and that's very bad.

    If this is the new MS we'll replace all our servers with Linux !

    Regards

    יום רביעי 21 מרץ 2018 10:36
  • How easy or difficult is it to UN-install these KB4088875 and KB4088878 updates??

    Or should I restore to an older backup, then not allow these two updates to be installed?? (this is our current plan)

    We have the SESSION_HAS_VALID_POOL_ON_EXIT and rebooting numerous times during the day issue on four XenApp servers.

    Thank you, Tom


    • נערך על-ידי tlyczko2 יום רביעי 21 מרץ 2018 14:49
    יום רביעי 21 מרץ 2018 14:48
  • What I found about SESSION_HAS_VALID_POOL_ON_EXIT at

    https://support.microsoft.com/en-us/help/4089344/security-update-for-vulnerabilities-in-windows-server-2008

    KB4089344 March 13, 2018

    After you install this security update, you may receive a Stop error message that resembles the following when you log off the computer:

    SESSION_HAS_VALID_POOL_ON_EXIT (ab)

    To work around this issue, disable the Desktop Window Manager. To do this, type the following commands at an elevated command prompt:

    sc config uxsms start= disabled
    sc stop uxsms

    I have not tested yet this solution

    יום רביעי 21 מרץ 2018 17:50
  • Hi all, would installing KB3125574 and KB4088878 together will resolve the issue for u all ? 

    https://support.microsoft.com/en-sg/help/3125574/convenience-rollup-update-for-windows-7-sp1-and-windows-server-2008-r2



    • נערך על-ידי DoranHolic יום חמישי 22 מרץ 2018 08:05
    יום חמישי 22 מרץ 2018 07:54
  • Yep a lot of my 2008 R2 servers took a dump and went to "DHCP", I have done  CMD ==>

    "set devmgr_show_nonpresent_devices=1" then go in to device manager and show hidden devices. remove any greyed out ones. also i had the experience that even after i reconfigured the NIC cards after a reboot the gateway disappeared again and had to set that once more. 

    I have also been having Terminal Servers crashing with the  SESSION_HAS_VALID_POOL_ON_EXIT

    I used this still monitoring.... 

    The following commands can be executed in an administrative command prompt:

    sc config uxsms start= disabled
    sc stop uxsms

    יום חמישי 22 מרץ 2018 13:56
  • Hi, have you got anywhere with this as the exact same issue has happened to me, 2 physical servers on server 2008 r2

    Cheers

    יום חמישי 22 מרץ 2018 16:21
  • Yep a lot of my 2008 R2 servers took a dump and went to "DHCP", I have done  CMD ==>

    "set devmgr_show_nonpresent_devices=1" then go in to device manager and show hidden devices. remove any greyed out ones. also i had the experience that even after i reconfigured the NIC cards after a reboot the gateway disappeared again and had to set that once more. 

    I have also been having Terminal Servers crashing with the  SESSION_HAS_VALID_POOL_ON_EXIT

    I used this still monitoring.... 

    The following commands can be executed in an administrative command prompt:

    sc config uxsms start= disabled
    sc stop uxsms


    Anyone had luck with this? I saw that same instruction - to disable uxsms service for the 2008 non-R2 version. I’ve tried this on 2008 R2 Citrix servers and it doesn’t seem to help, had several BSODs today with “SESSION_HAS_VALID_POOL_ON_EXIT”.
    יום חמישי 22 מרץ 2018 23:41
  • We initially thought that this issue only affects virtual 2008 r2 servers but I'm seeing a lot of people report that their physical servers are also having this issue.

    We've separated our physical and virtual 2008 servers into two different patching schedules, we plan to patch our physical servers first as we believed that the physical servers were unaffected but this may be futile. 

    I can see that a few people have had the issues on their physical 2008's, can anyone else confirm if they've had this issue with physical boxes?

    יום שישי 23 מרץ 2018 10:45
  • Thanks MS , this patch should be pulled immediately until rectified , imagine large enterprises that dont tightly control IPs ..... 
    יום שישי 23 מרץ 2018 14:38
  • Did you get an answer from Microsoft? I have a VM server that only has KB4089187 installed and after a reboot, the IP changed to 169.x.x.x even though the static IP was still in the NIC properties.
    יום שישי 23 מרץ 2018 14:50
  •  As such the MS SAN policy wouldn't let the drive come on automatically, had to go in and 'Online' the specific volumes in question and then rebooted to assure it stayed up. I will need to go in and disable that specific policy during my next maintenance window so if the volumes get re-hashed again I don't have to worry about them coming online properly.

    -GP

    sanpolicy=onlineall may be appropriate for your environment.

    It's what I ran.

    Was just trying to point out that other virtual interfaces were affected. In this particular case the paravirtualization drive controller.

    If you look through the eventlogs it looks like the pci bus was reset like when you drop a new motherboard into to replace a failed one only not quite so severe. Had some confirmation from VMware support when this first cropped up to that affect as well.

    -GP

    יום שישי 23 מרץ 2018 16:53
  • I have applies the solution

    sc config uxsms start= disabled
    sc stop uxsms

    on my patched physical Windows 2008 R2 remote desktop server but still have SESSION_HAS_VALID_POOL_ON_EXIT blue screen about once a week.

    יום שישי 23 מרץ 2018 22:14
  • Same, literally just had had it happen 4 term servers 2 are acting better than others.
    יום שני 26 מרץ 2018 13:29
  • I have reported an issue to Microsoft that I am having on physical 2008 boxes NOT R2, after installing the following patches it creates new copies of any NIC's that are installed and sets them all to DHCP

    KB4056564

    KB4073011

    KB4087398

    KB4089175

    KB4089229

    KB4089344

    KB4090450

    The response from MS is that no such issue has been reported with these patches (which isnt true as I have reported it to them) and tbh i dont hold out much hope as they have emailed since saying they wont be doing any root cause analysis but they are a break fix team. Putting the ip address back in gets the server back up and running so no need for me to run scripts and install other updates........

    יום שלישי 27 מרץ 2018 07:56
  • Had the same issue on an SBS 2008, quickest solution I found not knowing what had caused it was to uninstall the recent March Updates, which got the system working again.

    Next step is to work out which update(s) are causing it.

    I have so far narrowed it down to:
    KB4089229, 4089344, 4089453 or 4090450

    as the system connected again once these were uninstalled.

    Would be good to know which actually causes the issue so I can reinstall the others.



    Willie

    יום שלישי 27 מרץ 2018 11:49
  • Hi,

    Same issue here with a RDS.

    Your server is still having same amount of blue screen? Or is it less often ?

    יום רביעי 28 מרץ 2018 09:19
  • Is there a fix for this? I am getting BSOD 2-3 times daily. Can I uninstall all updates from 3/14 and have the server run fine again?
    יום רביעי 28 מרץ 2018 14:52
  • Did uninstalling fix the reboots?
    יום רביעי 28 מרץ 2018 14:53
  • Hi,

    I uninstalled every update quoted in the first msg and still get BSOD ..

    יום חמישי 29 מרץ 2018 07:41
  • I found a fix for this problem :

    First create a VSB file with the following code 

    Option Explicit
    Const HKEY_LOCAL_MACHINE = &H80000002
    Dim oReg : Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv")
    Dim oShell : Set oShell = CreateObject("WScript.Shell")
    Dim sPath, aSub, sKey, aSubToo, sKeyToo, dwValue, Result, SaveResult
    Dim NotDeleted
     
    NotDeleted = 0
     
    ' Get all keys within sPath
    sPath = "SYSTEM\CurrentControlSet\Enum\PCI"
    oReg.EnumKey HKEY_LOCAL_MACHINE, sPath, aSub
     
    ' Loop through each key
    For Each sKey In aSub
        ' Get all subkeys within the key 'sKey'
        oReg.EnumKey HKEY_LOCAL_MACHINE, sPath & "\" & sKey, aSubToo
        For Each sKeyToo In aSubToo
          Result = oReg.DeleteKey(HKEY_LOCAL_MACHINE, sPath & "\" & sKey & "\" & sKeyToo & "\" & "\Device Parameters" & "\SlotPersistentInfo")
          ' Allow failure only if key never existed
          If (Result = 1) Or (Result > 2) Then
            NotDeleted = 1
            SaveResult = Result
          End If
        Next
    Next
     
    If (NotDeleted > 0) Then 
      Wscript.Echo "One or more SlotPersistentInfo keys still exist under HKLM\System\CurrentControlSet\Enum\PCI\<deviceid>\<subdeviceid>\Device Parameters.  Please delete manually. Result = " & Result
    End If

    After running the script then run the updates 

    יום שישי 30 מרץ 2018 07:40
  • MS updated description of KB4088875 at https://support.microsoft.com/en-ca/help/4088875/windows-7-update-kb4088875

    They released fix for network adapter KB4099950 and fix for BSOD KB4099467.

    I see at my servers that KB4088875 was replaced with KB4100480

    https://support.microsoft.com/en-gb/help/4100480/windows-kernel-update-for-cve-2018-1038

    • הוצע כתשובה על-ידי TonyJPdx יום שני 02 אפריל 2018 21:33
    יום שני 02 אפריל 2018 16:46
  • The same happened to me on Server 2008, SP1. As server restarted after the installation of march 2018 updates, All the physical network card configuration goes to default settings. All communication with the Servers becomes inactive. To solve this issue follow the follow two methods 

    1. Just Uninstall the March Updates, Restart the Server. Most Probably previous configuration of the network reverted back to normal.

    2. Click Start, click Run, type cmd.exe, and then press ENTER.

    1. Type "set devmgr_show_nonpresent_devices=1", and then press ENTER.
    2. Type Start DEVMGMT.MSC, and then press ENTER.
    3. Click View, and then click Show Hidden Devices.
    4. Expand the Network Adapters tree.
    5. Right-click the dimmed network adapter, and then click Uninstall.
    6.  Rename the Adapter names and assign the IP Address

    יום שלישי 03 אפריל 2018 16:51
  • Any update on what you found? I am having a similar issue
    יום שלישי 03 אפריל 2018 20:10
  • Good morning,

    Same problem happened but only on vmware machines with 2008R2, vmxnet3 card and VM version 9.

    Same OS and network card with VM version 7, 8 and 11 had no problem with updates. 

    Hope this can help you all.

    Regards,

    יום חמישי 05 אפריל 2018 09:30
  • what is the ESXi Host version you have in your environment?

    Thanks..!!
    ~SG~

    יום שלישי 10 אפריל 2018 22:31
  • Do we know yet if this issue persists in the April CU?
    יום חמישי 12 אפריל 2018 14:56
  • It does persists, I believe !

    Windows 7 Pro did not have the March 23 preview installed; just had KB4093118 installed this week, and it knocked out ethernet connectivity via Realtek PCIE GBe family controller. DHCP conversation happens - it gets an IP and the nameservers okay, but logs a MAC address of 00:00:00:00:00:00 and in Windows the connection status is showing an empty "physical address" field.

    יום שישי 13 אפריל 2018 07:32
  • I took the plunge and applied the Apr Update and all others (apart from the Mar Update - KB4099950) and everything is Ok for my Win2008 (R2 SP1) server and my VMs (VMWare Workstation V12 Pro). I posted earlier about how the Mar Update broke these VMs for networking and I couldn't get it fixed (easily) so I reverted the box from a backup, and didn't apply any update, until now.

    If I get brave, I'll try to apply the Mar Update, but for now all is OK.

    *Edit (one week later). It doesn't even present me that update KB4099950 any more to even try to install any longer - perhaps all by design. So, all is working fine now.
    • נערך על-ידי mahacker יום ראשון 22 אפריל 2018 01:30 Edit
    שבת 14 אפריל 2018 02:56
  • Thank you for narrowing it down.  For our 2008 non-R2 systems, removing KB4089229 alone appears to have resolved the issue

      
    • הוצע כתשובה על-ידי ITBeast יום רביעי 13 יוני 2018 20:44
    יום שישי 20 אפריל 2018 12:10
  • Removing the KB4089229 patch from the Windows Update que worked with my HPC Windows Cluster that is compromised of Windows Server 2008 (NON R2) with the exception of one Windows Server 2008 R2 (The headnode). Thanks for posting this MGWhite.

    John M. Keller MCP (XP & 2003) | Security &#43; E-Mail : itbeast@msn.com


    • נערך על-ידי ITBeast יום רביעי 13 יוני 2018 20:49
    יום רביעי 13 יוני 2018 20:48