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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-05-01T13:40:03+00:00

    If you did a complete reinstall of the last

    Public Release build you would not have

    gotten KB4495666.

    What did you reinstall?

    The moment he switched to the Slow Ring he got the CU

    UPDATE 4/9: We have released Build 18362.53 (KB4495666) for Windows Insiders who are currently on Build 18362.30 of the Windows 10 May 2019 Update. This update also includes security updates that come as part of the normal monthly Patch Tuesday release cycle.

    The question should be: why did he switch if he didn't wanna be on the WIP anymore?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-05-01T13:34:59+00:00

    If you did a complete reinstall of the last

    Public Release build you would not have

    gotten KB4495666.

    What did you reinstall?

    I reinstalled to 1803, and then opted into the slow lane for Windows Insider, which got me to 18362.30. Then I got KB4495666 just today.

    With 18362.30, everything worked just fine. KB4495666 seems to be what screwed things up again.

    Was this answer helpful?

    0 comments
  3. CrazyKats 19,415 Reputation points Volunteer Moderator
    2019-05-01T13:15:32+00:00

    If you did a complete reinstall of the last

    Public Release build you would not have

    gotten KB4495666.

    What did you reinstall?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-05-01T12:47:27+00:00

    I reinstalled and got out of the inside program. For now everything is working fine.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-05-01T12:39:47+00:00

    Oh my god. I just did a complete reinstall, and opted into the Slow path for Windows Insider Previews, thinking I would be safe. Guess what just happened. There was a cumulative update today, ending with a 66 and I'm AGAIN STUCK in the same situation.

    I'll have to do ANOTHER clean install. This is BEYOND unacceptable. I'm never touching Windows Insider again.

    Was this answer helpful?

    0 comments