Can't enable .NET Environment in Windows 10 1903

I will re-quote my previous directions, from an earlier reply above, which worked for me, except below I have replaced KB4495620 with KB4506991, which is a newer .NET update.  Please give the below steps a try (after where it says "To resolve the issue"). Hopefully it will work.

________________________________________________________________________________________

https://developercommunity.visualstudio.com/comments/617759/view.html

I can still replicate this issue on Windows 10 Version 1903, build 18362.175. The fix is not as straightforward as installing the latest Windows Updates.

However, this can be fixed with some extra steps and still keep the device on Version 1903.

To replicate the issue:

DISM /Online /Disable-Feature /FeatureName:NetFx4-AdvSrvs /FeatureName:WCF-Services45 /FeatureName:WCF-TCP-PortSharing45 /FeatureName:NetFx3 /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

Run Optionalfeatures.exe to see the problem list of Optional Features.

To resolve the issue:

Uninstall KB4506991

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

Install KB4506991 --- This cannot be reinstalled without first adding back the NetFx3~~~~ Capability, as it will indicate that the KB is not applicable.

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




DISM /Online /Enable-Feature /FeatureName:WCF-TCP-PortSharing45

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.

You could've saved yourself the time and effort as that was suggested within the first 5 pages, when it was evident that the proposed fixes didn't work for all. ;)

What worked for me if anyone wants to try out.

I opted in windows insider and chose the "skip ahead" build (I have the 18985 build).

I restarted and manually verified for updates in order to install the build.

It took some time to finish (around 3-4 hours), but it kept my files and programs and net framework was installed again (3.5 and 4.8).

Right now since most things look stable I opted out (I chose the "Stop getting preview builds setting").

I don't know if any of these things influenced the outcome but before opting in windows insider I tried most of the solutions involving "Dism" and "pkmngr" commands.

I also manually extracted all the missing "mum" and "cat" files related to net framework (netfx) into the packages folder and tried to to run the commands from there.

I also had net framework 4.8 sdk installed.

Right now I'm just happy I can install the programs that I need.

HenryYHO's workaround did not work al all...

We just had a machine in that was not in any kind of Insider loop. Exactly the issue as described in the thread: Feature list unrecognizable, bunch of software stopped working because of missing .net. Including Powershell that has gone down the drain. 

Got interested in trying out Don Cuthbert's solution. Only, none of the KB's he mentions (KB4506991 or KB4495620) are present. So his solution never works. 

This machine is Windows 10 Pro (in Dutch), 1903, build 18362.418 with following updates present (and uninstallable if needed)

KB4517389

KB4521863

KB4520390

KB4515871

KB4515383

KB4508433

KB4509096

KB4498523

User describes the problem having started after an update. 

Is any of these KB's relevant to Don Cuthbert's solution, i.e. that you can uninstall it, run the first command in Don's solution, install it, and then run the second command from Don (the long one)? I am going to give it a shot myself, and see what happens. 

Wouter Pinkhof 

OK, follow up on this: when trying to uninstall KB4517389, I get an error after a while. No details given. Downloading and running the standalone says the update is already installed...