Here come the May updates

Topic

New Reply

First up consumer advice: Remember this is the time that your main machine should be in deferral mode. So either defer updates for a later date, choos
[See the full post at: Here come the May updates]

Susan Bradley Patch Lady/Prudent patcher

11 users thanked author for this post.

lmacri, WCHS, David F, CAS, Alex5723, Coldheart9020, jburk07, geekdom, NetDef, abbodi86, DrBonzo

Reply | Quote

Replies

AKB 2000003 has been updated for Group B Win7 (ESU) and Win8.1 on May 10, 2022.

There is a Security-only Update for those with Win7 ESU subscriptions.
There was no May. IE11 CU  for Win7 .

May Rollup KB5014012 Download 32-bit or 64-bit for those with Win7 ESU subscriptions.

You must have at least the August 2020 Servicing Stack KB4570673 previously installed to receive these updates).

There is a March 2022 Servicing Stack KB5011649 – Download 32-bit or 64-bit for those with Win7 ESU subscriptions.

There is a revised Licensing Preparation Package KB4575903 dated 7/29/2020 for Win7 ESU subscriptions, if you need it. You will need a year-3 ESU license.

Some 2022-04 .NET Security-only updates were re-released. See @abbodi86 ‘s comments here.
There are .NET updates listed for Win7. See #2445539.

 

There is also a May Servicing Stack Update for Win8.1 KB5014025 download 32-bit or 64-bit.

7 users thanked author for this post.

Speccy, EricW, jburk07, abbodi86, SueW, T, DrBonzo

Reply | Quote

Microsoft Windows Security Updates: May 2022 overview

1 user thanked author for this post.

DrBonzo

Reply | Quote

Another month and the .NET updates giving me that old headache feeling yet again. Does anyone know why they are re-released? Just metadata changes or what? The sizes are identical.

Reply | Quote

It’s prob a metadata thing for supercedence.  You don’t need to reinstall it.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

T

Reply | Quote

Yeah, it’s a metadata change.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

T

Reply | Quote

.NET Frameworks updates for this month are all new and all security-based
https://devblogs.microsoft.com/dotnet/framework-may-2022-updates/

6 users thanked author for this post.

SueW, T, WCHS, geekdom, jburk07, Julia

Reply | Quote

No issues to report on two Windows 8.1 Pro systems.

After taking a Macrium image of the system, installed the Servicing Stack Update first (KB5014025) downloaded from the Microsoft Catalog. Then via Windows Update installed the Monthly Rollup (KB5014011) and Security and Quality Rollup for .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 for x64 (KB5013872).

2 users thanked author for this post.

EricW, DrBonzo

Reply | Quote

Windows 11

• 2022-05 .NET 6.0.5 Security Update for x64 Client (KB5014330)
• Windows Malicious Software Removal Tool x64 – v5.101 (KB890830)
• 2022-05 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 11 for x64 (KB5013628)
• 2022-05 Cumulative Update for Windows 11 for x64-based Systems (KB5013943)

All four updates were installed at the same time. When I rebooted, cleaned up, and then checked for updates, I had to reinstall Windows Malicious Software Removal Tool x64 – v5.101 (KB890830).

No errors, but updates seem more and more cumbersome.

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

Reply | Quote

For my daily driver dual boot:

Windows 10 Pro Version 21H2 (OS Build 19044.1706)

Cumulative Update for Windows 11 for x64-based Systems (KB5013942)
Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 11 for x64 (KB5013624)
Windows Malicious Software Removal Tool x64 – v5.101 (KB890830)

Windows 11 Pro Version 21H2 (OS Build 22000.675)

Cumulative Update for Windows 11 for x64-based Systems (KB5013943)
Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 11 for x64 (KB5013628)
Windows Malicious Software Removal Tool x64 – v5.101 (KB890830)

No hiccups.

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

We were all once "Average Users". 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.

Computer Specs

1 user thanked author for this post.

Coldheart9020

Reply | Quote

bbearren wrote:

Cumulative Update for Windows 11 for x64-based Systems (KB5013942)

You must mean Windows 10??

1 user thanked author for this post.

deuxbits

Reply | Quote

I am surprised that the SSU for Windows 8.1 didn’t appear in Windows Update.  I found out about it here and installed it from the Update Catalog.  GHacks didn’t mention it.  Thank you PKCano.

 

 

Reply | Quote

If you are using Windows Update, the latest SSU should install automatically.  If I remember right, you won’t see it in MU/WU but if you look in windows update history after the fact you’ll see it installed?

I don’t know if I have an 8.1 either in a vm or on a machine to test but most of the SSU’s are moving to be pretty automatic these days.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

In Win8.1 the SSU does not install automatically.
The SSU has to install by itself. It will not show up in the WU queue until there are no other pending updates. So you have to install or hide the pending updates before you see it in the queue.

You can:
+ Install the SSU manually from Catalog download first, then run WU
+ Install/hide all the pending updates until the queue is empty, then search for updates to see the SSU
+ Hide all pending updates so the queue is empty, search and install the SSU, then unhide and install the updates you want.

Reply | Quote

https://support.microsoft.com/en-us/help/5014032  This month they also have a standalone SSU for corporate folks.

7 would come down after 10 would come down before the update until they integrated it.

 

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

anonymous wrote:

5014032

Why is this not in the Patch List. BelArc reports I need this and I am just on W10 Pro??

🍻

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

Hi wavy:

What is your Win 10 Pro version and build shown at Settings | System | About | Windows Specifications, and do you have a 32-bit or 64-bit OS? If required, Servicing Stack Updates (SSUs) for Win 10 are now deployed by Windows Update with the monthly cumulative update and the release notes <here> for the May 2022 cumulative update KB5013942 (OS Builds 19042.1706, 19043.1706, and 19044.1706 for Win 10 v20H2, v21H1 and v21H2, respectively) note that either SSU 19042.1704, 19043.1704 or 19044.1704 were included with KB5013942 this month.

Windows Update applied the May 2022 Patch Tuesday updates on my Win 10 Pro v21H2 machine on 13-May-2022 and KB5014032 (the 10-May 2022 SSU for v20H2, v21H1 and v21H2) is not listed as a separate update in my Windows Update history. The “Missing Security Updates” section of my Belarc Advisor Free v11.4.0 report (with the latest v2022.5.12.1 Belarc definitions) shows I’m fully patched.
———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.1 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676

1 user thanked author for this post.

wavy

Reply | Quote

Belarc is wrong.  It’s only needed “This SSU update includes changes for Microsoft Endpoint Configuration Manager customers”

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

wavy

Reply | Quote

Hi.

