February 2024 patches for Windows

Topic

New Reply

Ready or not, here comes the February updates for Windows. Will we see a fix for our  KB5034441 for Windows 10 22H2 and in KB5034440 for Windows 11 wo
[See the full post at: February 2024 patches for Windows]

Susan Bradley Patch Lady/Prudent patcher

7 users thanked author for this post.

scottchamings, L95, Norio, Alex5723, WCHS, lmacri, abbodi86

Reply | Quote

Replies

AKB 2000003 has been updated for Group B Win7 and Win8.1 on Feb 13, 2024.

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

1 user thanked author for this post.

abbodi86

Reply | Quote

KB5034765 Windows 11 23H2 and 22H2

KB5034763 Windows 10

KB5034768 Windows 10 1809

KB5034767 Windows 10 1607

KB5034774 Windows 10 1507

Reply | Quote

Susan Bradley wrote:

Ready or not, here comes the February updates for Windows. Will we see a fix for our  KB5034441 for Windows 10 22H2 and in KB5034440 for Windows 11 wo
[See the full post at: February 2024 patches for Windows]

A fix for our KB5034441 for Windows 10 22H2 and in KB5034440 for Windows 11?

Highly unlikely! Microsoft’s priorities lie elsewhere, since there is no financial incentive or marketing advantage to be gained here. I would be very happy to be proven wrong, however.

Reply | Quote

Looks like a big mess for Outlook 2016, requiring multiple patches to fix a RCE vulnerability with a CVSS 9.8 rating…

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21413

 

Reply | Quote

Yup this has a huge number of Office msi updates (if you still have that patching format)

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

For the .msi installed versions only. The fixes do not apply to Click-to-run versions.

--Joe

1 user thanked author for this post.

CraigS26

Reply | Quote

Yes it does, they are just rolled up in the click to run bundle.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

deuxbits

Reply | Quote

Those are just 5 updates, there are 7 more updates

they really stack them after 3 months of litening

Reply | Quote

Uneventful installation bringing my version of Windows 11 Pro to 22631.3155

2024-02 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64 (KB5034467)

2024-02 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5034765)

2024-02 .NET 8.0.2 Security Update for x64 Client (KB5035121)

2024-02 .NET 7.0.16 Security Update for x64 Client (KB5035120)

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

--Joe

Reply | Quote

Will we see a fix for our KB5034441 for Windows 10 22H2 and in KB5034440 for Windows 11 woes?

the answer to this question so far is a resounding NO!

continue to hide/block these updates indefinitely with wushowhide.diagcab, WUMT or wumgr, even with the newly released February 2024 updates

Reply | Quote

Susan Bradley wrote:

What we will see is “Highlights for Windows 11, versions 22H2 & 23H2 (cont.) •The Copilot in Windows icon will appear on the right side of the system tray on the taskbar. Also, the display of Show desktop at the rightmost corner of the taskbar will be off by default.”

Ugh. And double Ugh.

Show desktop sliver can be re-enabled at Settings, Personalization, Taskbar behaviours, Select the far corner of the taskbar to show the desktop.

(I suspect it was disabled as most don’t use it or even know it’s there.)

Why do you care where the Copilot icon is? (It can be turned off)

Reply | Quote

Because it’s taking the place of show desktop that many of us do you and has been there for many years. Give me a registry key or a group policy setting so we can get this out BEFORE it gets released please. Oh and can Microsoft please do that? There is nothing quite so frustrating in a firm than ‘dribbled’ changes. It makes me have to visually see everyone’s desktop.

Susan Bradley Patch Lady/Prudent patcher

6 users thanked author for this post.

Andy M, deuxbits, steeviebops, abbodi86, TechTango, PL1

Reply | Quote

Susan Bradley wrote:

Because it’s taking the place of show desktop that many of us do you and has been there for many years.

It’s not. You can easily have both. I do right now.

And Win + D still works just as it has for 28 years since Windows 95.

P.S. Take a poll in your company and see how many ever use either.

Reply | Quote

They do use the show desktop, they don’t use Win D.  No, I have to put it back, they don’t know where to go to put it back B.  This is tax season and they don’t want Microsoft to be messing with their desktops with Farmer’s deadline at the end of the month.

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

Andy M, deuxbits, Cybertooth

Reply | Quote

Susan Bradley wrote:

Because it’s taking the place of show desktop that many of us do you use and has been there for many years.

Is this “Desktop sliver” problem only in Windows 11? Does Windows 10/Pro have any GUI (or GP setting) to control Taskbar behavior so that the sliver either shows or does not? Or is the sliver always there in Windows 10, no matter what?

Reply | Quote

Microsoft calls that sliver Preview Desktop and here’s how to turn it off in Windows 10.

Right-click an “empty” spot on the taskbar and select the Taskbar settings option.

In the right-hand column turn off the Use Peek to preview the desktop… option like this.

