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-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
  2. 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
  3. Anonymous
    2019-06-14T15:57:22+00:00

    There is a Command that you can try, using an Administrator Command prompt:

    DISM /Online /Enable-Feature /All /NoRestart /FeatureName:Microsoft-Windows-NetFx3-OC-Package /FeatureName:Microsoft-Windows-NetFx4-US-OC-Package /FeatureName:Microsoft-Windows-Client-EmbeddedExp-Package /FeatureName:Microsoft-Windows-NetFx3-WCF-OC-Package /FeatureName:Microsoft-Windows-NetFx4-WCF-US-OC-Package

    Copy the above command (all one line). You should be able to just right-click in the Command Prompt window to paste it in there.  You should then restart and run optionalfeatures.exe check to see if anything has changed.

    Otherwise, installing the latest Insider Fast Ring build should fix .NET.  If you have no desire to be running pre-release Windows 10 until sometime in the Spring of 2020, you could then try rolling back to the current public build, but I don't know if .NET will remain fixed or not.  Or you can just stay with Insider build 18912, if it seems stable enough, until then, by putting your PC in the Insider Release Preview Ring.

    You can download build 18912 from this web page:

    https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso

    Mount the ISO file in Windows, which will create a new drive letter and run setup.exe to upgrade.  If you are not in the Insider program, you will need to join to download the ISO.

    Was this answer helpful?

    2 people found 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