You may be right, but usually I see it in the WU list immediately.  I can’t check what you write now since I installed it from the Catalog.  I will keep what you write for future reference.  Thank you.

 

Reply | Quote

As I recall, in W8.1 the latest SSU will not be offered through Windows Update until all important updates have been installed, or in other words, the important update queue is empty. I don’t remember whether it has to be empty because all the important updates have been installed or because you may have hidden some of them. I have 2 W8.1 computers and my important update queue is never empty because I refuse to install .NET 4.8, the MSRTs (MSRT updates have borked my W7 computers in the past, so no more), and Edge.

So, before I install the monthly rollup through Windows Update, I go to the rollup’s support page where it will tell me to install the latest version of the SSU before installing the rollup and will also tell me what the latest SSU KB number is. I download the latest SSU from the MS Catalog, install it, and then let Windows Update install the rollup.

Reply | Quote

After installing this months patches, one of my shared drives does not connect unless I use the ‘connect using different credentials’ setting and enter my username/password. This is for both server and client on the same domain. Normally, it connects as the current user on the client system and recognizes that I am already logged into the domain. The event logs on the server showed it trying to connect with the domain\computer name instead of domain\username. This suddenly happened after installing the May patches.

Reply | Quote

Which Windows? What patches?

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

1 user thanked author for this post.

deuxbits

Reply | Quote

Also shared drive to a NAS or Windows?

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

deuxbits

Reply | Quote

Now, after some investigation, this problem may be more unusual and even specific to our domain setup. It appears to be caused by something in the patches no longer allowing the server computer to recognize the equivalency of password and smartcard domain credentials.

Timeline:

all computers on windows 10 21H2, April patches, all on same domain

log into server computer with domain password

log into client computer with smartcard (on domain)

on client computer, access shared drive on server computer, successfully connects

update server computer to May patches

log into server computer with domain password

log into client computer with smartcard (on domain)

on client computer, access shared drive on server computer, connection fails

Event viewer SMB client side says: Error: The attempted logon is invalid. This is either due to a bad username or authentication information.

on client computer, access shared drive on server computer, specify “connect using different credential”, enter domain username and password, successfully connects

Log out of server computer and close session, log back into server computer with smartcard

log into client computer with smartcard (on domain)

on client computer, access shared drive on server computer, connection succeeds

on client computer, access shared drive on server computer, specify “connect using different credential”, enter domain username and password, connection fails

this behavior does not change after installing the may patches on the client computer. I am able to log into the server computer via remote desktop using either the domain password and smartcard

I am fairly certain that this behavior changed exactly when i installed the May updates on the server computer. However, our domain admins could have suddenly changed something without my knowledge also. Or there’s a small chance that I could just not remember how it behaved before the May updates.

1 user thanked author for this post.

deuxbits

Reply | Quote

This problem was apparently fixed by:
<p id=”page-header”>May 19, 2022—KB5015020 (OS Builds 19042.1708) Out-of-band</p>
Addresses a known issue that might prevent some services from authenticating machine accounts on clients or servers. This issue occurs after you install the May 10, 2022 update on domain controllers.

 

Reply | Quote

Windows 11 Pro

2022-05 .NET 5.0.17 Security Update for x64 Client (KB5014329)

2022-05 .NET 6.0.5 Security Update for x64 Client (KB5014330)

2022-05 .NET Core 3.1.25 Security Update for x64 Client (KB5014326)

2022-05 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 11 for x64 (KB5013628)

2022-05 Cumulative Update for Windows 11 for x64-based Systems (KB5013943)

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

All installed without issue.

--Joe

Reply | Quote

Just thought I’d share that my Lenovo ThinkPad T15 running Windows 11 Pro auto-installed KB5013943 this morning, and upon restart I got the wonderful Blue Screen of Death.  All auto-repair options failed and caused other BSoDs, and I had to do a System Restore to get it back to normal.

Definitely pause this update!

Reply | Quote

Blue screen of death (STOP error) information in dump files. (nirsoft.net) Run that tool please? BSOD are typically driver related.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

deuxbits, oldfry

Reply | Quote

I attached the report.  That’s the only Dump File that shows though, which was right around the time my System Restore completed, so I’m not sure if that file is related or was overwritten by the restore.  Just doing a Google search for KB5013943 yields quite a few users with the same issues, or worse.

Reply | Quote

Quick update.  I decided to roll the dice and try re-installing the update.  It failed again, gave me a BSoD, and then restarted into the Recovery Options Menu, and when I selected “Restart my PC”, the install completed and was successful.  So today, the restart option worked and all updates shows as successfully installed.

And then I restarted my laptop once more just to make sure it was good, and it’s now in the same BSoD loop as yesterday.  So much for the update installing successfully.  I had to do another System Restore to undo the update, which I have paused again, and will not be re-trying for a few weeks.

 

Reply | Quote

If you have fast restart turned on the “restart” from the power options is a complete restart like reb00t used to be. Re-boot is not the same. The system state is saved and restored while the user “stuff” is from scratch. Fast startup has been known to cause all manner of weird things to happen.

If you have an SSD a cold restart is much less painful than it used to be although it does take longer than a reboot with fast startup enabled. If something strange happens on a Win10 or Win11 machine I’m on, that is one of the first things I check. If it is on I turn it off and see if the situation is resolved.

--Joe

1 user thanked author for this post.

deuxbits

Reply | Quote

I found the issue.  On this laptop, I am running Sophos Home Edition Antivirus, and their “Hit Man Pro” driver had a conflict with this update.  Sophos released an update, and after that I was able to properly install KB5013943.  Sophos Link:

FIXED- Windows 11 Bluescreen/stop error after Windows Update KB5013943 – Sophos Home Help

2 users thanked author for this post.

Deo, lmacri

Reply | Quote

I just read this article on Ghacks relating to KB5013943 and Win 11. It basically says the update may cause apps to crash, fail to open, or have other issues on affected devices. Just thought I would let folks who have Win 11 know about it. I also wonder if KB 5013942 for Win 10 21H2 might have the same impact. Anyone know?

Peace, CAS

1 user thanked author for this post.

lmacri

Reply | Quote

no issues/problems so far with KB5013942 on Win10 20H2/21H1/21H2 – I usually check the Ten Forums site if Win10 users encountered problems but so far, vast majority of them had no problems with KB5013942

2 users thanked author for this post.

deuxbits, CAS

Reply | Quote

No just Windows 11.  Note that Microsoft is not going to pull the patch it will fix itself if it sees that you are having issues with the update.  There’s something called “known issue rollback” that will undo the part causing the issue.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

CAS

Reply | Quote

For Windows 11 KB5013943 error fix:
https://www.yourwindowsguide.com/2022/05/fix-apps-not-working-after-installing-kb5013943.html#.Ynuts0xBy3A

