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-08-27T00:41:27+00:00

    After reading every answer and fix, plus researching tech net as well. I finally got a solution that I should have done from the get go.  I did a full reformat and install with version 1809. I was able to then add the .NET framework 2.0 and 3.5 from control panel with no issue. 

    I spent many hours trying to fix it with all the cmd line prompts  the .NET fix tool and nothing worked. even did the powershell thing.

    I install windows with no internet connection and after it did a fresh install of 1809. I installed the .net frame work add in,  then I got brave and tried the 1903 update which did work as well . Seems you need to install the .NET frame work 2.0 feature prior too 1903 update .  This seemed to work I had 5 new machines with 1903 that would not let me install 2.0 or 3.5 framework 

    Do yourself a favor do a reformat and install a fresh windows 10 it works best.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. 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
  3. Anonymous
    2019-05-09T05:59:17+00:00

    Okay, I never go this far, maybe let's try remove '/All' command and do it again? Seems no '/All', no parent features needed.

    Like this:

    Dism /online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx3-OC-Package

    Dism /online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx4-US-OC-Package

    Dism /online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx3-WCF-OC-Package

    Dism /online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx4-WCF-US-OC-Package

    You're my hero. Thank you for this. It fixed all my issues and I was worried hardcore about my system. 

    Much love. Thank you so much! <3

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2019-04-11T00:53:59+00:00

    No clue how or why that extra stuff is there. That all happened when I applied the CU & rebooted.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2019-04-11T00:18:40+00:00

    Actually, your entire group of .NET has different names than mine.

    I could be wrong but looks like he's using either Enterprise or Server

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments