The patching showers of April

Topic

New Reply

Apple did their patching showers yesterday – another zero day fix 📱 iOS and iPadOS 15.7.5 – 2 bugs fixed 💻 macOS Monterey 12.6.5 – 1 bug fixed 💻 macOS
[See the full post at: The patching showers of April]

Susan Bradley Patch Lady/Prudent patcher

8 users thanked author for this post.

Pim, lmacri, jburk07, dglenn, fk5353, Alex5723, geekdom, abbodi86

Reply | Quote

Replies

AKB 2000003 has been updated for Group B Win7 and Win8.1 on April 11, 2023.

See #2551309 and #2551310 for information on Win7 and Win8.1 updates (Logged in Member access required).

4 users thanked author for this post.

Microfix, abbodi86, SueW, jburk07

Reply | Quote

Guinea Pig Update (10 moments of guinea pig fame)
Version and build after update: Win11Pro 22H2.22621.1555

WuMgr downloaded and installed:

• 2023-04 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5025239)
• Windows Malicious Software Removal Tool x64 – v5.112 (KB890830)

Installed without error and the system rebooted without error.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

6 users thanked author for this post.

Microfix, abbodi86, CAS, jburk07, Alex5723, fernlady

Reply | Quote

Microsoft Windows Security Updates April 2023: What you need to know before installation

.NET 6.0.16

.NET 7.0.5

Reply | Quote

The famous KB5012170 had been revised (binaries not changed)
now it’s advised to install the Servicing Stack Update (SSU) released March 14, 2023, or a later SSU update

https://support.microsoft.com/topic/kb5012170-security-update-for-secure-boot-dbx-72ff5eed-25b4-47c7-be28-c42bd211bb15

NOTE Improved diagnostics have been added to detect and report issue details through the event log. Please see KB5016061: Addressing vulnerable and revoked Boot Managers for more information.

2 users thanked author for this post.

geekdom, PKCano

Reply | Quote

Hardened Windows user. A & B sides of my dual boot PC got

KB5025239 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems as well as the malicious software remover.

No hiccups. Now running Windows 11 Pro (OS Build 22621.1555)

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

3 users thanked author for this post.

CAS, geekdom, fernlady

Reply | Quote

Win 10 Pro 22H2 x64. Updated without any issues. Now on 22H2 (OS Build 19048.2846).

Peace, CAS

1 user thanked author for this post.

TechTango

Reply | Quote

2023-04 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5025239)

2023-04 .NET 7.0.5 Security Update for x64 Client (KB5025916)

Windows Malicious Software Removal Tool x64 – v5.112 (KB890830)

All were installed without issues.

Now running Windows 11 Pro 22621.1555

--Joe

1 user thanked author for this post.

geekdom

Reply | Quote

abbodi86 wrote:

The famous KB5012170 had been revised (binaries not changed) now it’s advised to install the Servicing Stack Update (SSU) released March 14, 2023, or a later SSU update

The link you gave states for the Mar 14 SSU — Windows 10, version 20H2, 21H2, and 22H2 SSU (SSU installed from cumulative update KB5023696) … which I did.

MY Control panel History shows individual entries for prior SSUs but no evidence in March other than this statement. Confusing, but what’s new.

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / Opatch Pro / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

It’s mentioned in the article
it will be displayed in “Installed Updates”, not Update Histrory, as “Servicing Stack 10.0.19041.2664”, or later

3 users thanked author for this post.

deuxbits, WCHS, CraigS26

Reply | Quote

abbodi86 wrote:

it will be displayed in “Installed Updates”, not Update History, as “Servicing Stack 10.0.19041.2664”, or later

Today’s CU shows SSU .2780 for my Win 10 22H2 and I Think I read the March SSU line as 2/14 as the page spacing was so wide my focus took a nap. Thanks !

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / Opatch Pro / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

What should consumers know about Windows Local Admin Password Solution, if anything? I couldn’t decipher the referenced link at all.

1 user thanked author for this post.

fernlady

Reply | Quote

Nothing. It’s for business or education IT departments managing fleets of Windows workstations. The problem it solves is managing unique local admin passwords for tens, hundreds or thousands of PCs; for controlled reference when occasionally needed. It provides a means to avoid shared or simple passwords which would otherwise often get set up in practice.

ADDED:
It’s not available in Windows 10/11 Home anyway. Only Pro, Education and Enterprise.

3 users thanked author for this post.

deuxbits, WCHS, fernlady

Reply | Quote