Source:
https://answers.microsoft.com/en-us/windows/forum/all/cumulative-updates-for-windows-10-and-windows-11/6d7fccc6-e125-4ae4-9fbb-db7077065c31

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

Reply | Quote

Born’s Tech on Windows 11, KB5013943 fix:
https://borncity.com/win/2022/05/11/windows-11-update-kb5013943-erzeugt-fehler-0xc0000135/#more-24437

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

1 user thanked author for this post.

lmacri

Reply | Quote

2 Windows 10 Home v21H2 systems (one x64 and another x86 system)
————————————————————————
Macrium Reflect System Image backup completed. Resumed updates via Windows Update and installed the following:
-2022-05 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64 (x86) (KB5013624)
-Windows Malicious Software Removal Tool x64 (x86) – v5.101 (KB890830)
-2022-05 Cumulative Update for Windows 10 Version 21H2 for x64 (x86)-based Systems (KB5013942)

Windows Update installed the CU .NET Framework (KB5013624) first and duly prompted for a restart. The other 2 patches were held under the status “Pending Download” due to the “metered connection” status. After the restart, Windows Update
proceeded to download and install the other 2 patches after I hit the “Download” button.

New OS Build 19044.1706

1) Scanning and printing via USB cable to local printer are working. No network printing here.
2) Passed both DISM, SFC and CHKDSK checks before and after patching.
3) So far nothing untoward to report. No application errors. Both Windows 10 Home systems are running stable since patching 12 hours ago.

HTH.

3 users thanked author for this post.

deuxbits, WCHS, CAS

Reply | Quote

FYI,

Reports are coming in of Application Errors resulting from Windows 11 21H2 Cumulative Update KB5013943 for 10May2022:

Neowin – Windows 11 Patch Tuesday KB5013943 causing BSODs, black screen, buggy Teams, Discord
——–
https://www.neowin.net/news/windows-11-patch-tuesday-kb5013943-causing-bsods-black-screen-buggy-teams-discord/

Ghacks – May 2022 Windows 11 update KB5013943 may break apps
————————————————————
https://www.ghacks.net/2022/05/11/may-2022-windows-11-update-kb5013943-may-break-apps/

Born’s Tech And Windows World – Windows 11: Update KB5013943 results in application error 0xc0000135
———————-
https://borncity.com/win/2022/05/11/windows-11-update-kb5013943-erzeugt-fehler-0xc0000135/

HTH.

3 users thanked author for this post.

lmacri, deuxbits, Alex5723

Reply | Quote

Kudos to everyone who posted about this Win 11 app error 0xc0000135 that appeared on some machines after the May 2022 Patch Tuesday.

Multiple Win 11 users with Dell computers who installed KB5013942 (OS Build 22000.675) started seeing this error 0x0000135 when they tried to run or install Dell SupportAssist – see piotrekDell’s 11-May-2022 Application Installation Error 0x0000135. The problem was solved after they re-enabled the MS .NET Framework 3.5 through the Windows Control Panel as instructed in Gunter Born’s Tech and Windows World blog Windows 11: Update KB5013943 Results in Application Error 0xc0000135.
———————
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676

1 user thanked author for this post.

oldfry

Reply | Quote

Hi Everyone.  Anonymous here.

After I installed the SSU for Windows 8.1 yesterday, it showed up in the Windows Update list today (the only one).  I hid it. No point in installing it twice. Did Microsoft forget something?

I wish that updating wasn’t so complicated….

 

Reply | Quote

A first for me so This just an FYI for YOUR rare future repeat …. A guy in TenForums posted what happened to me. After MSRT and NetFrmwk processed (SSU inst’d in background) I saw — Re-Start Now — offered and didn’t pay attention to — Or Re-Start LATER. I Clk’d Re-Start and after May’s CU failed to show as Inst’d I went back to Update page to see the CU at 44% and it continued to Finish. All is well and Lesson Learned.. No idea WHY Re-Start was offered prematurely……

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / HP Envy Desk-Ethernet - SSD-HDD/ i5(8th Gen) 12GB / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU=0

1 user thanked author for this post.

deuxbits

Reply | Quote

Whenever there is a Net update, it will trigger a Restart request as soon as its installation completes.

It is up to you to keep an eye on things to avoid a Restart during the CU installation. Having experienced this once, I watch for all updates  Awaiting restart before clicking on Restart now.

Regards, Phil

1 user thanked author for this post.

deuxbits

Reply | Quote

CraigS26 wrote:

No idea WHY Re-Start was offered prematurely……

It happens all the time.
Dump Windows update and use WUmgr instead.

1 user thanked author for this post.

CraigS26

Reply | Quote

Windows 10 Pro 21H2.

Using WUmgr.

kb5014329 .net 5.0.17
kb890830 MSRT
kb5013624 .net 3.5, 4.8
kb5013942 CU

Manually update .net 6.0.5 (no Windows updates for .net 6..)

New step after second restart : Cleaning Up.

All is well.

2 users thanked author for this post.

jburk07, WCHS

Reply | Quote

I have updated (so far) without problems:
2x Win10 21H2 (KB5013942 CU, KB5013624 .NET 3.5, 4.8, KB890830 MSRT)
2x Win8.1 (KB5014011 Rollup, KB5013870 .NET Rollup, KB890830 MSRT, then KB5014025 SSU)
1x Win11 on ARM Insider Beta to Build22616.100 (KB5014650)

5 users thanked author for this post.

jburk07, Speccy, deuxbits, Fred, DrBonzo

Reply | Quote

Update:
Additional successful installations
1x Win10 21H2 (KB5013942 CU, KB5013624 .NET 3.5, 4.8, KB890830 MSRT)
2x Win7 SP1,1 Pro, 1 Home Premium (KB5014012 Rollup, KB5013637 .NET 3.5.1 using W7ESUI and KB5013632 .NET 4.8 using dotNetFx4)

1 Win8.1 Pro and 1 Win10 Pro 21H2 remaining.

3 users thanked author for this post.

jburk07, DrBonzo, SueW

Reply | Quote

Confirming the NPS issues.  We have two NPS proxy servers backed by NPS on three DCs.  Patched the DCs and started having issues with a VPN product that authenticates with computer certificates.  Rolling back now…

Reply | Quote

https://twitter.com/SteveSyfuhs/status/1524570912275587072 FYI we’re aware of the NPS issue. It’s not related to NPS specifically but rather with how we’re distinguishing between different kinds of names in the certificates. Only a subset of folks are affected by this.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I had the SSU (KB5012599) install without authorization – network connection set to metered on W10 home 21H2. Only discovered it when the restart message appeared. All other updates wait for me to initiate.

