If you could provide the output of the attempt to install the "not applicable" KB3173424, I/we would get an error message, which tells a little more than just "not applicable".
In the case I currently think about, this test might also fix the problem of wsusou finding KB3172729 over and over again.
The update with the ID KB3172729 internally contains two MSU files:
- windows8.1-kb3173424-x64_9a1c9e0082978d92abee71f2cfed5e0f4b6ce85c.msu (Servicing Stack 6.3.9600.18384)
- windows8.1-kb3172729-x64_e8003822a7ef4705cbb65623b72fd3cec73fe222.msu (SecureBoot dbx update)
Both of them need to be installed for the Windows Update Agent to detect KB3172729 to be installed, even if the KB3172729 MSU actually is installed.
http://www.catalog.update.microsoft.com/Search.aspx?q=kb3172729%2C%20server%202012%20r2As the system most likely alread has a newer Servicing Stack update applied, Windows Update will refuse to install the older one. But because of MS doing strange things sometimes Windows Update will still list KB3172729 as KB3173424 (the older Servicing Stack) is not installed.
I want you to install KB3173424 using DISM as this bypasses the version check done by the Windows Update Agent and install an older Servicing Stack update, even if a newer one is installed (don't worry, the older one will just be copied to the component cache and be registeres as installed; it will
not overwrite newer files).
If this fixes the issue, we could implement a function into wsusou, which will prevent this from happening.
Wer Rechtschreibfehler findet, darf sie behalten oder an den Meistbietenden versteigern. / Everybody finding a misspelling is allowed to keep or sell it.
aker
WSUS Offline Update „Community Edition“
https://gitlab.com/wsusoffline/wsusoffline/-/releases