Can't enable .NET Environment in Windows 10 1903

Anonymous
2019-04-10T07:18:57+00:00

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.

0 comments

177 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-04-16T03:05:34+00:00

    No none of those are there and attempting to install them results in "unknown" message.

    To replicate, I uninstalled every single Feature and then went into DISM commands and kept uninstalling with a /Remove switch to totally remove everything. Now the Features list has everything disabled.

    From the online searches I have done, difficulty reinstalling .NET features has happened in previous Windows versions and some suggest that Disabling Features was behaving as if /Remove had been used, but that the usual reinstall commands no longer work.

    I did install PowerShell 6.0, which gives me another way to run commands, but the results are no better than using the DISM commands.  The pkgmgr commands do run without error, but they do not resolve it.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-04-16T19:26:18+00:00

    I do like a challenge, but so far I have not found any way to fix this issue with .NET. The commands meant to restore it do not work.

    I even did a Windows Reset, but the results were no better than your in-place upgrade. .NET still looks the same, with several items misplaced in the list of available Windows Features. Even MMC cannot load the Event viewer now.

    This was all on a Hyper-V VM, so I can restore that easily, but I will try to send in a Feedback Hub Capture of the issues before I am done with it.

    That leaves a clean install as the only way forward that I can suggest. My system is setup with all data on separate disks, so a clean install for me has very minimal impact.  I totally remove all partitions from my NVMe SSD during a clean install.  I do not have many Apps, so it does not take long to be back to normal, and usually with several things improved, after a clean install.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-04-16T23:25:21+00:00

    I even did a Windows Reset, but the results were no better than your in-place upgrade. .NET still looks the same, with several items misplaced in the list of available Windows Features. Even MMC cannot load the Event viewer now.

    That leaves a clean install as the only way forward that I can suggest.

    It's certainly looking that way, Don. I'm now seeing more & more reports of this issue in the Feedback Hub too. No response from MS on any of the feedback though.

    Wonder if this will end up making it through to the 1903 release & they'll end up with yet another major issue for a small percentage of users (which still adds up to a large number of people) that was reported as a serious bug in the feedback hub but never actioned?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-04-19T04:12:04+00:00

    Same exact problem, same exact build and update .. although I went in and turned a few features back on in components, not I cant access all of my control panel...

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-04-19T05:06:57+00:00

    I found this documented on the Visual Studio .NET Developer Community Forums since January, 2019 and it is the most upvoted Problem there.

    https://developercommunity.visualstudio.com/content/problem/421852/windows-10-64-bit-1809-net-framework-4-and-472-can.html

    Please Upvote this there also. There is a utility, Collect.exe, that can gather all of the relevant log files to attach to your Comment in this Forum.

    http://aka.ms/vscollect

    Use the Comment reply type there, not the Solution reply.

    Was this answer helpful?

    0 comments