You also can permanently disable it (i.e.the option will be “grayed out” like in the above image) using the following registry entry.

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"DisablePreviewDesktop"=dword:00000001

Reply | Quote

n0ads wrote:

n the right-hand column turn off the Use Peek to preview the desktop… option like this.

I am asking about the sliver, not whether or not one is able “To use it/Peek to preview”. No matter whether you turning that switch ON or OFF in Windows 10, the sliver is still there, working to peek or not to peek, depending on the setting.

I don’t use Windows 11, but it seems that the sliver can disappear (so Susan has a reg file to make it come back or you can use the GUI to make it come back).

So, I am asking if you can make the sliver itself disappear in Windows 10.

Reply | Quote

What that option and the associated registry entry turns off is the sliver!

At least it does on my Windows 10 22H2.

Reply | Quote

The reg key does but the option does not.

(Peek preview affects hover, not click.)

Reply | Quote

n0ads wrote:

What that option and the associated registry entry turns off is the sliver!

Here are the results of “Use Peek to preview” ON/OFF and “Use Peek to preview” greyed out CHECKED/UNCHECKED in every combination possible.

The sliver is present, no matter what & the Desktop shows when clicking on it.
Hovering over the sliver produces the Desktop only in 2)

I greyed out “Use Peek to preview” not via the Registry, but by Settings > About > ‘Advanced system settings’ > ‘Settings’ under the Performance heading > check box for ‘Enable Peek preview’ under the ‘Visual Effects’ tab and the radio button set at ‘Custom’.

Following @b, maybe the only way to eliminate the sliver is via the registry key that sets the DWORD for “DisablePreviewDesktop” to 00000001. Using the GUI to get to Visual Effects does not do it.

Reply | Quote

Ok, I dug a bit deeper to find out exactly how I hid it and discovered it’s one of the many features available in 7+ Taskbar Tweaker.

Sorry for the confusion!

1 user thanked author for this post.

WCHS

Reply | Quote

I’ve installed KB5034765 and KB5034467 on my personal laptop. the former has now triggered (most of) the EU DMA changes. I now have the “All apps” link in the Start menu renamed to “All” and I can remove most of the apps. Still don’t have the option to remove Edge though (although I don’t intend to anyway).

Reply | Quote

Server 2008 & R2 still got updates this month

“Premium Assurance Support”?

Reply | Quote

Hardened Windows user:

KB5034467 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64
KB5034765 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems
KB5035120 .NET 7.0.16 Security Update for x64 Client
PowerShell v7.3.11 (x64)
KB890830 Windows Malicious Software Removal Tool x64 – v5.121

Now running Windows 11 Pro Version 23H2 (OS Build 22631.3155) I’ll wait for the push on my NAS and E5420.

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

Reply | Quote

… got the push:

E5420

2024-02 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64 (KB5034467)
2024-02 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5034765)
2024-02 .NET 6.0.27 Security Update for x64 Client (KB5035119)
Windows Malicious Software Removal Tool x64 – v5.121 (KB890830)

NAS
KB5034467 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 for x64
KB5034765 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems
KB890830 Windows Malicious Software Removal Tool x64 – v5.121

No hiccups.

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

Reply | Quote

Looks like MS has now provided a PowerShell script to Extend the Windows RE Partition.

4 users thanked author for this post.

deuxbits, Microfix, abbodi86, DKThompson

Reply | Quote

SteveIT wrote:

Looks like MS has now provided a PowerShell script to Extend the Windows RE Partition.

That’s not a fix.  Most users have no business trying to run PowerShell or definitely not trying to resize their RE partition.

3 users thanked author for this post.

Alex5723, Mark, NaNoNyMouse

Reply | Quote

Donny H wrote:

Most users have no business trying to run PowerShell or definitely not trying to resize their RE partition.

Unless they would like to give it a try.  Their PC and how they wish to use it is entirely their business, and no one else’s.  They are free to follow the advice of whomever they may choose.  See the green in my signature.

 

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.

TechTango, DKThompson, Microfix

Reply | Quote

Windows 10 22H2. I updated tonight. had to retry several times due to I imagine server load. 3 updates, removal tool, .NET update and cumulative. Took awhile to finally all download, but update went fine after a few tries, and system appears to be running fine.

OS build is now: 19045.4046

1 user thanked author for this post.

deuxbits

Reply | Quote

Updated Canary Today.

All seems well…

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

I quit Windows finally this year. Prepared that step for a long time to come. Way too many problems with it. Was worried moving to macOS and Linux would bring some troubles, but in reality I didn’t encounter one. MacOS is there for Office. But this Office gets less and less important because companies are finally stearing away from complicated templates designed for MS Office only. In fact, the last few years my work moved from an Office-environment to a browser based CMS for 99 percent of clients. dumping Windows gives a lot less stress and peace of mind. No wild ‘we know what is good for you’ buggy updates anymore!

2 users thanked author for this post.

Fred, Cybertooth

Reply | Quote