cheers, Paul

Reply | Quote

KB 5012599 is not an SSU is it? It’s the April CU.

1 user thanked author for this post.

deuxbits

Reply | Quote

From the MS site: https://support.microsoft.com/en-us/topic/april-12-2022-kb5012599-os-builds-19042-1645-19043-1645-and-19044-1645-548cc67c-7f12-46fd-878e-589ba81ac2f5

Windows 10 servicing stack update – 19042.1613, 19043.1613, and 19044.1613

cheers, Paul

1 user thanked author for this post.

deuxbits

Reply | Quote

That’s the April cumulative update – SSUs are part of /embedded into the CU.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

DrBonzo, deuxbits

Reply | Quote

From somewhere in the past, can’t produce the source, I recall something about the Metered Connection stopping larger downloads, but not smaller ones (SSUs are usually small). There was a maximum data size limiting setting in the Metered setup. Haven’t looked if it’s still there b/c I never use Metered Connections with my Win10 Pro.

1 user thanked author for this post.

DrBonzo

Reply | Quote

I read that, too, somewhere. My experience with a Win 10 Home computer that I got stuck maintaining last December is that setting metered connection to “on” has no effect at all on update downloads!

The computer was up to date when I got it – I checked – just before December’s patch Tuesday, and after checking that I turned metered connection on. Turned the computer on a few days later and it was immediately downloading the December updates. After that I now pause updates for at least 2 weeks after a given patch Tuesday. That has worked so far.

Reply | Quote

This confirms your recollection – Metered connections in Windows (microsoft.com). But, does not offer any numbers.

Also see Metered Internet connections: FAQ (microsoft.com)

--Joe

1 user thanked author for this post.

DrBonzo

Reply | Quote

OK, Don’t know if it will help, but here’s the info I was referring to:
Settings\Network&Internet\Status (Ethernet or WiFi, whatever you are using).
Under Properties, Set Metered Connections = ON

choose Data Usage

 

 

1 user thanked author for this post.

DrBonzo

Reply | Quote

Interesting. When I turned metered connection “off” I did it from Settings —> Security and Updates. I don’t have the Win 10 computer available to me right now, so I may not have the terminology quite right, but the metered connection toggle was on the same page as where you can pause updates, or perhaps under advanced settings near where you can set a date to resume updates. I did not toggle it off from Network Status settings. The way I did it seems to have no effect on anything!

Reply | Quote

The Download updates over metered connections (extra charges may apply) toggle in Settings> Update & Security > Advanced options determines whether Windows is “allowed” to download updates over a metered connect, not whether your connection is actually metered.

To set a connection as metered, open Settings > Network & Internet, click the Properties button in the Status section in the right-hand pane and turn on the Set as metered connection toggle.

Note: these 2 setting are directly related (i.e. if you set your connection as metered you also must turn off the download over metered connection toggle to stop update downloads.)

If you also want to set a specific “data limit” for your metered connection, Settings > Network & Internet, click the Data usage button in the Status section, click the Enter limit button in the right-hand pane and then enter your particular limit.

Note: 0.1 MB is the lowest setting it’ll accept so any update that’s less ~103 KB will still be automatically downloaded.

2 users thanked author for this post.

DrBonzo, WCHS

Reply | Quote

BleepingComputer reporting:
Windows 11 KB5013943 update causes 0xc0000135 application errors

https://www.bleepingcomputer.com/news/microsoft/windows-11-kb5013943-update-causes-0xc0000135-application-errors/

Reply | Quote

This Windows 11 preview information was presented on Bleeping Computer on May 4, 2022:
https://www.bleepingcomputer.com/news/microsoft/microsoft-windows-11-kb5012643-update-will-break-some-apps/

The KB5013943 update was released May 10, 2022 with the same problem.

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

Reply | Quote

The following May 2022 Patch Tuesday updates were installed successfully on my Win 10 Pro v21H2 laptop by Windows Update today and I haven’t noticed any negative effects so far:

• KB5013942: 2022-05 Cumulative Update for Win 10 v21H2 (OS Build 19044.1706)
• KB5013624: 2202-05 Cumulative Update for .NET Framework 3.5 and 4.8 for Win 10 v21H2
• KB5014329: 2202-05 .NET 5.0.17 Security Update for x64 Client
• KB890830 : Windows Malicious Software Removal Tool x64 – v5.101

The only glitch I noticed in the Windows Update process was the same I reported in post # 2439606 for last month’s April 2022 Patch Tuesday that often occurs when I have more than one update that requires a Windows restart to complete installation. As soon as KB5013624 (Cumulative Update for .NET Framework 3.5 and 4.8) finished installing and the status of the update changed from “Installing” to “Pending Restart” I was immediately prompted to “Restart Now” before KB5013942 (the May 2022 Cumulative Update for Win 10 v21H2 / OS Build 19044.1706) had finished installing – see attached image. This glitch isn’t an issue for me since always monitor the progress of my Patch Tuesday updates at Settings | Update & Security | Windows Update and don’t restart until all updates have finished installing but this might cause problems for others who use rely on Windows Update instead of using a third-party update manager like WuMgr.

———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676

3 users thanked author for this post.

jburk07, DrBonzo, WCHS

Reply | Quote

lmacri wrote:

The only glitch I noticed in the Windows Update process was the same

Let me see if I get this straight. You did not click on the ‘Restart Now’ in the black-box notification from the Action Center in the bottom right-hand corner. Instead, you let it keep installing the other updates –your screenshot shows that it’s started installing KB5013942 (21% of it), and you let it just continue until all of them are installed. Right?

I wonder how WU handles this if one has GP=2 (notify download/install), which issues a ‘download’ button for the downloading and installation. If I recall, even though one has unhid all 4 that you list here so that WU can find them in the queue, there is only one download button (and not four buttons). I am guessing that after clicking that one ‘download’ button, the WU screen is going to look like yours … but, as you advise, wait until all of them are listed as having been installed. And, only then, if you do not want to wait until “outside active hours”, do you click on grey-box “Restart now” in the WU display. Right?

1 user thanked author for this post.

DrBonzo

Reply | Quote

I use GP=2 and can confirm that clicking the Download starts the download and install for all the listed updates in the queue.

If there is a .NET update, it will trigger a Restart request as soon as its installation is complete, as described above. Like lmacri, I monitor the updates until all are installed or “Pending restart” before clicking “Restart now”.

If you restart immediately after the .NET update triggers it, you will, at best, waste time waiting for the reboot and a new download and install of the interrupted CU (BTDT). Less fortunate others have borked their systems by doing this, depending where the CU was interrupted.

Regards, Phil

2 users thanked author for this post.

WCHS, mulletback

