forums.wsusoffline.net

Hi,

I'm having a patch (KB4056898) which is not being applied and from the logs in doesn't even try which means that I must be using wrong parameters.
This is what MS writes about the update: https://support.microsoft.com/en-us/hel ... -kb4056898

I can see that /all and /sec_only affects the same variable in the doupdate.cmd but I cannot figure out if exact what they are used for?
and if those 2 affects any other kind of updates?

Hope someone can explain this

Best Regards
Updater1

Does WSUS Offline say at some point that it's missing some update? If not, maybe this update is already installed.

Regards
Dalai

Remeber that the SecOnly-patches are not requiered, if the full rollups are applied.

Also: The updates between 2018-01 and 2018-04 require the QualityCompat-value to be set. (.\client\opt\QualityCompat.reg)

Correct. My guess is that the WOU developer did remove the entire QualityCompat feature when I wrote that MS has discontinued the practice. However, for SecOnly, WOU must still unconditionally set that key, or the affected SecOnly packages are not applicable. That's because MS never bothered to re-release them, they still bear that dependency.

Hi All,

Nope, it doesn't state it as missing, it doesn't even appear in the logfiles and it seems that it's because that KB is a security only patch.

I haven't been able to find it in any rollup's, so if any of you know which rollup includes the KB4056898 please let me know.

I still haven't figured out what exactly /SEC_ONLY and /ALL are used for?

Regards
Updater1

The /SecOnly parameter tells wsusou not to install the cumulative rollups for Windows 7 / 8.1, but instead use the Security-only ones.
If not used, wsusou will install the cumulative ones.

The /all parameter tells wsusou, to ignore installed updates and try to reinstall them.

If you want to check, if you need KB4056898, please post the version of C:\Windows\system32\ntoskrnl.exe here and someone of us will tell you, if the update ist required or not.

Hi.

boco wrote:Correct. My guess is that the WOU developer did remove the entire QualityCompat feature when I wrote that MS has discontinued the practice. However, for SecOnly, WOU must still unconditionally set that key, or the affected SecOnly packages are not applicable. That's because MS never bothered to re-release them, they still bear that dependency.

Correct.
I removed the warning after your posting.
WOU did never set this value automatically.

Cheers
Torsten

Updater1 wrote:[...] and it seems that it's because that KB is a security only patch.

Yes, it is, but that doesn't really matter.

I haven't been able to find it in any rollup's, so if any of you know which rollup includes the KB4056898 please let me know.

All security fixes that are contained in the security-only update packages are also included in the rollup packages of the same month. In this particular case, the rollup package of 2018-01 (January 2018), KB4056895.

If you think you need this sec-only update, see if the QualityCompat registry value is present (see file wsusoffline\client\opt\QualityCompat.reg for the registry path). However, see aker's answer above; maybe the kernel version is already up-to-date.

Regards
Dalai

Hi,

I am fully aware that the security updates should be included in either the same month rollup package or the following, but where can I check if it's really there?
I can't find anywhere where it states which individual updates are included in a given monthly rollup

/Henrik

That's really easy: each monthly rollup replaces/includes all rollups /SecOnly-updates released before (rollups are cumulative).
So if you got the 2018-02 cumulative rollup, you won't need any patches released in the time from 10-2016 up to 2018-01 and don't need the 2018-02 SecOnly-update.

if I'm understanding something wrong, please tell me, what exactly you want to check. The Spectre-vulnerability? Something else? If you want to see a CVE-list, you have to check this in the TechNet security bulletin (I can't post the link from my mobile phone, but add it here as soon as I'm back home this afternoon/evening).