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-09T23:00:41+00:00

    I ended up in this trap after April 13, 2019. Not sure what the update was that triggered. I was about to give up and then decided to jump back on the fast ring. After that updated to the latest, my .NET frameworks are back on the "Turn Windows Features on" list. I reckon some of you folks might be able to jump back in the fast update and the get off after everything is working by opting to leave on the next stable retail.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-05-01T22:50:27+00:00

    My method is very extreme and would not happen under normal circumstances.

    Wouldn't be too sure about that Don. There is something happening during some upgrades & updates that is managing to remove all of the .NET features in some (probably rare) circumstances. This has been happening since at least 1803 & there is yet to be any acknowledgement from Microsoft.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-05-01T22:32:09+00:00

    After trying harder, by removing every enabled Feature with PowerShell (including the -Remove option) I was indeed still able to replicate this issue, even on 18362.86.

    My method is very extreme and would not happen under normal circumstances.  However, I do not think that a user should be able to change the list of Optional Windows Features (and end up removing standard items like NetFx3 which cannot be reinstalled).

    I am going to try it again, but without the -Remove option, as this at least is closer to what the optionalfeatures.exe normally does, when you simply uncheck an item in that list.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-05-01T20:01:17+00:00

    Also, note that you can upgrade directly from 18362.30 to 18362.86 via Windows Update.  You should not see, nor require, the superseded KB4495666.

    Most users, specially Fast ring Insiders didn't have that choice. :)

    Good news about .Net, kudos!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-05-01T17:59:05+00:00

    I will see if I can replicate this fail on 18362.86.

    Thanks but I didn't mean it was broken for .Net, I wouldn't know as I don't have any problems with it.

    I was just trying to say that KB4495666 was a flawed CU

    Was this answer helpful?

    0 comments