Reply | Quote

Hi WCHS:

I have tweaked a few Windows Update settings in my Win 10 Pro Group Policy Editor but my Automatic Updates setting still has its default configuration [i.e., Local Group Policy Editor (run gpedit.msc) | Computer Configuration | Administrative Templates | Windows Components| Windows Update | Configure Automatic Updates is not configured and uses 3 = (Default Settings) Download the updates automatically and notify when they are ready to be installed]. I normally defer my Patch Tuesday Updates by choosing a specific date at Settings | Update & Security | Windows Update | Advanced Options | Advanced Options | Pause Updates | Select Date. Once my Patch Tuesday updates start (I can tell because the fan on my Dell Inspiron is so loud :-)) and all the available updates finish downloading (status = Pending Install) the process pauses and waits for me to click the Install Now button shown below to start the installation.

When the Restart Now button appears I wait until all available updates have finished installing (i.e., until the status of every update that requires a restart has changed from “Installing- xx %” to “Pending Restart“). Once that happens I go ahead and click one of the Restart Now buttons shown in my image in post # 2446200 .  It doesn’t matter if I choose the Restart Now button at Settings | Update & Security | Windows Update or the Restart Now button in the grey pop-up notification from the Action Center as long as I’ve confirmed that all the updates have actually finished installing.
—————
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676

1 user thanked author for this post.

WCHS

Reply | Quote

lmacri wrote:

The following May 2022 Patch Tuesday updates were installed successfully on my Win 10 Pro v21H2 laptop by Windows Update today and I haven’t noticed any negative effects so far:
KB5013942: 2022-05 Cumulative Update for Win 10 v21H2 (OS Build 19044.1706)
KB5013624: 2202-05 Cumulative Update for .NET Framework 3.5 and 4.8 for Win 10 v21H2
KB5014329: 2202-05 .NET 5.0.17 Security Update for x64 Client
KB890830 : Windows Malicious Software Removal Tool x64 – v5.101

This quote is from Imacri’s May 13 post.
I am Win10/Pro 21H2
I hid these 4 patches on May’s Patch Tuesday (May 11) with WUSHOWHIDE, and today (May 29), I noticed that KB5014329 was no longer there. I unhid the other 3 and installed them with no problem.

What happened to KB5014329: .NET 5.0.17 Security Update for x64 Client??

Reply | Quote

Microsoft : You might see authentication failures on the server or client for services

After installing updates released May 10, 2022 on your domain controllers, you might see authentication failures on the server or client for services such as Network Policy Server (NPS), Routing and Remote access Service (RRAS), Radius, Extensible Authentication Protocol (EAP), and Protected Extensible Authentication Protocol (PEAP). An issue has been found related to how the mapping of certificates to machine accounts is being handled by the domain controller.

Note: Installation of updates released May 10, 2022, on client Windows devices and non-domain controller Windows Servers will not cause this issue. This issue only affects installation of May 10, 2022, updates installed on servers used as domain controllers.

Workaround: The preferred mitigation for this issue is to manually map certificates to a machine account in Active Directory. For instructions, please see Certificate Mapping…

Affected platforms:

​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2..

1 user thanked author for this post.

blackbox

Reply | Quote

Win10/Pro 21H2 here. 19044.1645 (April)
I’m not on the May updates yet, but the new “Search Highlights” feature showed up this morning. Clicking in the Search box to the far right (over the ‘celebration’ image) brings up recently accessed Apps b/c right-click on Taskbar or Search Box > Search has both ‘Search Highlights’ and ‘Open on hover’ turned on. When ‘Search Highlights’ is turned OFF, the ‘celebration’ image disappears from the Search Box, although it is still checked at Taskbar > Search.

I don’t see anything about birthdays, significant past events of the day, etc yet.

Reply | Quote

Help for Windows 8.1 x64 folks out there – updated, no issues so far:

1. Keep in mind there’s a new SSU this month, thus manually download KB5014025 first, install it and reboot (for good measure).
2. Let Windows Update install KB5014011 (or manually download it from the MS Catalog and install).

Now here’s an additional tip for Windows 8.1 (eventually applicable to Windows Server 2012 R2) folks: if the monthly update fails to install with cryptic errors such as 0x80070002 (WIN32: ERROR_FILE_NOT_FOUND) there might be a good, but less-known reason for that. Keep reading.

You see, some people choose to “customize” their %ProgramData%\Microsoft\Windows\Start Menu\Programs folder by moving some of the system shortcuts from their default locations (for e.g. grouping them all into a ‘Windows’ sub-folder) and create a ‘Programs’ toolbar on the taskbar: it might look weird to do that but it is, in fact, a very simple, but handy way to have your shortcuts at hand, similarly to having the Windows 7 “Start” button, just by using the system resources (without any need for additional software).

Problem is, the setup installers “expect” some, if not most system shortcuts to be present in their default locations: if they aren’t, installation might fail and throw those cryptic errors. This is a rather common cause of installation failures for Windows 10 (therefore, a quick and dirty way of preventing those “errors” from happening, if you knew that in advance, would simply be to move back the system shortcuts to their default locations, install the update and restore the system shortcuts back to your customized locations) – one that didn’t affect or manifest itself on Windows 7/8.x until very recently and something that people typically “fix” (blindly and unaware exactly of “why” it works) by “restoring the system health” with a dism /Online /Cleanup-Image /RestoreHealth command (or, in Windows 7, with a sfc /scannow command).

Thus, to sum things up: if you happen to experience trouble updating your Windows 8.1 (and, eventually Server 2012 R2) systems, the fail-safe approach is usually to manually update:

1. Confirm that your system shortcuts at %ProgramData%\Microsoft\Windows\Start Menu\Programs are all there, at their default locations (if they aren’t, move them back there or restore them with a dism /Online /Cleanup-Image /RestoreHealth command);
2. Download KB5014025 (the latest SSU) and KB5014011 (2022-05 monthly update) from MS Catalog.
3. Install KB5014025 (the latest SSU) first. Reboot afterwards (you don’t have to, but just in case – for good measure).
4. Install KB5014011 (2022-05 monthly update) and reboot.

Additionally (depending on your system configuration, preferences and needs) you might also let Windows Update install (and/or manually download and install yourself) the KB890830 (MSRT) and KB5013870 (.NET Rollup) updates.

Hope it helps. 😉

3 users thanked author for this post.

Steve, abbodi86, DrBonzo

Reply | Quote

A better idea than moving shortcuts and remembering to put them back is to simply copy them. Sometimes the copy will stop working and will need to be re-copied, but because the original stays right where it is expected to be: no other problems!

