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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-05-19T17:59:46+00:00

    Don thank you so much for your in investigation into this.

    I've followed all of the steps in this thread, plus many others, and have had no luck getting .net re-installed.  All DISM commands end in error 50 and any .net repair tools or installers fail.

    The .net framework installer always fails with:

    I wonder where it is pulling this information from?  I'm tempted to go start deleting any .net related registry keys and C:/Windows/ .net references.....If I have to re-image my OS it wouldn't matter would it?

    Before just madly deleting things maybe I'll switch to the fast ring and see if upgrading to 18895 fixes this, I'm still on 18362....  I'll respond back with any progress, seems like lots of people are having this issue.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-05-10T19:52:21+00:00

    Yeah, my feature list was the same as many of those pictures in this thread. No .NET Frameworks. Error 50 when I tried to use the console fixes etc. I'm now back, but living with the fast ring. I can probably downgrade to the slow at some point and then opt out for the next stable retail. Never done it before so I don't know how that goes.

    Brandon

    Thank you!

    I can confirm that upgrading today from build 18362.86 to 18895.1000 has repaired .NET on a VM on which none of the other solutions has worked.

    I captured the upgrade to Feedback Hub and submitted it.  https://aka.ms/AA52im7

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-05-10T17:37:45+00:00

    Thanks.

    I have a VM in the failed state, with no way to fix, so I am upgrading it to today's Fast Ring Build 18895 to see what happens.

    Apparently, these 20H1 builds do not expire until July, 2020, so one approach might be that if you find a build that seems stable for your needs, you can just Pause builds until next Spring (when 20H1 will become the public build) or pause until a more stable Slow Ring build is released.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-05-10T11:24:36+00:00

    Yeah, my feature list was the same as many of those pictures in this thread. No .NET Frameworks. Error 50 when I tried to use the console fixes etc. I'm now back, but living with the fast ring. I can probably downgrade to the slow at some point and then opt out for the next stable retail. Never done it before so I don't know how that goes.

    Brandon

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-05-09T23:37:29+00:00

    So you had this same symptom with the unusual list in optionalfeatures.exe and it fixed itself after some Insider update?

    Some with these symptoms are repairable, but many seem to have no fix.

    The Fast Ring builds are currently on the 20H1 build cycle, so anyone selecting that route will have to live with Fast Ring Insider bugs and those risks until March - May, 2020.

    There seems to be no action on the .NET Developer forums on this.  Perhaps they are only focused on .NET 5 or .NET Core now.

    Was this answer helpful?

    0 comments