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-18T20:37:10+00:00

    I tried something different this time when trying to repair .NET and it appears to have worked.  I will try this again on another device to confirm.

    I disabled .NET on build 18362.175 by uninstalling all of the default enabled .NET Features, using a DISM command (including the /Remove option).

    I used DISM to attempt to add NetFx3 as a Windows Capability. This restores .NET to the list of Capabilities, but not to the list shown in optionalfeatures.exe.  This is the same as it behaved in the past also.

    I then uninstalled the May 14, 2019—KB4495620 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 1903. After downloading it from Windows Update Catalog, I reinstalled the .NET KB4495620, as Windows Update did not appear to immediately find it.

    Then I ran the long DISM command to enable all of the disabled .NET features that was mentioned in an earlier reply:

    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

    After that, .NET was again looking normal in optionalfeatures.exe and the various features showed as Enabled in the command:

    DISM /Online /Get-Features /Format:Table

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-06-18T17:43:41+00:00

    @Amy1CW

    KB4495666 has been superseded by the CU currently available on the Public Build (KB4503293) which brings it to 18362.175, as in your image.  This issue is not only caused by that old Insider KB.  I don't know what situation triggers this .NET issue after some Cumulative Updates, nor which Cumulative Updates will trigger it.

    Perhaps it is no longer an issue, assuming people upgrade directly from 18362.30 to whatever the current CU is, but it still seems to be happening to a few users.

    Also, the problem can still be replicated merely by disabling some .NET features, even on the public build 18362.175.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-06-18T17:41:30+00:00

    Just wanted to straighten that out as there seemed some confusion on that point.

    I'm not confused but someone else is, so why are you replying to me?

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. 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