I’ve been doing this for years, starting with W7. I effectively have my own cascading start menu in a Toolbar I built myself, which is exactly what you are suggesting apart from the moving shortcuts bit and the fact I have multiple folders in the Toolbar.

2 users thanked author for this post.

Speccy, WCHS

Reply | Quote

The whole point of moving the shortcuts merely reflected my own, personal preference – one way to keep things “clean” (like you, I too prefer to have shortcuts organized into multiple sub-folders, having no shortcuts at all at the “root” level) but I hear you: you have a very good point there – and yes, it is actually a much better suggestion than my (somewhat clumsy) approach.

Indeed, it is probably better to leave the original system sub-folders and shortcuts quiet and alone at their default, predefined locations and just hide them (with an attrib +H <folder> or attrib +H <shortcut> command, from an elevated prompt) so that they won’t appear (be visible) in your customized toolbar – and make copies of those items you want to use into your customized toolbar. Something (roughly) like this:

cd %ProgramData%\Microsoft\Windows\Start Menu\Programs
mkdir Windows
xcopy /E /I Accessibility Windows\Accessibility
xcopy /E /I Accessories Windows\Accessories
xcopy /E /I “Administrative Tools” “Windows\Administrative Tools”
xcopy /E /I “System Tools” “Windows\System Tools”
xcopy /E /I “Windows PowerShell” “Windows\Windows PowerShell”
attrib +H Accessibility
attrib +H Accessories
attrib +H “Administrative Tools”
attrib +H “System Tools”
attrib +H “Windows PowerShell”
attrib -H *.lnk
xcopy *.lnk Windows
attrib +H *.lnk

Visually, it works like a charm… Next month I’ll let you know if it also works out well and allows the monthly updates to install flawlessly in those few Windows 8.1 legacy systems I’m maintaining. Thanks for the tip! 😉

Reply | Quote

I may be a bit confused here, so bear with me.

I have an Opera icon and a Firefox icon in the left part of the task tray. I don’t consider those icons to be shortcuts – there’s no bent arrow superimposed on them and they don’t require double clicks. Are you saying I need to make sure those icons (shortcuts?) in my taskbar are also still in the ProgramData\…\Programs folder?

I have a real shortcut (bent arrow and requires double click) icon for Firefox on my desktop. Do I need to make sure it’s still in the ProgramData\…\Programs folder as well?

Finally, what if the icons are in both places? Do I need to get rid of the task bar icons before I install the updates?

Thanks.

Reply | Quote

No, we’re just talking about the predefined (Windows) system folders and shortcuts (see above).

1 user thanked author for this post.

DrBonzo

Reply | Quote

Windows 10 Pro

Installed the Windows CU (KB5013942), .NET CU (KB5013624), and the MSRT (KB890830) using the PSWindowsUpdate module in PowerShell. All is well.

Reply | Quote

Win 10 Pro 21H1 64 bit.  Installed May CU KB5013942 with WUMgr, installed OK, and stable on 1 machine for 3 days.

Reply | Quote

new Win10 out-of-band updates released Thursday afternoon May 19 after 2pm pacific local time:

KB5015020 for Win10 20H2/21H1/21H2:
https://support.microsoft.com/help/5015020

KB5015018 for Win10 LTSC 2019 1809:
https://support.microsoft.com/help/5015018

KB5015019 for Win10 LTSB 2016 1607:
https://support.microsoft.com/help/5015019

I think Win7, 8.1 & Server 2008/2012 variants also got similar out-of-band updates as well

1 user thanked author for this post.

Alex5723

Reply | Quote

See the home page, master patch list updated as well.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

KB5014987 for Win 7
https://support.microsoft.com/help/5014987

KB5014986 for Win 8.1
https://support.microsoft.com/help/5014986

2 users thanked author for this post.

Steve, Fred

Reply | Quote

WCHS wrote:

… I unhid the other 3 and installed them with no problem. What happened to KB5014329: .NET 5.0.17 Security Update for x64 Client??

Hi WCHS:

I have no idea, since your post # 2439948 in CAS’ How to Uninstall KB5013354 ‌indicates that you received KB5013354 (2022-04 .NET 5.0.16 Update for x64-based Systems) when you installed your April 2022 Patch Tuesday Updates.

The May 2022 KB5014329 update for .NET 5 (.NET v5.1.17) is still posted in the Microsoft Update Catalog at https://www.catalog.update.microsoft.com/Search.aspx?q=KB5014329 and as far as I know it hasn’t been pulled from the Windows Update servers. The “Out of Support Versions” section at https://dotnet.microsoft.com/en-us/download/dotnet shows that .NET 5 is no longer supported as of 10-May-2022 and that v5.0.17 (rel. 10-May-2022) was the last release for .NET 5, so perhaps initially hiding the KB5014329 update with wushowhide caused some odd glitch with Windows Update.
—————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v101.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1689 * Macrium Reflect Free v8.0.6758

Reply | Quote

Hi Imacri,
Yes, your steel-trap mind is on spot!! — I installed KB5013354 2022-04 .NET 5.0.16 Update for x64-based Systems after unhiding it along with the other April Patch Tuesday updates on May 1. I figure that’s why the superceding KB5014329 2022-05 .NET 5.0.17 was in the WU queue on May 10 (May Patch Tuesday).

I did notice that https://dotnet.microsoft.com/en-us/download/dotnet shows that .NET 5 is no longer supported as of 10-May-2022 and that v5.0.17 (rel. 10-May-2022) was the last release for .NET 5. But, nevertheless, though out of support, it WAS in the WU queue on May 10.

5.0.17 is a security update and it seemed to me that it would be important to get this installed. So, I went to the MS Catalog for KB5014329, but I didn’t know which of the 18 links under the download button to click on. See the attached MS Catalog KB5014329 downloads.JPG. But, I knew that it is out of support now, so, I figured that sooner or later, I would find .NET 6.0.x in the WU queue.

Now comes the BIG surprise. I just now ran ASoft .NET Version Detector 21 R1 in order to see if there was enough information about 5.0.16 to make the correct download selection in the MS Catalog listing. It tells me that 5.0.17 is already on my system!! See the attached
ASoft .NET Version Detector 21 R1 results-May 31, 2022.JPG.

And then I checked Apps & Features and discovered that it had been installed 11 days ago, on May 20, 2022!! I have no idea how it was installed. I never saw it in the WU update queue to download and install (I have GP=2 download/install). And I never downloaded it. I have no idea what app might be needing whatever is the current version of 5.0.x. Some time ago, 5.0.14 suddenly appeared on my system (I never installed it myself and it is not listed in WU History). After that, I installed 5.0.15 and 5.0.16 after these updates appeared in the WU queue. But, I was aware that these were downloading and installing and they show up in WU History. But the installation of 5.0.17 is a mystery (as was the installation of 5.0.14).

