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-08-27T01:11:50+00:00

    You could've saved yourself the time and effort as that was suggested within the first 5 pages, when it was evident that the proposed fixes didn't work for all. ;)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-07-28T01:23:30+00:00

    I will re-quote my previous directions, from an earlier reply above, which worked for me, except below I have replaced KB4495620 with KB4506991, which is a newer .NET update.  Please give the below steps a try (after where it says "To resolve the issue"). Hopefully it will work.

    ________________________________________________________________________________________

    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 KB4506991

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

    Install KB4506991 --- 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
  3. Anonymous
    2019-07-28T01:00:22+00:00

    Don,

    Thanks for all of your help on this thread. I followed your suggestion in the previous post, and it's still not working for me.

    I have Windows 10 Pro, 1903, Build 18362.267.

    • Uninstalled KB4495620 successfully
    • Ran the DISM command with Windows ISO in a flash drive successfully
    • Installed KB4502584 successfully

    Tried running the DISM command and received an error 50 saying that Microsoft-Windows-FetFx3-OC-Package could not be enabled. Once I checked optionalfeatures.exe, I saw that the "abnormal" list was not fixed.

    I have the following updates on my PC:

    • KB4497932
    • KB4509096
    • KB4500109
    • KB4498523
    • KB4497727
    • KB4502584
    • KB4505903
    • KB4508433

    Also, I had reset my Windows 10 and updated Windows as soon as I installed it. I had the problem before and after, so no news here.

    Please let me know if you see anything different than your instruction here.

    Thank you.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-07-02T15:53:51+00:00

    Yes, I tried the command with the /Source parameter while the usb drive created by media creation tool is inserted.

    And yes, the drive has the letter E: :)

    The error message for the command "DISM /Online /Add-Capability /CapabilityName:NetFx3~~~~ /Source:E:\Sources\sxs" was something like "Could not find correct assembly" I think :/

    I am sure that this usb drive is the same I used a month ago. Should I create a new installation usb drive?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-07-01T22:13:55+00:00

    In the second DISM command, the one with /Source, you need to have the ISO mounted to some drive letter.  If you connect your USB drive containing the Version 1903 upgrade, you need to refer to whatever drive letter it has, not to "E:" (unless it happens to be in drive E:).

    That should enable you to install the latest .NET Cumulative Update.  However, there is now a new version, KB4502584, which you can download from the link below.  Be sure to get the right one to match your system.

    https://www.catalog.update.microsoft.com/Search.aspx?q=4502584

    I have tried many things to fix the error.  If your system is in the same error state, it will show an unusual mix of Optional Features (as in your screenshot) when you run optionalfeatures.exe.  The method that I described above is the only way that I have found to repair it without upgrading to a "20H1" Insider build, which will not evolve to become a public version until around April - May of 2020.

    I have not seen the issue either, unless I force it to happen, but I know that for some it apparently happens just by allowing some Cumulative Update to install.  The fact that PowerShell does not work is an indication that you have the same problem as is so difficult to resolve.

    Was this answer helpful?

    0 comments