I’ll discuss it in the newsletter.  In a business they tend to set up business computers with the same local admin password, this sets up a random password so that ransomware attackers can’t crack the one password and go like gangbusters across the network.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

deuxbits

Reply | Quote

It appears there may be an issue with the LAPS update in the April patch if you are currently using the Legacy LAPS MSI installer for a legacy LAPS implementation. There are reports of issues if the April security patch that includes the LAPS update is installed on a system and then the Legacy LAPS client is installed.

https://www.reddit.com/r/SCCM/comments/12jwvbp/psa_installing_laps_msi_after_aprils_updates/

https://twitter.com/brdpoker/status/1646229914142777344

Reply | Quote

This is one of those… well it makes sense issues. Pick one or the other and update your deployment documents.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

My April 2023 Microsoft update experience:
Firstly, imaged all systems prior to updates

Win10 Pro 22H2 x86 and 22H2 x64 (laptop and desktop)
April CU kb5025221 applied to each with no installation isues or faults reported within event viewer, sfc verification or dism checks.
Purged Winsxs folder of redundancy for good measure. Invoked an SSD manual TRIM on both systems once completed.
Computing on the edge but not using that browser, speaking of which, still hasn’t resurfaced. O&Oshutup had a couple of changes, restored ini configuration, sorted.

Win8.1 Pro x64 ESUB (Server 2012 R2 patching not EPOS)
kb5025285 patch applied without issue usual checks as per Win10 above which also displayed no problems.
Purged Winsxs folder and trimmed SSD, OS running slick.

Windows - commercial by definition and now function...

3 users thanked author for this post.

geekdom, Alex5723, abbodi86

Reply | Quote

Microfix wrote:

Purged Winsxs folder of redundancy for good measure.

How do you do that?

Reply | Quote

WCHS wrote:

How do you do that?

dism /online /cleanup-image /startcomponentcleanup /resetbase

It will run in two steps.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

2 users thanked author for this post.

geekdom, joep517

Reply | Quote

It never cleans as much as I would clean house if I were in charge.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

deuxbits

Reply | Quote

resetbase is disabled in Windows 10/11 by default

Did you enable “change” registry setting DisableResetbase?

abbodi86 wrote:

“ResetBase” is disabled in Windows 10/11 by default and has no effect

Reply | Quote

It seems that Enterprise LTSC 2019 is not getting KB5025229 (OS Build 17763.4252) via Windows Update

manual installation works fine
however, it cause “error about a source file not found” when trying to open Group Policy Editor

Reply | Quote

WCHS wrote:

Microfix wrote:

Purged Winsxs folder of redundancy for good measure.

How do you do that?

Checking current winsxs data usage :

Reply | Quote

Alex5723 wrote:

Checking current winsxs data usage :

I would like to have seen the PS window for the cleanup command, too — between the two AnalyzeComponentStore screenshots.

Reply | Quote

Windows 10 Pro 22H2 April updates.
All is well.

WinVer 19045.2846

2 users thanked author for this post.

deuxbits, geekdom

Reply | Quote

WCHS wrote:

I would like to have seen the PS window for the cleanup command, too — between the two AnalyzeComponentStore screenshots.

There is no report after cleanup command. Just the ======100%===== line.

Reply | Quote

@Alex5723, @WCHS wasn’t asking for the results report, he wanted to see the actual command you used to perform the cleanup; which neither of your screenshots provided.

@WCHS, since his screenshots don’t show exactly which one he used, here are all 3 variations of the cleanup command.

DISM /Online /Cleanup-Image /StartComponentCleanup
   (deletes previous versions of updated components)

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
   (also deletes superseded components & disables uninstall of those components)

DISM /Online /Cleanup-Image /SPSuperseded
(deletes components needed to remove service packs)

Even though the /ResetBase option is suppose to be disabled in Win10 & 11, I’ve always used the second one with no issues.

2 users thanked author for this post.

windbg, WCHS

Reply | Quote

Alex5723 wrote:

There is no report after cleanup command. Just the ======100%===== line.

I get this while it’s running:

I get this when it’s finished:

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

WCHS

Reply | Quote

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Image Version: 10.0.22621.1555

…

/Cleanup-Image /StartComponentCleanup [/ResetBase [/Defer]]
Use /StartComponentCleanup to clean up the superseded components and reduce the size of the component store. Use /ResetBase to reset the base of superseded components, which can further reduce the component store size.  Use /Defer with /ResetBase to defer long-running cleanup operations to the next automatic maintenance.

WARNING! The installed Windows Updates cannot be uninstalled after the
/StartComponentCleanup with /ResetBase operation is completed.

