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-10-18T17:39:28+00:00

    Sorry for the outdated information. That worked at that time because the KB listed was the most recent .NET Cumulative Update.

    I have not reproduced and tested this issue for a long time.

    I can do a test, to see if I can reproduce the failed OptionalFeatures state again, to see if it is still resovable in any way.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-10-18T20:55:57+00:00

    I decided to do a fresh install on a formatted sdd. Winver 1903. So far no issues. But it looks like some CU still wreck the OptionalFeatures, so probably some guys in the know need to have a relook at this. Thanks for the effort. 

    Wouter

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-10-18T22:23:30+00:00

    I did run a test and was able to replicate the strange listing in the OptionalFeatures menu, showing all .NET disabled.  I could not find a way to uninstall the latest .NET Cumulative Update - KB4522738. However, I still ran the Add-Capability command to reinstall NetFx3~~~~ and the long command to try to add back everything else.

    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

    The second command worked, except for /FeatureName:Microsoft-Windows-Client-EmbeddedExp-Package. But it fixed the OptionalFeatures.exe menu and i was then able to add back anything missing normally, using that OptionalFeatures menu.

    Because I have never seen this happen on a device, unless I force it, I don't know if what I did replicates your situation, but as far as I can test, it seems still repairable by using the above DISM commands.

    Meanwhile, I am glad to hear that you have it fixed for now and hope there may be enough info here to help others, if they want to try the repair, rather than a reinstall.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-11-08T17:28:22+00:00

    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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-12-09T06:40:09+00:00

    I found that it's still an issue on build 18363.476 (screenshots are in Chinese, but they are similar).

    I tried all the methods in this post and somewhere else, in Chinese and English communities, all those command lines, but none of them seem to work.

    Finally I read about that update to the latest Insider Preview may solve the problem, so I just joined the Insider Preview and update to 19037.1, and solve the problem.

    Since this is my personal PC, and there's nothing important in it, I can accept to use the Insider Preview version.

    I'd like to say thanks to Don, thank you very much!

    Was this answer helpful?

    0 comments