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
    2020-07-29T18:10:27+00:00

    i have the same problem

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-05-08T19:21:51+00:00

    I just want to chime in and say this was a life saver.

    Original problem:

    I tried to launch Powershell and got the following error message: 

    I came to this thread obviously and this is what I did to fix that error. 

    I followed Don Cuthbert's directions and pasted the following in the command prompt:

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

    Once that was done and successful, I restarted my laptop. Then pasted the following in the command prompt:

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

    After that (and successful), I pasted the following in the command prompt  

    DISM /Online /Enable-Feature /All /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

    REMOVING THIS

    "****/FeatureName:Microsoft-Windows-Client-EmbeddedExp-Package"

    as did aenewman. I restarted my laptop and Powershell launched successfully!!!  

    Thank you both for your help, especially Don!!! 

    ****************************************

    I wanted to add one more thing. The above directions also fixed an issue I had where the .NET Framework checkboxes were not checked (after many attempts to enable them), in Windows Features. After I performed the above, I checked Windows Features and the checkboxes were checked!!! YAY! 

    ****************************************

    I have to add one more thing (I'm very happy apparently). Those steps also fixed the "0x800713ec - Asia" error that I've had for months!!

    I kept getting that error anytime I tried to update my VPN (which prompted me to setup the .NET Framework). 

    Side Note: Before I performed the instructions Don suggested, I disabled my antivirus and Windows Defender. I dont know if that helped but either way I'm ecstatic.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. 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
  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-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