…

Also this  instruction set:

“This topic is about the different ways to reduce the size of the WinSxS folder on a running Windows 10, or later, installation.”

…

“Use the /ResetBase switch with the /StartComponentCleanup parameter

Using the /ResetBase parameter together with the /StartComponentCleanup parameter of DISM.exe on a running version of Windows 10 or later removes all superseded versions of every component in the component store.

From an elevated command prompt, run:
Windows Command Prompt

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

Warning

All existing update packages can’t be uninstalled after this command is completed, but this won’t block the uninstallation of future update packages.”

 

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

2 users thanked author for this post.

windbg, WCHS

Reply | Quote

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

WCHS

Reply | Quote

Hi Susan:

Windows Update successfully installed the following April 2023 Patch Tuesday updates on my Win 10 Pro v22H2 laptop and I haven’t noticed any negative effects so far:

• KB5025221: 2023-04 Cumulative Update for Win 10 Version 22H2 for x64 (OS Build 19045.2846)
• KB5025915: 2023-04 .NET 6.0.16 Update for x64 Client
• KB890830 : Windows Malicious Software Removal Tool x64 – v5.112

The update process went relatively smoothly this month. The progress message on the Windows Update GUI appeared to get stuck at “Downloading – 100%” for about 5 minutes before the “Install Now” button appeared (which often happens on my machine) but I just left it alone and eventually saw the “Restart Now” button once all updates had finished installing – see attached image.
—————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.2846 * Firefox v112.0.0 * Microsoft Defender v4.18.2303.8-1.1.20200.4 * Malwarebytes Premium v4.5.26.259-1.0.1976 * Macrium Reflect Free v8.0.7279

1 user thanked author for this post.

geekdom

Reply | Quote

lmacri wrote:

and eventually saw the “Restart Now” button once all updates had finished installing

Hi @lmacri ,
As I recall, you used to post that when you installed all of them together, you would get the “Restart now” in the midst of the installation, not after. So, now the appearance of “Restart now” is better behaved — i.e., after they all have finished installing?

Reply | Quote

WCHS wrote:

As I recall, you used to post that when you installed all of them together, you would get the “Restart now” in the midst of the installation, not after….

Hi WCHS:

That early “Restart Now” button only happens on my Win 10 Pro v22H2 machine if a MS .NET Framework 3.5, 4.8 and 4.8.1 update (which, like monthly Quality updates, also require a system restart to finish the installation) is offered with my other Patch Tuesday updates – see my 14-Nov-2022 post # 2497973 in November Updates Are Here and 24-Feb-2023 post # 2536955 in Here Comes February’s Valentines of Patches for sample images. There seems to be a race condition where my “Restart Now” button appears as soon as Windows Update has finished installing the MS .NET Framework update, even if my monthly Quality update hasn’t finished installing yet.

I won’t be surprised if my early “Restart Now” button returns the next time a MS .NET Framework 3.5, 4.8 and 4.8.1 update is released on a Patch Tuesday. Note that I have a Win 10 Pro OS and have configured Windows Update in my Local Group Policy Editor so that it does not offer Preview builds (i.e., Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received is ENABLED) so my system is only offered MS .NET Framework updates that include a security patch.

Last month several several Win 10 v22H2 users reported an unusual glitch where their “Restart Now” button never appeared after their their monthly Quality update KB5023696 finished installing – see arbbrich’s 14-Mar-2023 post # 2543539 in March Madness Here We Come for one example. I just wanted users affected by last month’s glitch to know that my April 2023 Patch Tuesday updates behaved “normally” for me this month.
—————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.2846 * Firefox v112.0.0 * Microsoft Defender v4.18.2303.8-1.1.20200.4 * Malwarebytes Premium v4.5.26.259-1.0.1976 * Macrium Reflect Free v8.0.7279

2 users thanked author for this post.

deuxbits, WCHS

Reply | Quote

I’ve also observed this premature/early restart when a .NET update is in the mix of updates.

And this month (April), several Win10 Pro 21H2 machines’ Settings->Update & Security->Windows Update panels exhibited the strange behavior of showing the update(s) available, downloading, then suddenly no longer reporting “installing” but instead reporting prematurely “You’re up to date” well before the cumulative update was done and a restart notification issued.

First time I saw it I thought I was mistaken about having seen the cumulative update briefly start installing. I thought maybe the cumulative update had failed?  I searched the update history, and the cumulative update was not present. Finally after some time, the restart notification showed up. And the cumulative update was done successfully.