I installed the updates for Windows 11 23H2. I left KB5034765 until last but when I saw that others here had installed it successfully, I went ahead with the installation.  I had problems with WUMgr, which couldn’t seem to download the update (something about the page being forbidden), so I tried with Windows Automatic Update, which did the update.  However there were two consecutive reboots for KB5034765 only.  The other updates were uneventful.

I did not notice any changes to my taskbar, or anything different at all.

Mark

Reply | Quote

I think I know why I got the two restarts.  I have Windows Automatic Update to restart after updating if necessary.  The update does the first restart, then WAU does the second since it apparently doesn’t know that there has already been an update.  I guess it needs Windows CoPilot to work properly.

Mark

 

Reply | Quote

The only thing I have noticed since last update is that the Windows Explorer listings are more detailed.  Libraries have appeared, or have become more prominent in the display.  I should mention that I don’t have most of Edge, and CoPilot has been disabled.

Mark

 

1 user thanked author for this post.

Cybertooth

Reply | Quote

Mark wrote:

However there were two consecutive reboots for KB5034765 only.

Hi Mark:

I can’t speak to Win 11, but on my Win 10 Pro v22H2 machine the installation of the monthly cumulative Quality Update by Windows Update that changes the OS build number always re-boots a second time after I click “Restart Now” once the installation reaches the point where screen says “Working on updates. 30% complete. Don’t turn off your computer“. I’ve observed this extra re-boot on Patch Tuesdays for several months now.

