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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-03-19T21:48:29+00:00

    I actually did spend a lot of time yesterday testing. I installed version 1909 and was able to use my usual method to create the .NET fail. However, I could not fix it in any way that I tried. I even tried some methods that I had found online that involved replacing .MUM files in the C:\Windows\servicing\packages folder with files from the original ISO and then doing an in-place repair install (re-running setup.exe from install media for the same version that you have installed). But even a Windows Reset does not fix things. It has to be a clean-install, as what is needed for .NET to work after a Windows Reset simply isn't in the image anymore.

    I have seen some explanations of why removing various packages makes them almost impossible to install. The mystery then is how in some cases .NET gets restored. An actual Windows OS build upgrade seems to work for anyone who needs to preserve their existing installed software, so upgrading to Insider Slow Ring build 19041.xxx should work.

    I was able to use the following commands to remove or to install NetFx3. Removing the Capability made it impossible to install the latest .NET CU, but enabling the NetFx3~~~~ Capability enables the .NET CU to install.

    DISM /Online /Remove-Capability /CapabilityName:NetFx3~~~~

    DISM /Online /Add-Capability /CapabilityName: NetFx3~~~~

    Here is the latest .NET CU:

    http://catalog.update.microsoft.com/v7/site/Search.aspx?q=4537572

    KB 4537572 Details:

    https://support.microsoft.com/en-us/help/4537572

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-03-19T22:04:43+00:00

    For installing the latest CU try this:

    Install this SSU: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4541338

    Then install the CU: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4551762

    As for upgrading to Version 1909, have you tried via the ISO? Just download the ISO file, mount it in Windows and run setup.exe to change from version 1903 to 1909. Because this is a cosmetic change to the Windows version number, it is not a full OS upgrade, but it does enable some things. This will also auto-install the latest Cumulative Update.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-03-19T23:11:54+00:00

    Unfortunately, I completed a fresh install of windows with a 1909 install package. No more .NET errors! I figured a full wipe wouldn't be that painful given I've been running on 1903 for less than a year ... along with apps randomly not installing.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-03-21T04:39:43+00:00

    I can confirm that an upgrade to a higher Windows build or version does fix .NET. I could not find any other way to repair it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-04-02T23:57:42+00:00

    This solved this problem for me on Windows 10 home on 4/2/20 after deleting the

    part of the command "/FeatureName:Microsoft-Windows-Client-EmbeddedExp-Package".  The system suggested that I use the "get-features" option.  I couldn't figure out how to use it without reading the help, so I just removed it and that worked.  Thank you for posting.

    Was this answer helpful?

    0 comments