I hypothesize this annoying update status/progress glitch is due to the new embedding of the Servicing Stack Update (SSU) in the cumulative update.

 

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

1 user thanked author for this post.

lmacri

Reply | Quote

When that happens, I have found that if I close the Settings App, then reopen it to Windows Update, things resume where they “left off” when it blinked out. It agains shows downloading and installing. That’s without doing anything else, like checking for updates, erc.

1 user thanked author for this post.

lmacri

Reply | Quote

Thank you PKCano. I’ve also found that close and reopen to work in the past. Did not work this time around….

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

Reply | Quote

PKCano wrote:

When that happens, I have found that if I close the Settings App, then reopen it to Windows Update, things resume where they “left off” when it blinked out.

Hi PKCano:

I’ve noticed something similar. If I hear my fan running at high speed on the day I’ve selected to install my Patch Tuesday updates, I will go to Settings | Update & Security | Windows Update just to monitor the progress of the updates, but as soon as I do that the download / installation progress monitor appears to come to a grinding halt, and I sometimes have to close and re-open that settings window (or even put my computer to sleep and then take it out of sleep mode) to get the progress monitor moving again.

I suspect this doesn’t always pause the actual Windows Update process, though.  During my March 2023 Patch Tuesday updates I recall I opened Task Manager and could see that there was still CPU and disk activity going on in the background for the Windows Update service host, even though the progress monitor indicated nothing was happening.
——————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.2846 * Firefox v112.0.0 * Microsoft Defender v4.18.2303.8-1.1.20200.4 * Malwarebytes Premium v4.5.26.259-1.0.1976 * Macrium Reflect Free v8.0.7279

Reply | Quote

deuxbits wrote:

And this month (April), several Win10 Pro 21H2 machines’ Settings->Update & Security->Windows Update panels exhibited the strange behavior of showing the update(s) available, downloading, then suddenly no longer reporting “installing” but instead reporting prematurely “You’re up to date” well before the cumulative update was done and a restart notification issued.

Hi deuxbits:

That’s interesting. Before reading your post I created a new thread today at Microsoft Office 2019 C2R Not Updating to report that my Microsoft Office Home and Business 2019 C2R Version 2302 / Build 16130.20332 (Current Channel) says “You’re up to date!” when I run a manual update check, even though I’m sure I’m a few versions behind. I wonder if the two problems are related.
—————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.2846 * Firefox v112.0.0 * Microsoft Defender v4.18.2303.8-1.1.20200.4 * Malwarebytes Premium v4.5.26.259-1.0.1976 * Macrium Reflect Free v8.0.7279

Reply | Quote

lmacri wrote:

… my Microsoft Office Home and Business 2019 C2R Version 2302 / Build 16130.20332 (Current Channel) says “You’re up to date!” when I run a manual update check, even though I’m sure I’m a few versions behind.

UPDATE:  This was apparently a widespread issue (see the 03-Apr-2023 reddit thread Microsoft Office 365 Suddenly Downgrades from Version 2303 to 2302 on Current Channel for one example) but I was finally able to update to the latest Version 2303 / Build 16227.20280 this evening.  See post # 2552176 in my thread Microsoft Office 2019 C2R Not Updating for further details.
—————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.2846 * Firefox v112.0.0 * Microsoft Defender v4.18.2303.8-1.1.20200.4 * Malwarebytes Premium v4.5.26.259-1.0.1976 * Macrium Reflect Free v8.0.7279 * Microsoft Office Home and Business 2019 C2R Version 2303 / Build 16227.20280

Reply | Quote

deuxbits,

I observed the same behavior you describe on two Win 10 22H2 machines and one Win 11 22H2 machine. One Win 11 machine to to go and I expect the same. Experience with WU weirdness, listening for fans, and a suspicious eye on activity in Task Manager have prevented any unfortunate mishaps.

Reply | Quote

I have a question I have !0 Pro.  Home user. I’m still on 21H2.  Is WU going to automatically offer 22H2  before 21H2 runs out?  So far I haven’t been offered it.

Reply | Quote

Windows Update has been offering 22H2 automatically since its release.
The question is, do you have something blocking the upgrade?
Have you set TRV to stay on 21H2 using Susan’s scripts, Registry entries, or Group Policy?
Have you deferred feature updates?
Are you using InControl to block it?
Are you using WUMgr to block it?
What other third-party software have you used in the past to block upgrades that you have forgotten you used?

Is Windows Update working normally otherwise?

1 user thanked author for this post.

Geo

Reply | Quote

Still getting regular updates.  Haven’t blocked anything. Thanks I’ll check your  suggestions.

