I will see if I can replicate this fail on 18362.86.
Can't enable .NET Environment in Windows 10 1903
Well, this is a showstopper for me. I'm in the Release Preview ring & installed 1903 (18362.30) yesterday . Update went fine. No issues experienced.
Got a Cumulative Update to install today (KB4495666). Installed it & rebooted. Build is now at 18362.53. .NET framework was disabled & 90% of my applications will no longer run! In "Control Panel/Programs and Features/Turn Windows Features on or off", ".NET Environment" is unchecked. If I check it & hit "OK" it take about 10 seconds & says "Windows completed the requested changes". The .NET Environment, however, is still unchecked when I go back to "Turn Windows Features on or off" & >NET applications still don't work.
I've uninstalled all of the updates installed today (KB4495666 & KB4493478), but .NET is still utterly broken. I've read that this was an issue prior to the release of 18362 to the Release Preview ring but was supposed to have been fixed. Looks like this MAJOR bug was reintroduced with the cumulative update?
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
177 answers
Sort by: Most helpful
-
Anonymous
2019-05-01T17:37:37+00:00 -
Anonymous
2019-05-01T17:11:00+00:00 The update from 18362.1 to 18362.30 was supposed to fix this issue:
It is bad enough that this happens, but it can be replicated on any recent version of Windows, just by using DISM to uninstall .NET Features. Some features then vanish from the list shown with DISM /Online /Get-Features /Format:Table and cannot be restored apart from a total clean install. I even tried sysprep yesterday, but the Features are totally removed from the image, so cannot be enabled. An example is the Feature named NetFx3 that shows in the DISM list. It vanishes if .NET 3.5 has been removed. It should never vanish from this listing.
-
Anonymous
2019-05-01T13:51:23+00:00 I figured that this issue here might have been an one-off instance, or because of a long upgrade path, and that the same thing surely won't happen with a completely fresh install.
Guess I was wrong, guess KB4495666 is just broken all together.
It was broken, that's why they were forced to release KB4497093 to fix it
-
Anonymous
2019-05-01T13:48:36+00:00 I figured that this issue here might have been an one-off instance, or because of a long upgrade path, and that the same thing surely won't happen with a completely fresh install.
Guess I was wrong, guess KB4495666 is just broken all together.
-
Anonymous
2019-05-01T13:40:03+00:00 If you did a complete reinstall of the last
Public Release build you would not have
gotten KB4495666.
What did you reinstall?
The moment he switched to the Slow Ring he got the CU
UPDATE 4/9: We have released Build 18362.53 (KB4495666) for Windows Insiders who are currently on Build 18362.30 of the Windows 10 May 2019 Update. This update also includes security updates that come as part of the normal monthly Patch Tuesday release cycle.
The question should be: why did he switch if he didn't wanna be on the WIP anymore?