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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-05-10T11:24:36+00:00

    Yeah, my feature list was the same as many of those pictures in this thread. No .NET Frameworks. Error 50 when I tried to use the console fixes etc. I'm now back, but living with the fast ring. I can probably downgrade to the slow at some point and then opt out for the next stable retail. Never done it before so I don't know how that goes.

    Brandon

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-05-09T23:37:29+00:00

    So you had this same symptom with the unusual list in optionalfeatures.exe and it fixed itself after some Insider update?

    Some with these symptoms are repairable, but many seem to have no fix.

    The Fast Ring builds are currently on the 20H1 build cycle, so anyone selecting that route will have to live with Fast Ring Insider bugs and those risks until March - May, 2020.

    There seems to be no action on the .NET Developer forums on this.  Perhaps they are only focused on .NET 5 or .NET Core now.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-05-09T23:00:41+00:00

    I ended up in this trap after April 13, 2019. Not sure what the update was that triggered. I was about to give up and then decided to jump back on the fast ring. After that updated to the latest, my .NET frameworks are back on the "Turn Windows Features on" list. I reckon some of you folks might be able to jump back in the fast update and the get off after everything is working by opting to leave on the next stable retail.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-05-09T05:59:17+00:00

    Okay, I never go this far, maybe let's try remove '/All' command and do it again? Seems no '/All', no parent features needed.

    Like this:

    Dism /online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx3-OC-Package

    Dism /online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx4-US-OC-Package

    Dism /online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx3-WCF-OC-Package

    Dism /online /Enable-Feature /FeatureName:Microsoft-Windows-NetFx4-WCF-US-OC-Package

    You're my hero. Thank you for this. It fixed all my issues and I was worried hardcore about my system. 

    Much love. Thank you so much! <3

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2019-05-02T04:44:58+00:00

    Unfortunately, this only worked on build 18362.86 (after the problem was first replicated on that same build, by using PowerShell to disable & remove all Optional Features).

    I tried, on the same device, reverting to 18362.30 and doing this removal and repair again, but it did not work.  Also, I then upgraded (with .NET already gone) to 18362.86 and I cannot Enable .NET.

    From what I have read, .NET issues have sometimes only been repairable if any subsequent KB update is first uninstalled. So once .NET has failed, or has been removed, and a new KB has been installed, you can't fix it.

    The CBS and DISM logs indicate missing Parent Features, which prevent the remaining, listed .NET Features from being Enabled.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments