This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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.
My method is very extreme and would not happen under normal circumstances.
Wouldn't be too sure about that Don. There is something happening during some upgrades & updates that is managing to remove all of the .NET features in some (probably rare) circumstances. This has been happening since at least 1803 & there is yet to be any acknowledgement from Microsoft.
Wow, I found a DISM command that appears to have fixed this. It worked on 18362.86 that was showing the same symptoms, with NetFx3 unknown, etc. and the strange list of Features in optionalfeatures.exe.
If anyone still has a system in this state you can try it. It involves using a single command to enable 5 of the still-listed NetFx Features at once. Below is all one line:
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
You can see the list of the 5 features at the top of the below screenshot, with the required command at the bottom.
Unfortunately, this only worked on build 18362.86 (after the problem was first replicated on that same build, by using PowerShell to disable & remove all Optional Features).
I tried, on the same device, reverting to 18362.30 and doing this removal and repair again, but it did not work. Also, I then upgraded (with .NET already gone) to 18362.86 and I cannot Enable .NET.
From what I have read, .NET issues have sometimes only been repairable if any subsequent KB update is first uninstalled. So once .NET has failed, or has been removed, and a new KB has been installed, you can't fix it.
The CBS and DISM logs indicate missing Parent Features, which prevent the remaining, listed .NET Features from being Enabled.
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
I ended up in this trap after April 13, 2019. Not sure what the update was that triggered. I was about to give up and then decided to jump back on the fast ring. After that updated to the latest, my .NET frameworks are back on the "Turn Windows Features on" list. I reckon some of you folks might be able to jump back in the fast update and the get off after everything is working by opting to leave on the next stable retail.
