|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
WSUS – or Windows Server Update Services – is what many corporate/business patchers use to update machines. Larger firms use SCCM – System Center con
[See the full post at: Patch Lady – Not all patches make it to WSUS]
Susan Bradley Patch Lady/Prudent patcher
I called them “Seeker updates”. Updates that are installed only if you click on the “Check for updates” button. They are not installed automatically. “Seeker updates” do not appear in WSUS.
As far as I can tell, “Seeker updates” appeared for the first time in march. They replaced updates that had to be manually downloaded from the catalog.
Francis
My take would be that I have noticed sometimes in WSUS that not all patches for a particular issue or versions of Windows don’t always come out at the same time. Sometimes more show up the following day.
With the way things are running there now my guess is someone forgot to push these out. There’s no truth to the rumor that these shenanigans began after the state of Washington legalized marijuana. 🙂
Red Ruffnsore
You don’t have to approve and install if you synchronize, unless you use the default setting under which all Critical Updates are automatically applied. This is not common practice though.
Wait at least until the end of the week before approving new patches, especially for non-personal machines.
Yes, that is correct. The servicing stack needs to be installed before the CU. It contains the update for the updating mechanism.
Windows update does the SSU’s for you. You only need to worry about SSU’s if you
a. patch manually (i.e. go to the catalog site)
b. patch via WSUS/SCCM or other third party
Susan Bradley Patch Lady/Prudent patcher
Nope. The SSU silently gets installed. If you WU, the ONLY way you see that a SSU has been installed is doing a dism command. It does not show that the SSU has been installed via the gui “view update history”.
Don’t uninstall anything if you get your updates via Windows update. You are fine.
Susan Bradley Patch Lady/Prudent patcher
I’m not sure that KB 4103714 is actually going to uninstall. It’s been going for about 3 hrs. now and the bar is no further than it was.
I cancelled it. I guess the only way to do this is to go to my cloned drive from before the update and start all over again with a clean slate.
UPDATE: After cancelling the Uninstall window ( which just sat there not moving for over 3 hrs. ), I decided to run sfc /scannow and it said that there was a repair in progress and it needed a reboot. I rebooted and it evidently finished the Uninstall because I am now back to 16299.371.
There was no reboot called for after all that time, I guess your just supposed to guess when it’s ready for a reboot to Uninstall. MS sure has improved windows LOL.
Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).
The second update for Windows 10 in each month is the loose equivalent of the Preview updates for Windows 7/8.1 and their server variants.
This means that the second update is production ready (whatever that meaning is currently), but not mandatory.
The only difference may be that occasionally the Windows 10 “preview” contains security updates but this is not necessary a rule.
Most users here should be concerned with Windows Update only for their machines and not the multitude of the other options, except for analysis and debate.
It is all very fluid and it is not only Microsoft affected.
It seems that they all caught a disease called “cloud-itis”.
Susan – as a follower of yours for several years I can only say thank you for all your work in these trying times.
I’m not a business user, but your efforts over the years have spilled into our world of jousting with the Micrometer’s fiddling with our small biz users.
I’m glad to see you affiliated with Wood Land, and I hope that you and we will learn and serve to make the last years of W7 and it’s brethren a useful launching pad for a future that may in fact help us to still be online and actually spending our time and efforts in a useful way.
jimzdoats
If an administrator wants them you can manually import them from the catalog into WSUS BUTTTTTTTT make sure you also match up these updates with the corresponding Servicing stack update.
I’m simply not willing to go through all of this hassle. A person has to do WAY too much detective work just to properly keep up with it all. Either that, or simply cave to installing whatever updates Microsoft wants to feed to your computers.
Not to be repetitive, but my time would be far better spent in making Linux work than in keeping up with all of the Windows foolishness.
Hi
First post and un-lurking.
Reviewing the June updates today via AskWoody, I see on the referred ghacks post a need for a May servicing stack update (SSU). Which made me think, yup, probably not yet deployed within my WSUS server. I take the cautious route for only releasing security, rather than functional, updates so SSUs are classified within the “Updates” class.
I think Susan must have been thinking about this recently because via a search, this pretty much came within the first few results:
Seemingly didn’t get very far? If only WSUS had a regex filter… 🙂
I’ll just add a +me too because missing these SSUs is annoying and means you have to keep reading resources like here (thanks Team Woody) like a hawk.
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
