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.
Hi, have same problem. build: 18362.449
tried evenything. Not able to deinstall KB522355..
Optionalfeatures does not work, DISM enable-features gives error 50 (on all .net fetaures). See below.
Did you ever find a solution to this? I'm having the same issue.
Have you tried these two Administrator Command Prompt Commands from my post on the previous page of this thread? Note that the second command is all one line. You should be able to copy them from here and just right-click in your Command Prompt window to paste them there.
DISM /Online /Add-Capability /CapabilityName:NetFx3~~~~
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
What version of Windows 10 are you running? Run ver at a Command Prompt to get your Windows build number.
I have not tried those but i will in the morning. Im running 1903 but i upgraded to 1909 in hopes of it restoring the functionality but it did not.
So the first command worked:
DISM /Online /Add-Capability /CapabilityName:NetFx3~~~~
The longer dism command you posted did not work.
When I do: DISM /Online /Get-Capabilities /Format:Table | Sort
I show NetFx3~~~~ as installed. I then tried the DISM commands and I still get Error 50.
What I notice when I do a:
DISM /Online /Get-Features /Format:Table | Sort
There is no NetFx3 or NetFx4-AdvSrvs even listed in the table. These are just completely gone. I have a feeling this is what's preventing the dism commands working as the log file for dism states:
DISM Package Manager: PID=9468 TID=12804 Parent features must be enabled before this feature can be enabled. "Microsoft-Windows-NetFx4-WCF-US-OC-Package" - CPackageManagerCLIHandler::Private_ProcessFeatureChange
I spent a lot of time working through this with earlier builds, which is documented throughout this long thread, along with some approaches that worked for others in some cases. I have never seen the error happen on its own myself, but I was able to replicate the symptoms by completely uninstalling all of these using PowerShell. The end result is the same abnormal list in the OptionalFeatures.exe list.
What you are seeing with missing .NET packages is common when this state is encountered. The problem appears to be that there are parent features to these .NET packages, which are not auto-installed by the DISM commands. I was at one point thinking that uninstalling the latest .NET Cumulative Update prior to doing the commands to install NetFx3 and the others would help, but when I last tested this, I was not able to do that. The fix -- installing NetFx3~~~~ Capability and then the others, still seemed to work. I did see some errors, but enough of the long command worked that it enabled the rest to be installed using the normal Control Panel Inerface (OptionalFeatures.exe).
You could try uninstalling the NetFx3~~~~ Capability and then reinstalling again. See if you can then install the latest .NET CU. Documentation that I read indicated that installing as a Capability, rather than using the /Add-Package DISM commands was the best way to do this. To uninstall NetFx3~~~~ try:
DISM /Online /Remove-Capability /CapabilityName:NetFx3~~~~
For some, what worked was to upgrade to a recent Windows Insider build of Windows 10. To try that, you could join a device to the Windows Insider Program and join the Slow Ring to get build 19041. If you are not on Insider builds already, you will be running pre-release builds for Windows 10 Version 2004, due this Spring, so that has some associated risks.