Reply | Quote

There are screenshots at the bottom of AKB2000016 to show where the Registry and Group Policy settings are for TRV and deferral.

1 user thanked author for this post.

Geo

Reply | Quote

As of yesterday (4/12) I have done the following 2023-04 April updates without problems:

1x Windows 8.1 Pro
4x Win10 Pro 22H2 to Build 19045.2846 (three ar Parallels VMs on Intel Macs, one is an old Dell XPS Studio 1340 laptop I upgraded from Win7 a couple of months ago)
1X Win11 Pro ARM 22H2 to Build 22621.1555 (Parallels VM on M1 MacMini, removed from Insider Program in March, now consumer)
x1 Win11 Pro 22H2 to build 22621.1555 (AMD Ryzen 3.4300G hardware install on low end test desktop)

Remaining updates to do: 2x Win8.1 Pro, 1x Win10 Pro

4 users thanked author for this post.

Geo, geekdom, Microfix, abbodi86

Reply | Quote

Couple of enlightening articles relative to this months patches, what microsoft close, fix and fix again…

Dustin Childs over on Zero Day Initiative

Apurva Venkat over on CSOonline

NOTE: you may need to use a paywall bypass in UBO extension or similar:
I use the method in this article on gHacks 😉

Windows - commercial by definition and now function...

1 user thanked author for this post.

deuxbits

Reply | Quote

The article is by Ashwin, not Martin.

I use Bypass Paywalls Clean and it seems to work, without going through all the gymnastics recommended by the article.  I found I had two versions, a recommended one and a non-recommended one, so I deleted the non-recommended one.  The add-on gets regular updates on Firefox.

Thanks for reminding me about it.

Mark

 

2 users thanked author for this post.

Microfix, deuxbits

Reply | Quote

I found the problem. I checked back in my update history and  it didn’t have  KB5015684 the enable package listed. Downloaded/installed it and it immediately allowed  the 22H2  feature update to proceed.  Thanks for the suggestions.

1 user thanked author for this post.

geekdom

Reply | Quote

deuxbits wrote:

I’ve also observed this premature/early restart when a .NET update is in the mix of updates.

I am using WUmgr, no ‘premature restart’ when .NET updates included.

https://www.askwoody.com/forums/topic/the-patching-showers-of-april/#post-2551620

Reply | Quote

https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-overview

..Legacy LAPS Interop issues with the April 11 2023 Update

Important

The April 11, 2023 update has two potential regressions related to interoperability with legacy LAPS scenarios. Please read the following to understand the scenario parameters plus possible workarounds.

Issue #1: If you install the legacy LAPS CSE on a device patched with the April 11, 2023 security update and an applied legacy LAPS policy, both Windows LAPS and legacy LAPS will enter a broken state where neither feature will update the password for the managed account. Symptoms include Windows LAPS event log IDs 10031 and 10033, as well as legacy LAPS event ID 6. Microsoft is working on a fix for this issue.

Two primary workarounds exist for the above issue:

a. Uninstall the legacy LAPS CSE (result: Windows LAPS will take over management of the managed account)

b. Disable legacy LAPS emulation mode (result: legacy LAPS will take over management of the managed account)

Issue #2: If you apply a legacy LAPS policy to a device patched with the April 11, 2023 update, Windows LAPS will immediately enforce\honor the legacy LAPS policy, which may be disruptive (for example if done during OS deployment workflow). Disable legacy LAPS emulation mode may also be used to prevent those issues…

Reply | Quote

Hi everyone,

I’ve patched 3x Windows 11 22H2 systems and 2x Windows 10 22H2 64 bit systems and have not experienced any issues.

All systems have SSD primary hard drives and no SSD slowdown was observed. I benchmarked the systems before and after the updates using CrystalDiskmark. I only did so since there were reports of SSD slowdown and other issues within the following article:

https://www.windowslatest.com/2023/04/13/windows-11-kb5025239-issues-file-explorer-ssd-bsod/

Thanks.

1 user thanked author for this post.

geekdom

Reply | Quote

While I usually wait for the MS-DEFCON status to reach 3 or 4, yesterday I had just done a full disk image backup and so threw caution to the wind and installed the following updates on Windows 10 Pro 21H2, bringing the build version up to the latest 19044.2846.

Windows Malicious Software Removal Tool x64 – v5.112 (KB890830)

2023-04 .NET 6.0.16 Security Update for x64 Client (KB5025915)

2023-04 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5025221)

No (apparent) issues whatsoever.

1 user thanked author for this post.

geekdom

Reply | Quote