Solved Has Microsoft pulled July 2018 Security Rollup for Win7 (X86)?

[Batch]

On 11th July (using non-auto Windows Update) I downloaded and installed "2018-07 Security Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4338818)" amongst others. All seemed fine.

Yesterday I had occasion to restore (a system image) to just before the update.

Now, when Windows Update runs it does not offer me this update. It still offers me (as it did originally) a 2018-07 Security Monthly Quality Rollup for .NET, Malicious Software removal tool plus a Defender Update (as well as .NET 4.7.2. which I'm not interested in).

But it does offer me "2018-06 Preview of Monthly Quality Rollup for Windows 7 for x86-based Systems (KB4284842)"

So have Microsoft pulled KB4338818 (at least for Win7x86)? I can't see any specific evidence of them having done so.

However I do note what MS state at https://support.microsoft.com/en-gb/help/4338818/windows-7-update-kb4338818 under Known Issues. Is that the explanation (for it, seemingly, being pulled)?

 

[Snick]

Hi Batch,
I don't believe they have, here's link to M$ catalog KB4338818, it's listed at bottom of page, updated 7/13/18.
Nic

 

[Batch]

Thanks for the reply Snick. I get what you are saying, but still makes me wonder if they've pulled it from being available thru Windows Update, but still left it available for download.

I'm tempted to download the .msu and try running it standalone (as I can just restore an image again afterwards it goes belly up). I notice that all the downloads at that catalog have a "pciclearstalecache" .exe as well as the .msu - does that need to be run as well (before / after)?

 

[poolmon]

I was offered both updates you mentioned last week (along with 3 Office Updates) but did not install any. This weekend the first two updates no longer appeared and only the Office ones did, which I installed. The first 2 are still missing but 2 different ones now show, KB2952664 (an old tracking update) and malicious software removal.

I've had this happen before and when it did the missing updates eventually showed up. Don't know if this is the case now or not, but they remain missing on my computer.

 

[Snick]

Where did you locate info? I presume you extracted the .exe and .msu from the KB.

I notice that all the downloads at that catalog have a  "pciclearstalecache" .exe as well as the .msu - does that need to be run  as well (before / after)?

As I indicated in my previous post the date is 7/13/18 on the M$ catalog update list. M$ most likely reissued it, usually that's the case when they botch it the first time.

Regarding pciclearstatlecache.exe the KB applies the PCIClearStaleCache.exe file. This cleans up the adapter entries within the cache that lead to errors. If it's included in the KB I'd just run the installer, .exe and all, and I believe the .exe executes prior to the .msu install.

Here's a tool SIW2 recommended on another thread for installing updates etc. Most of the documentation is in Chinese, however the GUI is pretty straight forward. You don't need ADK or any of it's tool installed.

Dism++ | New Windows Utility

Nic

 

[ProactiveSvcs]

According to a poster on the PatchManagement mailing list, Microsoft have pulled this update from Windows Update detection because it caused BSODs on some systems under certain networking conditions. They intend to reissue it "mid-July".

 

[Snick]

Well there's the answer to the WU question. That further confirms the M$ catalog with 7/14/18 date.

 

[Batch]

Thanks for all the replies. Just checked again and still no sign of the re-issued KB4338818 being available thru Windows Update. Not critical for me at this time as is only affecting my standby lappie, so will bide my time for now. My main PC (also Win7x86) updated OK in the first place (before KB4338818 pulled and I haven't had cause to do a restore to prior to the updates, so it is working fine (and I have an image after the updates now anyhow).

Snick: The .exe and the .msu (and only those) are available as separate downloads from the Download dialogue that opens up when one clicks the Download button in catalog link that you included with your first reply. No need to "extract" from anything.


More generally, I find it frustrating / irritating (plus other words / phrases I shall not mention) that MS are so pitifully poor at communicating what they are doing (in this case in respect of pulling / re-issuing updates). And I pity the poor sods that are getting BSODs and haven't a clue what to do.

 

[Batch]

MS has re-released the update today. Now installed and seemingly working fine.

Thanks to all for your input.

 

[poolmon]

MS has re-released the update today. Now installed and seemingly working fine.

Thanks to all for your input.

I think they may have just pulled it again. I saw it reappear when you did but I did not install it then. It's now gone again, so they could still have an issue . .

 

[PCMDX]

Still showing

It's still showing up, along with the other referenced updates, as of today's date.

We do updates to hundreds of PCs of various brands, models, OS. The June and July 2018 Security Roll Ups have caused some systems to not boot normal (or at all) after install. The only recourse is to do a System Restore prior to the installation.

Impacted so far have been HP 8000 Windows 7 Pro (32-bit) with 100% failure, some NCR PC (Win7 Pro 32-bit).

I'm finding nothing from Microsoft, or other forums, or the Event Log to explain the reason for failure.

 

[poolmon]

This update resurfaced for a third time on two different WIN 7 64 bit desktop computers after disappearing twice as an Important Update.

I just installed it on both (now that we are at the end of the month) and hopefully any latent issues have been addressed.