Installing the Win10 1903 second Sept cumulative update, KB 4522016, prevents installation of .NET 3.5

Topic

New Reply

Looks like our Keystone Kops patches are turning into bumper cars. You may recall that MS has released “optional non-security” third monthly cumulativ
[See the full post at: Installing the Win10 1903 second Sept cumulative update, KB 4522016, prevents installation of .NET 3.5]

Reply | Quote

Replies

.NET Framework downloads are here:
https://dotnet.microsoft.com/download/dotnet-framework

Carpe Diem {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.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

Reply | Quote

[Zaphyrus]

didn’t think patches could get worse, but the more I see this news, the more I am conviced Microsoft is encouraging us to not install updates at all.

Just someone who don't want Windows to mess with its computer.

• This reply was modified 3 years, 6 months ago by Zaphyrus.

Reply | Quote

With new Images …. I  inst’d Net Frmwk 3.5/4.8 KB 4522738 seen in Settings History and KB 4515871 seen in Control Panel Update History that Google doesn’t even show yet. KB 4522016 was Inst’d 2 days ago (24th).

No issues so far.

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

Reply | Quote

[bbearren]

On the B side of my dual-boot I got Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903 for x64 (KB4522738).

No KB4522016 offered, yet, no issues either.

On the A side, I got that same update.

No KB4522016 offered, yet, no issues either.

Create a fresh drive image before making system changes/Windows updates, in case you need to start over!

We all have our own reasons for doing the things that we do. We don't all have to do the same things.

Computer Specs

• This reply was modified 3 years, 6 months ago by bbearren.

Reply | Quote

No KB4522016 offered

KB4522016 isn’t offered, it has to be manually installed from the catalog. I manually installed KB4522016  and happened to not have .Net 3.5 installed, so I checked if I could reproduce this bug. I could. Both the full install dotnetfx35.exe and the bootstraper dotnetfx35setup.exe don’t do anything after double clicking and approving the UAC prompt. Calling them from an administrator powershell with various flags also results in no output, and no install. No big deal for me since I didn’t need .net 3.5 in the first place. There was probably a reason they didn’t offer this update to people.

KB4522738 and KB4517211 are new today, so maybe they’ll fix the issue. I do have the cumulative update for .Net framework 3.5 and 4.8 from September 10th (KB4514359), but not the newer one from today. Since KB4522738 was released a couple days after KB4522016, maybe it will contain a fix.

Reply | Quote

Never mind, I did already have .net 3.5 installed via Windows Features, so I can’t test if this is an issue. I was surprised that it didn’t show up in the installed programs since I figured I had just about every version installed by now, so it makes sense that the only reason it’s not there is because it’s included with the OS, whoops.

Reply | Quote

Doesn’t everyone feel a little like they are in Redmond and working in the QA/QC department lately on Windows 10 issues. And the depressing  truth is that it’s been going on for some years now  with no signs of improvement and by 2023 there will be no remaining option to avoid that fate.

Oh for the days when that QA/QC was accomplished, for the most part, before any end users revived the result.

Reply | Quote