Well, nothing in this thread fixed it for me. Had to do a clean install of Windows. A whole day of work wasted.
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-29T16:26:13+00:00 -
Anonymous
2019-04-29T01:16:33+00:00 I'll check for that. Thanks.
Did this end up working for you? I was unable to try this option as mine was corrupted after applying a Cumulative Update rather than a new Windows Build. In my case, uninstalling the CU did not fix the .NET issue & I ended up having to do a clean install.
-
Anonymous
2019-04-28T02:05:47+00:00 I'll check for that. Thanks.
-
Anonymous
2019-04-28T01:37:26+00:00 Yes, I should have heeded this when I decided to use this computer for my home Automation. But, you would think Microsoft would assist on reversing this. Guess not.
There's a grace period of 10 days in which you can reverse it if you still have the Windows.old folder