I checked the Reliability Monitor (Control Panel | All Control Panel Items | Security and Maintenance |Reliability Monitor), and indeed there is a record on May 20 of 5.0.17 being installed and 5.0.16 being removed. See the attached Reliability monitor May 20, 2022 – from Paint resized.JPG. Evidently, something called Microsoft .NET Host FX Resolver kicked to do the removal of 16 and the installation of 17, unbeknownst to me.

Do you (or anyone else) know of whether it’s possible to track this down?… how did the removal of 5.0.16 and the installation of 5.0.17 come about? Is it possible to find out what precipitated 5.0.17 – perhaps some indication of the app that needed it? I know there’s something called the Event Viewer for checking on when (and perhaps how) some action occurred, but I don’t really know how to use it for this purpose, (i.e., if it would tell me what made it happen).

And Question #2: Should I be expecting .NET 6.0.x to be appearing in the WU queue sooner or later? Or alternatively, will 6.0.x be surreptiously installed (as happened with 5.0.14 and 5.0.17) whenever whatever app decides it needs it?

Reply | Quote

Hi WCHS:

As I noted in CAS’s 13-Apr-2022 How to Uninstall KB5013354, I have no idea why KB5013354 (.NET 5.0.16 Runtime for x64 Client) was pushed out to my system by Windows Update when I installed my April 2022 Patch Tuesday updates on 15-Apr-2022. According to my Windows Update history April 2022 was the first time a .NET 5.x Runtime Client was installed on my machine (which seemed odd to me at the time since .NET 5 was scheduled to reach end of support on 10-May-2022) and as far as I know I have no software on my system that requires .NET 5.x. I originally suspected it might be required by Dell SupportAssist v3.10.4 (since it has built-in hardware diagnostics) but the system requirements <here> say that utility requires .NET Framework v4.7.2 (“NOTE: If you do not have Microsoft .NET Framework 4.7.2, SupportAssist installs the latest Microsoft .NET Framework on your PC“).  In theory I could uninstall my current .NET Runtime v5.0.17 from Control Panel | Programs | Programs and Features and if it’s really required by an installed program it should be downloaded the next time I launch that program, but for now I’m just leaving the .NET 5 Runtime installed until I can figure out if there’s some way to trace if .NET 5 is actually being used on my machine (e.g., using Process Explorer to look for child threads associated with .NET 5 being called by a newly launched .exe parent process).

Just FYI, my Windows Reliability Monitor logged similar entries for the removal of .NET v5.0.16 components when .NET v5.0.17 was installed by Windows Update along with my other Patch Tuesday updates on 13-May-2022 (see attached image).

According to Sky’s 15-May-2022 post # 2447030 in Microfix’s Various .NET Frameworks EoS Date the .NET v5.x and 6.x updates (unlike the .NET Framework updates) are delivered via Microsoft Update and are only installed by Windows Update if you have “Receive updates for other Microsoft products when you update Windows” enabled at Settings | Update & Security | Windows Update | Advanced Options | Update Options (which I do). If I’d left that option disabled I suspect I would have never gotten KB5013354 (.NET 5.0.16 Runtime for x64 Client) installed in April 2022 in the first place.

As Paul T noted in post # 2450219, if you install a program that requires the .NET 6 Runtime and it’s not already installed it should be automatically pushed out to your machine.  I know very little about the newer .NET runtimes but I’m guessing they are similar to the “classic” .NET Frameworks where you can have more than one version installed at the same time (e.g., .NET Framework v3.5 and .NET Framework v4.8), so I wouldn’t expect .NET 5 to be automatically “upgraded” to .NET 6 just because .NET 5 reached end of support on 10-May-2022.
————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v101.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1689 * Macrium Reflect Free v8.0.6758

1 user thanked author for this post.

WCHS

Reply | Quote

lmacri wrote:

I originally suspected it might be required by Dell SupportAssist v3.10.4 (since it has built-in hardware diagnostics) but the system requirements say that utility requires .NET Framework v4.7.2 (“NOTE: If you do not have Microsoft .NET Framework 4.7.2, SupportAssist installs the latest Microsoft .NET Framework on your PC“).

Hi Imacri,

Thinking of possibilities, based on what I see on my Dell 7569:

1.  I use SupportAssist (3.10.4). The  “Automatic scanning and performance optimizations” setting is turned off.  The only scanning I do is “Get drivers and downloads” and that is a manual operation. I don’t have .NET Framework v4.7.2.  I have .NET FW 2.0, 3.0, 3.5, and 4.8.   But, despite the description in the quote, maybe it is installing .NET (Core) 15.0.17  (i.e., Microsoft.NETCore.App 5.0.17).However, I did not do any manual scanning on May 20, so it appears that the May 20 installation of 5.0.17 could not have been triggered by one of the Home page SupportAssist diagnostics, since no SA diagnostic option was selected on that date.
2. I have SupportAssist | Settings | System Diagnostics | System Repair turned on.  As you know (from all our past discussions of this on the Dell community forum) System Repair triggers “Successful application reconfigurations” daily (and as many as 3 times daily and for each time the same application might be reconfigured more than once)–all documented in the Reliability Monitor.  So, maybe it’s possible that this triggered the installation of 5.0.17.   Do you have System Repair turned on?  I think I remember your saying on the Dell community forum that you had finally decided to turn it off, but I wanted to ask here because that might be a variable that is similar to or different from our two machines.
3. The only other App that was installed on May 20 is a new version of Microsoft Edge (101.0.1210.53).  I rarely use Microsoft Edge and this current version on my machine is an old one, since Edge updates only if opened and I haven’t used it since May 20.  But, if I understand Paul T’s response <here>, only non-Microsoft applications would trigger a .NET update, if needed, and Edge is a Microsoft Product.

Reply | Quote

Hi WCHS:

The .NET Framework 4.5 and higher are backwards compatible with apps built with earlier versions of the .NET Framework (see the MS support article <here>), so if you have .NET Framework v4.8.x then you shouldn’t need .NET Framework v4.7.2 installed separately.

I have System Repair disabled in SupportAssist v3.10.4. In fact, I disabled both services for Dell SupportAssist and Dell SupportAssist Remediation at Start | Windows Administrative Tools | Services a few months ago so that neither of these programs can automatically start at boot-up . On rare occasions I will start SupportAssist manually and run a “Get Drivers & Downloads” check from the Home tab if I think that Dell Update v4.x is recommending a software or driver update that isn’t appropriate for my Service Tag, and when I do that SupportAssist runs an auto-check for an available update for the SupportAssist program.

