Can't enable .NET Environment in Windows 10 1903

I decided to do a fresh install on a formatted sdd. Winver 1903. So far no issues. But it looks like some CU still wreck the OptionalFeatures, so probably some guys in the know need to have a relook at this. Thanks for the effort. 

Wouter

Sorry for the outdated information. That worked at that time because the KB listed was the most recent .NET Cumulative Update.

I have not reproduced and tested this issue for a long time.

I can do a test, to see if I can reproduce the failed OptionalFeatures state again, to see if it is still resovable in any way.

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

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.

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. ;)