Page 2 of 2

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 19.03.2018, 21:07
by mekschr
When I told you there were no hidden updates, the pc was closed already I opened it to check, so restarting can't be the solution, Where should I search for those hidden updates ?

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 20.03.2018, 05:37
by aker
Please run "regedit" and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat.
Please check, if this key exists and a REG_DWORD named "cadca5fe-87d3-4b96-b7fb-a231484277cc" and the value 0 exists.

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 20.03.2018, 07:45
by mekschr
Read the post again, What I meant by Quality Key was that cadca5fe-87d3-4b96-b7fb-a231484277cc thing, Its value is 0.

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 20.03.2018, 09:38
by boco
Check if the Windows Update itself has them installed. It tends to do this on Automatic.

Also, no idea if this month's Previews are already out, but keep in mind that those supersede the main Rollups, too, since they are essentially early versions of next month's Rollup packages.

Other than that, I'm out of ideas.

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 20.03.2018, 10:23
by mekschr
After writing this post at first, When I opened Windows Update and made a check, It wanted me to Install 2017-12 Monthly Rollup, after installing it and rebooting it told me to install 2018-2 Rollup, Why does it want me to install older updates ?

Anyways, Thanks alot to you all for trying to help me, Much Appreciated.

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 20.03.2018, 13:56
by boco
Usually the Rollup packages are fully cumulative, that means, every new one relaces ALL older ones (currently from Oct. 2017 which was the first).

If now the latest one from March is hidden (or Windows thinks it is hidden), or if it is otherwise inapplicable (that's the case for systems without the QualityCompat key/value), Windows Update will offer the next older one from the chain your system fulfills requirements for.

If the QualityCompat key/value is missing, that is 2017-12 (the last one that did NOT require that value to be present). If the one from March is assumed to be hidden, then it's the next older one from February.

So, the behavior of WU is at least halfway logical, although the reason it offered both in sequence is not. The causes of the behavior is unknown.

You could try to reset WU, that will make it forget anything that was hidden.
1. Stop the Windows Update Service.
2. Delete (or rename) the SoftwareDistribution subdirectory that's inside the WINDOWS directory.
3. Start the Windows Update Service.

Now WU is squeaky-clean and will hopefully act sane, again.

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 21.03.2018, 20:50
by mekschr
Yay, renaming/seleting "SoftwareDistribution" folder fixed it, and now I can install KB4088875 with no problems, Thank you all for helping me, Much Appreciated.

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 22.03.2018, 01:22
by AsokAsus
Apparently by default, WSUSofflineupdate is hiding KB4088875, but KB4088875 is not actually a security-only update, but is the actually the full rollup update, which WSUSofflineupdate isn't supposed to be installing anyway.

It is KB4088878 that's the security-only update associated with the KB4088875 rollup, and I'm actually wondering if WSUSofflineupdate was meant to hide KB4088878.

BOTH updates are EXTREMELY buggy and problematic as stated by Microsoft themselves at:


Furthermore, Woody Leonhard claims at ComputerWorld that while KB4088875 is still listed as "Important", but is now unchecked
so it won't install automatically:

I really wonder if WSUSofflineupdate should automatically exclude installing KB4088878 until Microsoft gets their act together ...

Re: Problem with KB4088875 *2018-3-W7X86SecurityRollup"

PostPosted: 22.03.2018, 03:05
by Dalai
Not sure whether or not you're aware of this: Monthly Rollups must be hidden if SecOnly packages are to be installed because the Rollups supersede the SecOnly updates. So yes, it's correct that WSUS Offline hides KB4088875 when the /seconly switch is given. Otherwise it wouldn't be able to install KB4088878. Your statement about WSUS Offline hiding KB4088875 by default is only true in case that the /seconly switch is specified.

Hiding the SecOnly updates doesn't make sense because they're neither to be installed by default (via Windows Update) nor would it change anything; the WUA would still select the same updates for installation (minus the single hidden update of course).

Whether or not updates are buggy or cause (serious) issues may be relevant to the user, but in the end it doesn't always matter for WSUS Offline on a larger scale. If you don't want WSUS Offline to install specific updates, you can add them to its exclude list. Adding to that: it's always a good idea to wait a couple of days or even weeks before installing new Windows updates. And it's also always a really good idea to have a working backup/image of your system (hardware can always fail at any time).

Conclusion: I don't see anything that could or should be changed in WSUS Offline, but maybe that's just me.