Hotfix KB4099950 to fix lost network settings after KB4088878 and/or KB4088875 on Windows 7 SP1 and/or Windows Server 2008 R2 SP1.
Does not apply to:
Windows Server 2008 R2 SP1 + KB3125574
Windows 7 SP1 + KB3125574
// Since it was the first item on the known issues section. You would already have remedied the problem.
Applies to:
Windows Server 2008 R2 SP1 + KB2775511
Windows 7 SP1 + KB2775511
Windows Server 2008 R2 SP1
Windows 7 SP1
If you had installed the March 2018 security updates (KB4088878 & KB4088875) and lost network settings on Windows 7 SP1 and/or Windows Server 2008 R2 SP1. And if you looking for a fix, here it is.
4099950 Network Interface Card settings can be replaced, or static IP address settings can be lost
https://support.microsoft.com/?id=4099950
Note: It needs to be installed before KB4088875 and/or KB4088878 are installed.
Update: If for some reason you still haven’t installed the March 2018 Security updates, resynchronize WSUS after 2:00 p.m. Pacific (GMT-8) today (4/3/2018) which will force KB4099950 before KB4088875 and/or KB4088878 are installed.
Q: What about my Windows Server 2008 SP2 based systems?
A: If pci.sys version is older than 6.0.6002.22567, you will need to set the registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\Pci
HackFlags (DWORD) 0x00040000 (Hex)
*Note, if there’s a HackFlags value there already, make sure you OR the values instead of overwriting it."
i.e.
· If HackFlags doesn’t exit:
Value: 0x00040000
· If HackFlags does exits
New Value: (Existing Flags | 0x00040000)
Example: if existing value is 0x0000001, change value to (bitwise OR) 0x00040001
Source:
2710558 Network adapter teaming breaks after you install the hotfix that is described in KB article 2487376 or 2495300 in Windows Vista SP2 or in Windows Server 2008 SP2
Q: In April 2018 security updates, do we need to do anything else?
A: No, it (KB4099950) will be bundled with the April 2018 updates.
[Updated Apr. 10, 2018]
For Windows Server 2008 R2 SP1, download the April Security update 2018 (KB4099950) from the Windows Catalog.
https://www.catalog.update.microsoft.com/Search.aspx?q=4093118
[Updated Apr. 12, 2018 at 3:00 p.m. Pacific (UTC-8)]
For Windows Server 2008 R2 SP1, we have re-released the April 2018 Security hotfix KB4093118 which now includes KB4099950.
For more info about the April 2018 security hotfix:
April 10, 2018—KB4093118 (Monthly Rollup)
https://support.microsoft.com/en-us/help/4093118/windows-7-update-kb4093118
Yong
Comments
- Anonymous
April 12, 2018
"... will force KB4099950 before KB4088875 and/or KB4088878 are installed." - Is that definitely the case? Is there a way to verify that from WSUS? There is no sign of KB4099950 or a revision to either KB4088875 or KB4088878 in WSUS... is there something I'm missing?- Anonymous
April 12, 2018
@JamesAf First install KB4099950 from the "Windows Update Catalog, not to be confused with "Windows Update" or "WSUS" or "WSUS integrated w/ SCCM) from https://www.catalog.update.microsoft.com/Search.aspx?q=4099950.- Anonymous
April 12, 2018
So if I'm deploying updates to a large estate via SCCM and WSUS - I would need to download KB4099950 from the Microsoft Update Catalog and import it to WSUS?- Anonymous
April 12, 2018
@jamesaf, that is correct at the moment.
- Anonymous
- Anonymous
- Anonymous
- Anonymous
April 12, 2018
I noticed I need to push KB3125574 out to some devices yet. Will pushing KB4099950 before pushing KB3125574 resolve the NIC issues that could occur? Or do I need to run the script instead of KB4099950?- Anonymous
April 12, 2018
@ffej23. If you install KB4099950 from the “Windows Update Catalog, not to be confused with “Windows Update” or “WSUS” or “WSUS integrated w/ SCCM) from https://www.catalog.update.microsoft.com/Search.aspx?q=4099950 before installing KB3125574, you will be good to go and not have to run the script mentioned in KB3125574.
- Anonymous