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-06-17T23:15:06+00:00

    I tried installing build 18362.30 and recreated the .NET issue. I let it upgrade to the latest CU, but .NET remained broken.

    I then upgraded to 18912, using the ISO. That fixed .NET. Once I confirmed that .NET was there and I had PowerShell working, etc., I rolled back to 18362.175. However, .NET was again broken.

    So, if the only way to fix .NET is to upgrade to 18912, you may have to keep running that until Spring 2020.

    However, for most, a clean install of Windows 10 version 1903 will auto-update during install to build 18362.175 and .NET will work properly.  If a clean install is an option, I would try that instead of using the Insider builds.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-06-16T08:24:19+00:00

    I mean, they released an update that breaks the .NET infrastructue for ALL the Win10 users...

    Not what you want to hear but CU KB4495666 did not break it "for ALL the Win10 users"

    It didn't break mine and I don't know what it is, but there must be something else involved.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-06-16T08:10:15+00:00

    Thank you,

    The DISM command is uneffective, so the only solution is tu go to the insider thing.

    and will have to format/ reinstall Windows and all the stuff when the update will be published and available for the public.

    I'm completely stunt that Microsoft doesn't reac, I mean, they released an update that breaks the .NET infrastructue for ALL the Win10 users, and they want all the Win10 users to jump to Beta testers ?!?! that is such a non sense.

    When I've installed the Windows, it was working, it is due to an update, this should be fixable, right ?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-06-14T09:39:23+00:00

    Hello,

    I'm in a fresh install of Windows 10 Pro 1903,

    installation done through usb key generated by the Windows tool.

    I have to same .NET problems listed here, not possible to install, weird "extensivity" things, and my log viewer is not lauching, nor my powershell ( mscoree.dll ).

    so even a fresh install, with a brand new Hard Drive has the problem.

    anybody found anything ?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-06-12T23:25:41+00:00

    This time, .NET has been fixed by the 18912 upgrade. The question is whether rolling back to 18362 will break .NET again or not.

    Was this answer helpful?

    0 comments