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.
I just completed an upgrade so I had a way to test the command. I copied and pasted from my reply above, to be sure that I had no typo here in the Forum post. Below you can see that it worked, pointing to the Windows.old folder as /Source, although this PC does not have any .NET issue to begin with.
The CBS.log shows all the details of how it ran. Your CBS.log should also indicate what happens when you try.
It could be. I was expecting your list to be missing some items. The unusual items that you do show in your Features are sub-components of some of the parent items.
Are you certain that you typed the DISM command with /Source correctly? Below is the DISM help screen describing it. You can copy the command from the above Forum post and paste it into your Administrator Command Prompt by right-clicking the Command Prompt screen. I am wondering if you missed the "/"?
C:\Windows\system32>DISM /Online /Enable-Feature /?
Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Image Version: 10.0.18362.53
/Enable-Feature /FeatureName:<name_in_image> [/PackageName:<name_in_image>]
[/Source:<source>] [/LimitAccess] [/All]
Enables the feature specified by the FeatureName command argument.
You do not have to specify the /PackageName if it is the Windows Foundation Package.
Otherwise, use /PackageName to specify the parent package of the feature.
Multiple /FeatureName arguments can be used if the features are components in
the same parent package.
You can restore and enable a feature that has previously been removed from the
image. Use the /Source argument to specify the location of the files needed to
restore the feature. Multiple /Source arguments can be used.
Use /LimitAccess to prevent DISM from contacting WU/WSUS.
Use /All to enable all parent features of the specified feature.
Example:
DISM.exe /Online /Enable-Feature /FeatureName:Hearts /All
DISM.exe /Image:c:\offline /Enable-Feature /FeatureName:Calc
/PackageName:Microsoft.Windows.Calc.Demo~6595b6144ccf1df~x86~en~1.0.0.0
DISM.exe /Image:c:\offline /Enable-Feature /FeatureName:Feature
/Source:c:\test\mount
The command "DISM /Online /Cleanup-Image /RestoreHealth" took a while to run but ultimately made no difference.
The installed features includes these .NET features that we're trying to enable & they're the same as your PowerShell listing. There is no mention of feature "NetFx4-AdvSrvs" from your powershell listing. I wonder if this is the missing "parent feature"?
Feature Name : Microsoft-Windows-NetFx3-OC-Package
State : Disabled
Feature Name : Microsoft-Windows-NetFx4-US-OC-Package
State : Disabled
Feature Name : Microsoft-Windows-NetFx3-WCF-OC-Package
State : Disabled
Feature Name : Microsoft-Windows-NetFx4-WCF-US-OC-Package
State : Disabled
Same result as with the /All option. DISM.log says
"Parent features must be enabled before this feature can be enabled"
"/Source" doesn't seem to be a valid option for DISM. From DISM.log
"Encountered an unknown option "source" with value "C:\Windows.old\Windows" "