I originally thought this re-boot at “30%” Complete” had something to do with installation of my .NET Framework update. However, there was no .NET Framework update delivered to my system during the December 2024 Patch Tuesday updates and I still saw the second re-boot (see my 17-Dec-2024 post # 2612637 in Susan Bradley’s We Need a Little December Copilot) so I’m guessing the second re-boot is required to complete the installation of the Servicing Stack Update (SSU) that is now bundled with each monthly Quality Update.

As far as I know this extra re-boot at “30% complete” also occurs if you use WUMgr to manager your updates – see the WUMgr image attached to Alex5723’s 10-Aug-2023 post # 2578826 in SusanBradley’s August 2023 Updates Are Out.
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Edge v121.0.2277.112 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

Reply | Quote

I haven’t installed this months updates on any of my (Win 11 22H2) machines yet, but have seen the  extra reboot @ 30% for months on all of them if I happen to be paying attention. Definitely a Win 11 thing too.

Reply | Quote

Everyone seems to think the reboot at 30% is a “second reboot”, it’s not!

Whenever a PC reboots/restarts, the screen will turn black between the shutdown and the reboot/restart and (unless you’ve got it disabled) you’ll “momentarily” see the PC’s BIOS screen like this.

If you don’t see this happen, the PC has not rebooted/restarted!

BTW, here’s what’s actually happening when you click “Restart Now” during a Windows update.

The OS “starts” it’s shutdown process by stopping all interactive user processes, including the desktop, and the update process installs the first 30% of the update.

The PC then shuts down (i.e. the screen turns black) and initiates a reboot/restart.

During the restart, the update process installs the other 70% of the update and, if that succeeds, starts the interactive user processes.

If the update “fails” during the restart, you’ll see a message indicating the update is being rolled back and the PC will go thru a second reboot/restart cycle to remove all the parts of the failed update.

2 users thanked author for this post.

lmacri, Cybertooth

Reply | Quote

https://www.ghacks.net/2024/02/13/the-windows-security-updates-for-february-2024-are-here/

Windows 10 version 22H2: 38 vulnerabilities, 1 critical and 37 important.
Windows Pragmatic General Multicast (PGM) Remote Code Execution Vulnerability — CVE-2024-21357

Windows 11 version 22H2: 41 vulnerabilities, 2 critical. 38 important, and 1 moderate
Windows Pragmatic General Multicast (PGM) Remote Code Execution Vulnerability — CVE-2024-21357
Windows Hyper-V Denial of Service Vulnerability — CVE-2024-20684

Windows 11 version 23H2: 41 vulnerabilities, 2 critical. 38 important, and 1 moderate
same as Windows 11 version 22H2

Windows Server 2008 R2 (extended support only): 27 vulnerabilities: 1 critical and 26 important
Windows Pragmatic General Multicast (PGM) Remote Code Execution Vulnerability — CVE-2024-21357

Windows Server 2012 R2 (extended support only): vulnerabilities: critical and important

Windows Server 2016: 34 vulnerabilities: 1 critical and 33 important
same critical vulnerability fixes as Windows Server 2008 R2

Windows Server 2019: 39 vulnerabilities: 1 critical and 38 important
same critical vulnerability fixes as Windows Server 2008 R2

Windows Server 2022: 36 vulnerabilities: 2 critical, 33 important, and 1 moderate
Windows Pragmatic General Multicast (PGM) Remote Code Execution Vulnerability — CVE-2024-21357
Windows Hyper-V Denial of Service Vulnerability — CVE-2024-20684..

1 user thanked author for this post.

Fred

Reply | Quote

Ooops, so much for a quiet mid-February notice,
will all leaks and flaws be repaired right now?
And we can rest greatfull to Redmonds gift to society.

* _ ... _ *

1 user thanked author for this post.

Alex5723

Reply | Quote

SteveIT wrote:

Looks like MS has now provided a PowerShell script to Extend the Windows RE Partition.

Initially released last month. Good only if Recovery partition is after C: partition.

3 users thanked author for this post.

deuxbits, SteveIT, Mark

Reply | Quote

Taking a quick look at the code, it looks like the script will create a new WinRE partition after the OS partition if the existing WinRE partition is before the OS partition:

# However, if the WinRE partition is before the OS partition, there is no chance to extend it
# As a result, it's better to create a new WinRE partition after the OS partition

In addition, I couldn’t find where the script sets the gpt attributes (to 0x8000000000000001) as required in the manual instructions of KB5028997. These attributes specify that the partition is required for the computer to function properly, and that the partition won’t receive a drive letter.

3 users thanked author for this post.

DKThompson, Alex5723, Microfix

Reply | Quote

What if you don’t have a recovery partition or a WinRE partition (WinRE is disabled)?

Reply | Quote

The patch will probably still fail.  Microsoft hasn’t addressed any of the issues.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Yes, the patch fails.  I tried it just to see, was curious.  It is hidden and will stay hidden.  But, if KB5034441 gets incorporated into a Cumulative update, then the whole update will fail.  And then what.  I have no intention of creating a recovery partition or a WinRE partition.  Don’t need either.  But, if I am forced to create either, then will see what is needed to create, unless it will go on without the partitions.

Reply | Quote

Reads like Microsoft are deliberately trying to slowly kill off W10 before EoS for the non-techies, dispicable!

Must be desperate for the upgrade uptake to Win!!

Microfix wrote:

I’m of the thought that it’s unlikely MSFT will re-issue a patch to replace/ supercede kb5034441 for W10.

kinda rings true there..

Windows - commercial by definition and now function...

1 user thanked author for this post.

Cybertooth

Reply | Quote

Well actually, they are trying to elevenize Win10 with “cool” backported features that will make it miserable enough

1 user thanked author for this post.

Cybertooth

Reply | Quote

I have a Win11 22H2 laptop, 2 Win10 22H2 desktops and this Win10 22H2 laptop.  When I built the 2 desktops, the Windows install did not create a recorvery partition or a WinRE partition.  I don’t have any issues with Win11.  I guess when the ok for Win11 23H2 is given, then I will upgrade the Win11 22H2 laptop and will upgrade one of the Win10 22H2 desktops to Win11 23H2 to see how that experience goes.  I vowed to never go from XP to 7 but did.  And vowed to never go from 7 to 10 but did.  Did 2 years of 7 ESU.  So will go from 10 to 11 when 23H2 is blessed.  As the Borg say, resistance is futile.

Reply | Quote

Three 22H2 W10 devices updated
(Dumped the dull and utterly boring W11 after 9 months, no image wasted on a backup device, reimaged back to W10)
Two W10 Pro x64 and one W10 Pro x86.
CU KB5034763
NET KB5034685
No issues or tissues so far..

© Computer Mental LLC

Windows - commercial by definition and now function...

6 users thanked author for this post.

Fred, PDX5802, TechTango, deuxbits, Cybertooth, Alex5723

Reply | Quote

Probably worth noting that the Exchange update was CU14, and the CVE was addressed by enabling Windows Extended Protection not any particular new security update, so if you had that enabled you were already good to go.

Reply | Quote

Two canary 22H2 W10 Pro x64 machines updated so far. No issues seen other than the now standard premature restart notification when the .NET update is installed but the CU is still in the midst of installing. We always wait for all updates to show “Pending restart”

CU KB5034763

.NET KB5034685

Plus the WMSRT v 5.121 KB890830

However, not stress tested yet. More to come.

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

Reply | Quote

Windows 10 Pro 22H2 installed Feb. updates
CU KB5034763
.NET 7.0.16 KB5035120
.NET 6.0.27 KB5035119
.NET 3.5, 4.8, 4.8.1 KB5034685
Defender update KB2267602
MSRT KB890830

All is well.

1 user thanked author for this post.

deuxbits

Reply | Quote

Alex5723 wrote:

Good only if Recovery partition is after C: partition.

In my experience this partition_movement was best done by hand with a (free) partition tool, and INDEED placing the recovery-partition AFTER the C:\ Windows-Systempartition.

Did they ever test their repairs? Boy oh boy

* _ ... _ *

2 users thanked author for this post.

PL1, Alex5723

Reply | Quote

Microsoft are in not rush to fix  KB5034441

The problem they created!

It really shows how much the don’t care.

All they seem to be focused on is copilot.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Hi Susan:

Windows Update successfully installed all updates offered for the February 2024 Patch Tuesday on my Win 10 Pro v22H2 laptop, and I haven’t observed any negative effects so far. This includes:

• KB5034763: 2024-02 Cumulative Update for Win 10 Version 22H2 for x64 (OS Build 19045.4046)
• KB5034685: 2024-02 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 222H2 for x64
• KB5035119: 2024-01 .NET 6.0.27 Security Update for x64 Client
• KB5035120: 2024-01 .NET 7.0.16 Security Update for x64 Client
• KB890830 : Windows Malicious Software Removal Tool x64 – v5.121

I was not expecting to be offered KB5034685 since this month’s 2024-02 .NET Framework update does not include a security patch (I used my Local Group Policy Editor to configure Window Update to skip Week C/D Preview updates, which also had the odd side-effect of blocking .NET Framework updates that did not include security improvements), but that seems to be a thing of the past. See my 13-Oct-2023 post # 2593792 in October Updates – Here Comes Copilot about a similar unexpected installation of the KB5031224 2023-10 .NET Framework update that did not include a security patch. No worries, though – I’m fine getting all Patch Tuesday .NET Framework updates again, with or without a security patch.

I also did not see the early “Restart Now” glitch this month that normally occurs when Windows Update delivers a .NET Framework update with my other my Patch Tuesday updates. This month’s KB5034685 2024-02 .NET Framework update installed successfully without having the status of the update change to “Pending Restart” (see attached image), which differs from what duexbits reported above in post # 2637687 for their Win 10 Pro v22H2 machines.
——————————-

NOTE that last month’s KB5034441 (WinRE Update for Win 10 v21H2 and v22H2: January 9, 2024) installed successfully on my system along with my other Jan 2024 Patch Tuesday updates even though I had less than 250 MB of free disk space my WinRE partition  (see my 16-Jan-2024 post # 2628138 in Ready for the New Patching Year? for details) so I was not expecting KB5034441 to be re-offered this month.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

3 users thanked author for this post.

Deo, Cybertooth, WCHS

Reply | Quote

The .NET’s are driving me crazy this month.  They are titled up – and acting like – they have new security content but the documentation says they don’t.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

WCHS

Reply | Quote

2 .NET Denial of Service vulnerabilities this month, CVE-2024-21386 and CVE-2024-21404, might be why?

Reply | Quote

Those two are for .NET Core, not .NET Framework

Reply | Quote

A wrote:

2 .NET Denial of Service vulnerabilities this month, CVE-2024-21386 and CVE-2024-21404, might be why?

Hi A:

Those CVEs apply to the .NET v6.x/v7.x/v8.x Runtimes but I don’t think they apply to any .NET Frameworks.  Those CVE’s are documented in the 13-Feb-2024 .NET blog entry .NET February 2024 Updates – .NET 8.0.2, 7.0.16, .NET 6.0.27, but there’s no mention of them in the blog entries for the 23-Jan-2024 .NET Framework January 2024 Cumulative Update Preview or the 14-Feb-2024 .NET Framework February 2024 Security and Quality Rollup Updates.

Also, if you read the actual security advisories for CVE-2024-21386 and CVE-2024-21404 there is no .NET Framework listed as an affected product.

If I search Security Update Guide of the Microsoft’s MSRC at https://msrc.microsoft.com/update-guide/vulnerability for “.NET Framework” this lists 5 or 6 other known vulnerabilities [including CVE-2024-21312 (.NET Framework Denial of Service Vulnerability)] with recently updated write-ups, but I didn’t bother reading through each of those CVE write-ups to try to determine which, if any, of those vulnerabilities was patched by the 23-Jan-2024 KB5034582 .NET Framework Preview and/or “stable” 13-Feb-2024 KB5034685 .NET Framework cumulative update.
——————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

Reply | Quote

Susan Bradley wrote:

The .NET’s are driving me crazy this month. They are titled up – and acting like – they have new security content but the documentation says they don’t.

I suspect Microsoft is assuming that everyone installed the 23-Jan-2024 KB5034582 .NET Framework Preview, which apparently included security updates even though the CVEs that were patched are not listed <here> in the information bulletin.  In their minds the the “stable” 13-Feb-2024 KB5034685 released on Patch Tuesday contains no “new” security updates because the updates bundled inside the KB5034582 Preview and the “stable” KB5034685 are identical.

According to the information bulletin <here> for the 13-Feb-2024 KB5034685 Win 10 users with .NET Framework v4.8.0 should have received 5034468 while users with .NET Framework v4.8.1 should have received 5034466.

My .NET Framework v4.x was updated to v4.8.1 on 12-Oct-2024 (listed under “Other Updates” in my Windows Update history), and when I check at Control Panel | Programs | Programs and Features | View Installed Updates I can see that I received the correct KB5034466 update with my Feb 2024 Patch Tuesday updates.

The KB5034466 information bulletin <here> states “This update was originally released in the Security and Quality Rollup that’s dated January 23, 2024…The January 23, 2024 update for Windows 10 Version 22H2 includes security and cumulative reliability improvements in .NET Framework 3.5 and 4.8.1”  but doesn’t list the CVE’s that were patched in January 2024.  The summary goes on to says “There are no new security improvements in this release” but the security updates in the 13-Feb-2024 Patch Tuesday release were “new” to people like me who did not install the 23-Jan-2024 Preview build.
————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

Reply | Quote

It’s called .NET “Cumulative” Update, it contain all previous fixes, security or quality

and yes, this February updates (for all supported Windows versions) or the January Previews do not contain “new” security fixes

https://devblogs.microsoft.com/dotnet/dotnet-framework-february-2024-security-and-quality-rollup-updates/

i really thought everyone is already got used of this “confusing” update model, because it’s going since late 2020

Reply | Quote

abbodi86 wrote:

this February updates (for all supported Windows versions) or the January Previews do not contain “new” security fixes

Hi abbodi86:

The problem for me is incomplete / incorrect documentation, not the concept of cumulative updates.

If you are correct that the Jan 2024 Previews and Feb 2024 Patch Tuesday updates did not include a security improvement for a .NET Framework then the information bulletin for KB5034466 (i.e., the .NET Framework v3,5 and v4.8.1 update released on 13-Feb-2024 that is bundled inside KB5034685) has incorrectly stated “The January 23, 2024 update for Windows 10 Version 22H2 includes security and cumulative reliability improvements in .NET Framework 3.5 and 4.8.1” .

If there are no security improvements in the 23-Jan-2023 KB5034582 Preview build then I would also expect the “Security Updates” section of the information bulletin at January 23, 2024-KB5034582 Cumulative Update Preview for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 to say “There are no new security improvements in this release. This update is cumulative and contains all previously released security improvements” (either that, or actually list the CVEs patched if it does include a security improvement).  Instead, that “Security Updates” section for the 23-Jan-2023 KB5034582 Preview build is completely blank, which I don’t recall ever seeing before.

If you are correct and the January 9, 2024-KB5034275 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 released with the Jan 2024 Patch Tuesday updates was the last cumulative update to include a security improvement then this certainly wasn’t clear to me from the past month’s documentation.
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Edge v121.0.2277.112 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

Reply | Quote

All KB5034685 / KB5034466 / KB5034468 articles has the notice “no new security improvements in this release”

KB5034582 is Preview (Optional) cumulative update, by design, it’s not supposed to include any new security fixes
yes, they could clearly put the notice like previous previews, but it just complementary

2 users thanked author for this post.

lmacri, WCHS

Reply | Quote

abbodi86 wrote:

KB5034582 is Preview (Optional) cumulative update, by design, it’s not supposed to include any new security fixes

Hi abbodi86:

Thanks for that info. I didn’t realize the .NET Framework Preview builds never include security improvements.

That must also mean that something has recently changed with the setting I use in my Win 10 Pro Local Group Policy Editor (LGPE) to manage delivery of Week C/D Preview Updates (Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received).

Up until October 2023 Windows Update would not deliver Patch Tuesday .NET Framework updates that did not include a security improvement as long as that setting was ENABLED in my LGPE.  I don’t know why this happened but the  behaviour was consistent for many years until KB5031224 (Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2: October 10, 2023) was delivered with my other Oct 2023 Patch Tuesday updates, even though KB5031224 did not include a security improvement.

I’ll wait for release of the next .NET Framework update that does not include a security improvement and will start a separate topic about controlling Preview Builds with the LGPE if something “wonky” happens again and the update is delivered.  I know that the option to select a delivery channel (e.g., Semi-Annual Channel) was removed from that LGPE setting over a year ago so perhaps other changes have been implemented in that LPGE setting that I’m not aware of.
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Edge v121.0.2277.112 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

WCHS

Reply | Quote

In my experience:

The “Preview Updates” contain non-security content.
The “Cumulative Updates” contain security content and non-security content.
The Monthly CU for .NET then contains security content and non-security content, even though there were no new security content.

That may explain why your setting didn’t prevent the installation of the CU.

1 user thanked author for this post.

lmacri

Reply | Quote

PKCano wrote:

… The Monthly CU for .NET then contains security content and non-security content, even though there were no new security content.,,

Hi PKCano:

I understand that.

However, up until  October 2023 my Local Group Policy Editor (LGPE)  settings prevented delivery of .NET Framework Monthly CU updates released on Patch Tuesdays that did not include a security improvement. That means that I should not have received the “stable” KB5031224 (10-Oct-2023) and this month’s KB5034685 (13-Feb-2024) .NET Framework Monthly CU updates, since both did not include a security update, but both were installed by Windows Update.

Since October 2023 I’ve received every .NET Framework Monthly CU update released on a Patch Tuesday, regardless of whether it includes a security improvement or not. That’s fine by me – I was just trying to point out that my LGPE setting at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received isn’t behaving the way it used to prior to October 2023, at least in regards to my .NET Framework updates.
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

Reply | Quote

lmacri wrote:

Since October 2023 I’ve received every .NET Framework Monthly CU update released on a Patch Tuesday, regardless of whether it includes a security improvement or not.

For me, it’s “since Aug 2021”. (See #2639035). If your records for Patch-Tuesday installs go back to 2022 and 2021, you might find that Feb 2022’s KB5009467 and Aug 2021’s KB5004331 were delivered and installed, even though their KB descriptions say there is ‘no security improvement’.

I’ve had that GP setting since April, 2021 and I had always thought if affects Week C/D ‘Preview’ patches, not Week B Tuesday patches. I used to get Previews prior to April 2021, but after enabling that GP setting, they no longer appeared in the WU queue.

Reply | Quote

lmacri wrote:

Up until October 2023 Windows Update would not deliver Patch Tuesday .NET Framework updates that did not include a security improvement as long as that setting was ENABLED in my LGPE.

Hi @lmacri,
Ever since I upgraded to version Win 10 20H2 on April 9, 2021, like you, I also have had Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received set to ‘enabled, 0 days’

For 22H2 KB5031224 (October, 2023) and for 22H2 KB5034685 (February, 2024) I have observed the same behavior that you report – WU delivered it, even though there were new security improvements reported in Microsoft Catalog’s description for the KB.

In addition, according to my records, the same thing happened with:
Feb, 2022 .NET Framework patch 21H2 KB5009467 and
Aug, 2021 .NET Framework patch 21H1 KB5004331.

In each of these cases (as with the Feb 2024 and the Oct 2023 .NET Framework patches), there had been in the previous month’s NET Framework update a new security improvement.

Reply | Quote

WCHS wrote:

For 22H2 KB5031224 (October, 2023) and for 22H2 KB5034685 (February, 2024) I have observed the same behavior that you report – WU delivered it, even though there were new security improvements reported in Microsoft Catalog’s description for the KB.

Hi WCHS:

Is that a typo? If you read the “Security Improvements” section of KB5031224 (10-Oct-2023) and KB5034685 (13-Feb-2024) they now both say “There are no new security improvements in this release“. That is why I was surprised when both these .NET Framework Monthly CU updates were delivered to my machine.

According to the bulletins for the older KB5004331 (10-Aug-2021) and KB5009467 (08-Feb-2022) you mentioned in your post # 2639035 both those .NET Framework Monthly CU updates for Win 10 v21H1 also did not include a security improvement, and Windows Update did not deliver either of those older updates to my computer.

For example, my 14-Feb-2022 post # 2425269 in Susan Bradley’s February 2022 Patch Tuesday Early Reports states in part:

“… As expected, I didn’t receive this month’s KB5009467 .NET Framework 3.5 and 4.8 for Windows 10 (no security update included) because I have my Local Group Policy Editor option at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received enabled and set to Semi-Annual Channel …”

As far as I can tell, delivery of .NET Framework Monthly CU updates that do not have a security update is a relatively recent phenomenon on my own machine. I’m guessing this started after Microsoft removed the option to select the “Windows Readiness Level for Updates You Receive” (e.g., Semi-Annual Channel) from the LGPE setting at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received. The dropdown box to select a delivery channel for Windows Updates in that LGPE setting can still be seen in the second (now outdated) 24-Jun-2020 image in post # 2275043 of PKCano’s AKB2000016: Guide for Windows Update Settings for Windows 10, but that dropdown box is no longer present in my current LGPE setting (see attached image).
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

1 user thanked author for this post.

WCHS

Reply | Quote

WCHS wrote:

In addition, according to my records, the same thing happened with:
Feb, 2022 .NET Framework patch 21H2 KB5009467 and
Aug, 2021 .NET Framework patch 21H1 KB5004331.

I apologize here. I did not read my notes thoroughly. They were installed yes, but I manually installed them with the Stand Alone Installer. Even though they contained no new security improvements, I wanted to keep up with the reliability improvements.

My GP setting looks almost like your screenshot, except that I have ‘0’ for the days.

I am lost on MS’ logic for delivering Oct ’23 KB5031224 and Feb ’24 KB5034685. I’m surmising that MS is dotting its ‘i’s and crossing its ‘t’s by simply delivering the current month’s cumulative KB whether it has new security improvements or not. Maybe the reliability improvements are now as important as the security improvments. Who knows? But, as you say, it’s OK for it to be installed, even though there are no new security improvements.

1 user thanked author for this post.

lmacri

Reply | Quote

KB5034765.
Windows 11 users complain of taskbar, Start menu, and performance issues

..Among the problems people say they have been experiencing are a disappearing taskbar, a non-functioning Start menu, and graphical glitches across the Windows UI. Other complaints include the lengthy display of the “updates are underway” message, BSoDs, sluggish performance and more…

With Microsoft yet to admit that the update has any issues, there are no official fixes as yet…

Microsoft’s Jen Gentleman suggests uninstalling the KB5034765 update, restarting Windows and then reinstalling the same update…

1 user thanked author for this post.

Cybertooth

Reply | Quote

lmacri wrote:

WCHS wrote:

For 22H2 KB5031224 (October, 2023) and for 22H2 KB5034685 (February, 2024) I have observed the same behavior that you report – WU delivered it, even though there were new security improvements reported in Microsoft Catalog’s description for the KB.

Hi WCHS:

Is that a typo? If you read the “Security Improvements” section of KB5031224 (10-Oct-2023) and KB5034685 (13-Feb-2024) they now both say “There are no new security improvements in this release“. That is why I was surprised when both these .NET Framework Monthly CU updates were delivered to my machine.

According to the bulletins for the older KB5004331 (10-Aug-2021) and KB5009467 (08-Feb-2022) you mentioned in your post # 2639035 both those .NET Framework Monthly CU updates for Win 10 v21H1 also did not include a security improvement, and Windows Update did not deliver either of those older updates to my computer.

For example, my 14-Feb-2022 post # 2425269 in Susan Bradley’s February 2022 Patch Tuesday Early Reports states in part:

“… As expected, I didn’t receive this month’s KB5009467 .NET Framework 3.5 and 4.8 for Windows 10 (no security update included) because I have my Local Group Policy Editor option at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received enabled and set to Semi-Annual Channel …”

As far as I can tell, delivery of .NET Framework Monthly CU updates that do not have a security update is a relatively recent phenomenon on my own machine. I’m guessing this started after Microsoft removed the option to select the “Windows Readiness Level for Updates You Receive” (e.g., Semi-Annual Channel) from the LGPE setting at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received. The dropdown box to select a delivery channel for Windows Updates in that LGPE setting can still be seen in the second (now outdated) 24-Jun-2020 image in post # 2275043 of PKCano’s AKB2000016: Guide for Windows Update Settings for Windows 10, but that dropdown box is no longer present in my current LGPE setting (see attached image).
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.4046 * Firefox v122.0.1 * Microsoft Defender v4.18.23110.3-1.1.24010.10 * Malwarebytes Premium v4.6.8.311-1.0.2259 * Macrium Reflect Free v8.0.7783

Yes, it’s a typo. Thanks for pointing that out. Can’t be corrected now … but hopefully a reader can sort that out — otherwise, it doesn’t make much sense.

Reply | Quote

Updates for Feb.

Three Win11 updates to 22H2 Build 22621.3155, two in Parallels VMs on Apple Silicon and one h/w install on a low-end HP test desktop. All with the following patches:
KB5034407 .NET Framework 3.5/4.8.1
KB5043765 Win11 22H2 2024-02 Cumulative Update
Windows Defender update
No further updating of the WinRE Build 3000 since January. No Edge, no Copilot, no new Outlook, no extra buttons, NO problems.

Three Win10 updates to 22H2 Build 19045.4046, two in Parallels VM on Intel CPUs (WinRE part3 843MB and WinRE part5 1.54GB) and one on an old Dell Studio XPS 1340 upgraded from Win7 (winRE part2 14.656GB). In Jan., I used Mini Tool Partition Wizard on one of them to enlarge the WinRE partition to 1.54GB. Although there was an error on download (not install) with KB5034441, it installed after the reboot on all three in Jan. without errors. See #2628205 and #2629983. All with the following patches:
MSRT
KB5034685 .NET 3.5/4.8/4.81 Rollup
KB5034763 Win10 22H2 2024-02 Cumulative Update
Windows Defender update
No further updating of the WinRE Build 3920 since January. No Edge, no Copilot, no new Outlook, no extra buttons, NO problems.

Reply | Quote

PKCano wrote:

KB5043765 Win11 22H2 2024-02 Cumulative Update

Any of the bugs reported ?

Reply | Quote

None so far

1 user thanked author for this post.

Alex5723

Reply | Quote

Hi, PKCano:

It looks like you will be upgraded to Windows 11 23H2 soon now.

See today’s GHacks issue. (Feb 22).

Mark

Reply | Quote

Doubtful.

Reply | Quote

n0ads wrote:

Microsoft calls that sliver Preview Desktop and here’s how to turn it off in Windows 10.

I don’t and never had Preview Desktop on my Windows 10 since version 1803.

Reply | Quote

Alex5723 wrote:

I don’t and never had Preview Desktop on my Windows 10 since version 1803.

Did you remove the sliver? It’s been there on both of my laptops since they were first opened, one with v1703 and the other with v1909.

Reply | Quote

WCHS wrote:

Alex5723 wrote:

I don’t and never had Preview Desktop on my Windows 10 since version 1803.

Did you remove the sliver? It’s been there on both of my laptops since they were first opened, one with v1703 and the other with v1909.

Not to my recollection.
I don’t use 3rd party hacking software.

1 user thanked author for this post.

WCHS

Reply | Quote