Patch List for May 14, 2024

Topic

New Reply

We’re still in testing mode for this month’s updates. So far there has been an acknowledged deployment issue whereby Windows Server 2019/KB5037765 may
[See the full post at: Patch List for May 14, 2024]

Susan Bradley Patch Lady/Prudent patcher

6 users thanked author for this post.

abbodi86, Karen H., Lars220, Alex5723, bowled845, lmacri

Reply | Quote

Replies

Also encountering an issue where KB5037765 is not showing as being applicable to Windows Server 2019 x64 when deployed from Configuration Manager. The KB appeared to be updated yesterday as it was re-sync’d just after 7PM CST but has not resulted in a positive change so far.

Reply | Quote

Anecdotally, there have been 3 PC’s in my office that have the new lock screen widgets where the lock screen has “crashed”. 2 out of 3 times, the lock screen is totally blank, can’t be unlocked, and a hard reboot is required. One time, the user was given an error message and the lock screen reloaded itself.

More typical untested Microsoft garbage rolling out. I miss the days when Microsoft actually had in-house testing instead of relying on the general public to be beta testers.

2 users thanked author for this post.

jrp2706, arbrich

Reply | Quote

Links to block it coming in Monday’s newsletter.  Do you have any sort of customization?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Hello Susan,

I followed your advice to update Office 2019 (in Win 10 22H2). I had updates blocked since May 26, 2023. It took quite a while to download, but installation was fast. When I opened Word to edit a file, it opened but I was blocked from editing. I went to the MS website and followed the instructions to get Word out of protected mode: File, Options, Trust Center, Trust Center Settings, Protected View, then unchecked the three options under Protected View, and clicked OK.

Nothing has changed, I still can’t edit my exsisting Word files. It is almost as if the Office updates is putting every file I open into Protected View, and keeping it there even when I haveProtected View turned off.

I created totaly new test file, and I could do what I wanted with it, but when I went to save it , Microsoft asked me to Sign in and type the email of the account I would like to use to open the document. Then I saw it tried to direct me to OneDrive. I don’t have a OneDrive account (and don’t really want one), so I selected This PC. I re-opend the test file and it allowed me to edit it once I save it.

Then I saved it again in File, Save as, with a new filename. I closed, then opened the new file and now I couldn’t edit it anymore, but I could print it. I went back to Trust center Protected view, and all three boxes are unchecked. Then I went into the Info screen for the file, and looked into Protect Document. I couldn’t change it from the Always Open Read-Only choice.

I did a quick check of an Excel file and it seem to be working normally. I could create, modify and save the file. Although when I went to save it, it also tried to direct me to OneDrive. So I selected This PC again. Everything seems to be normal with Excel. All the existing Excel files I opened also seem to work fine.

Can you tell me what I need to do to be able to open, edit and save my existing Word 2019 files?

Thanks  you for all the things you do for us AskWoody members.

Reply | Quote

KS wrote:
Anecdotally, there have been 3 PC’s in my office that have the new lock screen widgets where the lock screen has “crashed”. 2 out of 3 times, the lock screen is totally blank, can’t be unlocked, and a hard reboot is required.

Yes, confirmed, saw this today on an up-to-date Win11 Pro box: totally blank lock screen, unable to unlock, hard shutdown/reboot was used to regain access to box.

And unfortunately that’s not the only problem we seem to be having. After updates were applied to above box, the existing “Lock screen status” setting was annoyingly overridden and reset to “Weather and more” (as expected, sadly)… so “Lock screen status” setting was then manually reset to preferred setting “None of this garbage” (yes, abbreviated as “None” on drop-down menu), BUT SETTING DID NOT HOLD – “Lock screen status” setting was _again_ overridden and reset back to “Weather and more”.

Worse yet, this same repeated override of manually reset “Lock screen status” setting back to “Weather and more” has been observed on multiple other (up-to-date Win11 Pro) boxes.

So we appear to have an unreliable feature, a feature we do not need, a feature we do not want enabled – combined with an unreliable setting that at present doesn’t seem to allow the feature to be reliably/permanently disabled… great combo, thanks Microsoft!

1 user thanked author for this post.

jrp2706

Reply | Quote

Looking forward to those instructions on how to block those lock screen ‘widgets’ on Windows 11: totally don’t need widgets on my PC.

Reply | Quote

We keep running into issues with  5037771.

System Ends up booting to a BLACK screen and can do nothing. Both Dell Optiplex SFF desktops. Both Windows 11 22H2. End up spending hours trying to fix, hide the patch,  SFC/scannow, until finally we can get it going and block that patch.  We are in the middle of another one right now again. Very frustrating how bad testing at Microsoft has become.

Reply | Quote

DAdams wrote:

Also encountering an issue where KB5037765 is not showing as being applicable to Windows Server 2019 x64 when deployed from Configuration Manager. The KB appeared to be updated yesterday as it was re-sync’d just after 7PM CST but has not resulted in a positive change so far.

AVOID the KB5037765 update AT ALL COSTS! It is a faulty & broken update and fails to install on most Server 2019 AND Windows 10 LTSC 2019 systems!

Microsoft has recently posted an out-of-band update [KB5039705] on Thursday May 23 to resolve the issues found with the KB5037765 update:
https://support.microsoft.com/help/5039705
https://www.catalog.update.microsoft.com/Search.aspx?q=kb5039705

for those using Server 2019 & LTSC 2019: install KB5039705 instead of KB5037765

Reply | Quote

Was unable to install the May Cumulative update (KB5037771) on my 23H2 Win 11 Pro Geekom Mini PC. The install error said KB5037771 failed to install. The event log showed a failure to install KB5037771 with an error code of 0x800f081f. Since this was a repeat of the same problem I experienced with the March 2024 cumulative update, I made the decision skip excessive troubleshooting and did a Win 11 repair install using the Win 11 23H2 iso. Afterwards, KB5037771 installed without issues.

Reply | Quote

EP wrote:

for those using Server 2019 & LTSC 2019: install KB5039705 instead of KB5037765

from Born’s Tech & Windows World blog – Windows Server 2019 OOB update KB5039705: Fails on Citrix with error 0x8007371B

Reply | Quote

Updated my daily driver (MinisForum UM790Pro) and “canary” (DellXPS8920) last evening.
Only problem was it stalling and requiring 2 reboots on both machines. But it worked and I am not showing any adverse effects.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote