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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-06-21T22:34:52+00:00

    https://developercommunity.visualstudio.com/comments/617759/view.html

    I can still replicate this issue on Windows 10 Version 1903, build 18362.175. The fix is not as straightforward as installing the latest Windows Updates.

    However, this can be fixed with some extra steps and still keep the device on Version 1903.

    To replicate the issue:

    DISM /Online /Disable-Feature /FeatureName:NetFx4-AdvSrvs /FeatureName:WCF-Services45 /FeatureName:WCF-TCP-PortSharing45 /FeatureName:NetFx3 /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

    Run Optionalfeatures.exe to see the problem list of Optional Features.

    To resolve the issue:

    Uninstall KB4495620

    DISM /Online /Add-Capability /CapabilityName:NetFx3~~~~

    Install KB4495620 --- This cannot be reinstalled without first adding back the NetFx3~~~~ Capability, as it will indicate that the KB is not applicable.

    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

DISM /Online /Enable-Feature /FeatureName:WCF-TCP-PortSharing45

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-06-18T22:35:57+00:00

    Sorry about that. 😁

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-06-18T17:43:41+00:00

    @Amy1CW

    KB4495666 has been superseded by the CU currently available on the Public Build (KB4503293) which brings it to 18362.175, as in your image.  This issue is not only caused by that old Insider KB.  I don't know what situation triggers this .NET issue after some Cumulative Updates, nor which Cumulative Updates will trigger it.

    Perhaps it is no longer an issue, assuming people upgrade directly from 18362.30 to whatever the current CU is, but it still seems to be happening to a few users.

    Also, the problem can still be replicated merely by disabling some .NET features, even on the public build 18362.175.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-06-18T17:41:30+00:00

    Just wanted to straighten that out as there seemed some confusion on that point.

    I'm not confused but someone else is, so why are you replying to me?

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more