Master Patch List as of October 11, 2022

Topic

New Reply

#PatchTuesday I’ve updated the Master Patch List for yesterday’s releases I’ll be keeping an eye out for issues and will be updating that page and spr
[See the full post at: Master Patch List as of October 11, 2022]

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

abbodi86, lmacri, CAS

Reply | Quote

Replies

My WSUS server just notified me that August’s KB5012170, the problematic secure boot update that breaks Bitlocker encryption has been re-issued (a day after the rest of the updates). Not sure if this one fixes the previous reboot problem, I’m certainly not going to roll it out to any of our fleet until I hear more feedback.

No matter where you go, there you are.

Reply | Quote

Adobe Acrobat DC update latest version is corrupt and will not install.  Adobe aware and working on new patch

Reply | Quote

I can’t find any reference to this. Do you have a link?

Reply | Quote

Update worked fine for me and with no issues. Now on version 2022.003.20258.

Reply | Quote

Please provide a link if possible. It also failed in our case.

Reply | Quote

Perhaps it’s an issue caused by declining a desktop shortcut?

Problems with patching to version 22.003.20258

It’s not broken for everyone.

Reply | Quote

Thank you. That’s exactly what we are seeing.

1 user thanked author for this post.

b

Reply | Quote

I updated 21H2 yesterday without incident. Everything working jut fine. Now on 21h2 (OS Build 19044.2130).

Peace, CAS

1 user thanked author for this post.

deuxbits

Reply | Quote

Yesterday Windows Update automatically updated my Windows 10 21H2 machine to OS Build 19044.2130. Normally I defer and install updates following the AskWoody DefCon system, but this time I either forgot to pause the updates or Windows decided to ignore the pause. Whatever the case, I have not noticed any problems.

1 user thanked author for this post.

deuxbits

Reply | Quote

Small correction for NET CORE

Reply | Quote

I’ve now patched six Win 10 Pro 21H2 machines with KB5018410 (4 test, 2 live). Also three of those with Office 2016 C2R updated to 2209, and one Office 2013 Pro to 15.0.5493.1000 and have not seen any issues yet. (We don’t use Outlook nor Exchange.)

As always, YMMV.

Thanks to everyone else who reports this info on this thread. It allows me the confidence to go ahead and test, then if it seems safe, begin to deploy.

Basic research is what I am doing when I don't know what I am doing - Werner Von Braun

Reply | Quote