No clue how or why that extra stuff is there. That all happened when I applied the CU & rebooted.
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: Newest
-
Anonymous
2019-04-11T00:53:59+00:00 -
Anonymous
2019-04-11T00:46:17+00:00 It's Windows 10 Pro.
Out curiosity, how did you get all those extra features in there? like .Net Environment, IIS Management Services and ASP.Net 4.8? I'm using W10 Pro as well but I don't have any of those.
-
Anonymous
2019-04-11T00:35:43+00:00 Yep. The CU has totally wrecked .NET to the point where it can't currently be reinstalled. The entire "C:\Windows\Microsoft.NET" folder size is 43MB where the same folder under the Windows.old folder is jus over 700 MB!
-
Anonymous
2019-04-11T00:27:59+00:00 The repair tool doesn't work, but it does give me a "Failed" result, recommending to reinstall, which I can't do. The manual .NET installer also doesn't work.
There are more reports of others experiencing this issue appearing in the Feedback hub now.