Replies

I believe that the best time to install KB 4099950 is immediately before installing KB4088878, without a reboot in between. If you’re willing to try again, uninstall KB 4099950, install KB 4099950 from the Catalog (do not reboot), then install KB4088878, then reboot.

4 users thanked author for this post.

HiFlyer, Elly, woody, ch100

The .msu contains the .exe. There is no need to do anything with the .exe.

2 users thanked author for this post.

TonyC, SueW

‘One question (slightly OT): Running .msu updates invokes the Standalone Installer. The first thing it does is go away for 5-6 minutes “Searching for updates on this computer” – even though I already clicked on the update to run. Then it asks me if I want to run the update I clicked on in the first place!?!? Anyone know why it does this?’

See my comments at Turn off Windows Update if you want to force-feed individual patches.

4 users thanked author for this post.

HiFlyer, Elly, LH, Kirsty

@Woody: Thank you for posting my questions :).

Could you please inform netwarrior20 that KB4099950 has in fact been missing from Windows Update since around April 17?

2 users thanked author for this post.

HiFlyer, woody

“At reboot, the registry key deleted is recreated because it is created anyway if missing, regardless of the patches. However, because now the version of pci.sys is above the known problematic version, the registry key is ignored and no longer creates problems.”

According to this netwarrior20 comment (my bolding), those registry keys still do serve a purpose:

“The script does indeed clear all the entries. This is to prepare the system for when the new pci.sys loads upon next boot.

Simultaneously on next boot after the cache is now properly read (that’s the fix) and no new adapter instantiated, the existing adapter is now re-cached. That’s what you’re seeing with the new entries. The purpose of the new cache entries is to prevent a new adapter from being instantiated should the MAC address on the existing instance change.“

2 users thanked author for this post.

jelson, Elly

“One thing that isn’t clear to me at all is if Total Meltdown can be run from Javascript or not.”

That’s an important question indeed. I don’t know offhand, and haven’t researched it much.

Perhaps there could be a new AskWoody Knowledge Base article created that accomplishes this.

1 user thanked author for this post.

geekdom

“What evidence exists that Group B gets less telemetry than Group A?”

I wonder much more traffic this site might get if more of its content were indexed by web search engines.

2 users thanked author for this post.

satrow, woody

Questions for netwarrior20:

3. Does Microsoft know that KB4099950 has been unavailable in Windows Update since approximately April 17?

4. Is Microsoft aware that the documentation for KB4088878 stating that KB4099950 is applied automatically when installing KB4088878 is incorrect?

1 user thanked author for this post.

Elly

Questions for netwarrior20:

1. For those that are experiencing either of the two networking issues introduced in the March 2018 Windows 7 updates, does uninstalling the problematic update(s) (and then rebooting) undo the issues a) never, b) sometimes, or c) always?

2. For those that are experiencing either of the two networking issues introduced in the March 2018 Windows 7 updates, what is your recommended procedure for fixing these issues, assuming that one has physical access to the affected computer?

1 user thanked author for this post.

Elly

1. Yes. After installing the Windows 7 March 2018 Windows monthly rollup, Windows 7 April 2018 Windows monthly rollup, or Windows 7 March 2018 security-only update, and then rebooting, the file pci.sys should be at the version listed in the file lists available at Windows 7 SP1 and Windows Server 2008 R2 SP1 update history.

2. Yes.

2 users thanked author for this post.

woody, jburk07

@jburk07: That is correct :).

After the first reboot after installing KB4093118 on Windows 7, the pci.sys version should end in 24056.

5 users thanked author for this post.

walker, SueW, HiFlyer, KarenS, jburk07

Installation of KB4093118 should run the equivalent of KB4099950 before KB4093118 installs. Thus the same logic holds.

I think so indeed.

3 users thanked author for this post.

HiFlyer, KarenS, jburk07