Patch Lady – KB 4088875 issue acknowledged

Topic

New Reply

Microsoft has officially acknowledged the issue Woody pointed to yesterday. In the release notes of KB 4088875 this is now listed:   new Ethernet
[See the full post at: Patch Lady – KB 4088875 issue acknowledged]

Susan Bradley Patch Lady/Prudent patcher

4 users thanked author for this post.

Elly, cesmart4125, woody, abbodi86

Reply | Quote

Replies

I didn’t receive KB 4088875 .  Does anyone know why?

Thanks in advance for your help with this.

Win 7 SP1, Office 2010 SP2, Intel Core 2 Duo T7100, 4 GB RAM

Reply | Quote

Microsoft seems to be purposely blacklisting KB4088875 from appearing in Windows Update for some users.

3 users thanked author for this post.

Elly, woody, walker

Reply | Quote

That would lead me to conjecture that, not only does MS know what the problem is, but they can identify potentially afflicted machines using current telemetry.

Reply | Quote

I haven’t gotten it either.  Is it for Win 7 only?  If so, it makes me wonder why.

Being 20 something in the 70's was much more fun than being 70 something in the 20's.

Reply | Quote

indeed, no KB4088875 update for all my Win7 SP1 PCs lately.
I’ll just wait for a newer update to replace it.

Reply | Quote

Upon info from Thiersee abd tested my myself, KB4088875 will not show until you installed latest two Preview Rollups KB4075211 & KB4091290

if you use WUMT and check “Include superseded” it will be shown directly

2 users thanked author for this post.

Elly, MrBrian

Reply | Quote

Someone at Microsoft just sent me a message, pointing to the fix shown here:

Symptoms

A new Ethernet virtual Network Interface Card (vNIC) may be created with default settings in place of the previously existing vNIC, causing network issues. Any custom settings on the previous vNIC are still persisted in the registry but unused.

Resolution

To fix this issue, run the VBS script that’s provided below. Copy and paste this in notepad and save with .vbs extension.

Instructions

Before you run the script, make sure that you back up the following registry key and subkeys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI

This script can be run on physical or virtual computers:

1. Immediately prior to installing the Convenience Rollup.
   Or
2. Immediately after installing the Convenience Rollup but prior to restarting the following patch install.
   Or
3. After installing Convenience Rollup 3125574 and restarting even though the computer is in problem state. In this case, another restart will be required after executing the script.

Following is the script:

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 

 

Thanks, technical01010.

1 user thanked author for this post.

Elly

Reply | Quote

@Woody. Why do people message you replies to forum posts rather than posting themselves? It doesn’t require creating an account.

Reply | Quote

Over the years I’ve had several reasons for posting comments that are sent to me.

Think of it as anonymous posting with an extra layer of anonymity. 🙂

Reply | Quote

I thin I’m slowly going mad:  The following WU’s just popped up on reboot:

KB4088875, (the famous IP/card killer) after being absent for 3 days, KB091290, KB2952664 (telemetry), KB890830 (malicious software removal tool)…

..I’m going to lie down, now…later do a backup/mirror image of the whole drive using Terabyte’s Image for DOS (IFD) and await further instructions from the IT Gurus here.  This nonsense could give one a total freak out.

From here it looks like 8875 causes problems, 1290 fixes them.

Wouldn’t it just be easier not to install 8875 in the first place? Or have they fixed it? 400MB of updates; insane.

Win7ProSP1X64x86 and counting down to Ubuntu…

 

Edited for HTML. Please Copy/Paste using the text tab.

Win7 Pro SP1 64-bit, Dell Latitude E6330, Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Greenhorn
--
"Windows Update? Bah! I could carve a better ecosystem out of a banana!" -Jamrach Holobom

Reply | Quote

Perhaps you meant KB4091290 instead of KB091290? As far as I know, KB4088875 hasn’t been fixed yet. Hopefully a fix will be issued this week.

1 user thanked author for this post.

walker

Reply | Quote

Btw, this update breaks not only 2008 machines but 2012 servers as well. In fact the VBS script does nothing to help these machines.

Reply | Quote