I’ve gone back through my notes and recall that there are some Dell users with higher-end XPS and Alienware laptops who are starting to receive newer (and undocumented) SupportAssist v3.11.x and v3.12.x updates that fail to install correctly. I don’t know if an upcoming version of Dell SupportAssist requires a .NET (Core) v5.x or v6.x Runtime, but see my 02-Jun-2022 post in crimsom’s 17 R5, SupportAssist v3.10.4 Blue Screen (who discovered they actually have SupportAssist v3.11.1.18 listed at Control Panel | Programs | Programs and Features) in the Dell forum for further details. That post includes a comment about BruceSJ’s 20-May-2022 thread AutoUpdate Issues UAC Prompt to Install .NET 5.0.14 where he states that that his XPS 8930 / Win 10 Pro v21H2 machine displays a prompt to install the .NET v5.0.14 Runtime every time the automatic Dell SupportAssistAgent AutoUpdate task is run by the Task Scheduler. For some reason that Task Scheduler task repeatedly fails to run to completion on my Inspiron 5584, but that might be because the Dell SupportAssist service is currently disabled on my system.
—————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v101.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1689 * Macrium Reflect Free v8.0.6758 * Dell SupportAssist v3.10.4.18 * Dell Update for Windows Universal v4.5.0 * Dell SupportAssist Remediation v5.5.2.16157 * Inspiron 5583/5584 BIOS v1.18.0

Reply | Quote

lmacri wrote:

I know very little about the newer .NET runtimes but I’m guessing they are similar to the “classic” .NET Frameworks where you can have more than one version installed at the same time (e.g., .NET Framework v3.5 and .NET Framework v4.8), so I wouldn’t expect .NET 5 to be automatically “upgraded” to .NET 6 just because .NET 5 reached end of support on 10-May-2022.

Anybody else want to weigh in on this?

Reply | Quote

End of support does not mean “remove and replace automatically” – at least not in other MS products, except maybe Windows.

cheers, Paul

1 user thanked author for this post.

WCHS

Reply | Quote

WCHS wrote:

how did the removal of 5.0.16 and the installation of 5.0.17 come about? Is it possible to find out what precipitated 5.0.17 – perhaps some indication of the app that needed it?

Imacri explains in her aside on July 3 at the end of her reply to @Deo at Why Runtime 5.0.x?, that SupportAssist 3.11.4.29 (rel. 23-Jun-2022) is now requiring .NET Core Runtime v5.0.x in addition to Microsoft .NET Framework 4.7.2.

So, I think that explains why v5.0.14 and then v5.0.17 were installed on my machine without my being aware of it, since I regularly use SupportAssist.

Reply | Quote

Hi WCHS:

Actually, I have no idea why Windows Update installed KB5013354 (2202-04 .NET 5.0.16 Runtime for x64 Client) during my April 2022 Patch Tuesday Updates in the first place. As far as I know I did not have any software on my Dell computer that required the .NET (Core) Runtime v5.0.x back in April 2022.  When Windows update installed the KB5014329 security update (2202-05 .NET 5.0.17 Runtime for x64 Client) during my May 2022 Patch Tuesday updates, I still wasn’t aware of any software I had at that time that required the .NET (Core) Runtime v5.0.x.

SupportAssist v3.11.4.29 was not released until around 23-Jun-2022, and a .NET (Core) Runtime v5.x was not required for the previous SupportAssist v3.10.4.18 released on 21-Nov-2021.  Compare the old v3.10.4.18 minimum system requirements <here> that only list “Microsoft .NET Framework 4.7.2” versus the new v3.4.11.29 minimum system requirements <here> that list “Microsoft .NET Framework 4.7.2 and .NET Core Runtime v5.0.14“.

At the end of the day, if Dell users want to use the new SupportAssist v3.11.4.29 to run update checks for Dell software and drivers and/or run Dell hardware diagnostics then they should leave the .NET (Core) Runtime v5.0.17 installed.   What really confounds me is why Dell would release a new SupportAssist v3.11.4.29 in June 2022 that requires a .NET (Core) Runtime v5.0.x that reached end of support on 10-May-2022 and will get no further security updates. At some point in the future Dell will release a newer SupportAssist version that requires the current .NET (Core) Runtime v6.x and we’ll have to go through this nonsense again.
———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1766 * Firefox v102.0.1 * Microsoft Defender v4.18.2205.7-1.1.19300.2 * Malwarebytes Premium v4.5.11.202-1.0.1716 * Macrium Reflect Free v8.0.6867 * Dell SupportAssist v3.11.4.29 * Dell Update for Windows Universal v4.5.0

2 users thanked author for this post.

WCHS, oldfry

Reply | Quote

Hi Imacri,
I know what you are saying about the release date of v 3.11.4.29 on June 23 and Dell’s announced requirement for .NET 5.0.x for that version. But, it’s quite possible (in my opinion in my case because I use SupportAssist) that the earlier version of SupportAssist (v3.10.4.18 (my upgrade was Nov 20, 2021) started requiring .NET 5.0.14 sometime after Nov 20, quite possibly when a new SupportAssist OS Recovery Tools was installed (for me on Feb 18, 2022) or when a new SupportAssist-OS-Recovery-Plugin for-Dell-Update was installed (for me 5.5.1.16143 on March 22, 2022). And after 5.0.14, upgrades to later versions ensued.

I say this because Dell is notoriously late in posting new information on its support pages!! For example, in my e-mail, I get Dell’s Technical Updates about the availability of new drivers for my machine, but Dell’s support page does have them listed at the time of the Technical Update. It takes about two weeks more for the new driver to appear on the Dell support list of driver updates for my machine and for it to appear in SupportAssist and Dell Update.

Why both SupportAssist and Dell Update? I use both apps to get driver information, although I do the updating with SupportAssist because it keeps a running history of scans for driver downloads, a history of actual update installations, and a Restore button, if things go sideways.) But, SupportAssist does not provide a URL for driver update details nor the Dell ID for the new driver. I get that from Dell Update.

Another reason for SupportAssist and not just Dell Update? I know the overhead in using SupportAssist (and its System Repair), but I have the space for it, at least right now. I do regular backups and regular system images and I also have several copies of them in different places, but I can’t help but think that it’s a good idea to be over-prepared. Recently, I had a problem booting up (I think because I did not press the power button long enough or hard enough – it’s a small protrusion on the right edge of the laptop). SupportAssist kicked in, I chose the latest repair point, the system restarted, and everything returned to normal.

1 user thanked author for this post.

oldfry

Reply | Quote

What else did you install on the 20th?

What non-MS software do you have installed that may need .NET?

I can’t see 6 being installed unless you install something that needs it, but we don’t know what you have installed so anything is possible.

cheers, Paul

Reply | Quote