Can't enable .NET Environment in Windows 10 1903

Anonymous
2019-04-10T07:18:57+00:00

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?

Windows for home | Windows 10 | Performance and system failures

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.

0 comments

177 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-04-11T13:58:01+00:00

    Good work!  I began by looking at DISM and then switched to doing the same in PowerShell, not realizing that PowerShell was disabled.

    I wonder if installing PowerShell 6, which is a small download, would work? I was actually trying the commands in PowerShell 6.

    https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-core-on-windows?view=powershell-6

    The repair via upgrade that Roger suggested might be the simplest.

    I also wondered if a DISM repair would help.

    DISM /Online /Cleanup-Image /RestoreHealth

    You can also list the FeatureNames with DISM in order to get the syntax right, but I will need to look that up, or use DISM /Online /?.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-04-11T16:59:26+00:00

    You can also point to a Source folder to restore optional features, if the command that was already suggested does not work without a Source. You could probably just point to your Windows.old files as the Source:

    DISM /Online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx3-OC-Package /Source:C:\Windows.old\Windows

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-04-11T20:48:20+00:00

    "/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" "

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-04-11T20:50:39+00:00

    Same result as with the /All option. DISM.log says

    "Parent features must be enabled before this feature can be enabled"

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-04-11T21:03:18+00:00

    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

    Was this answer helpful?

    0 comments