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-04-10T21:23:20+00:00

    On my laptop now, there's only a single ".NET Environment" entry. I can neither install nor remove any .NET components. Running the Standalone .NET installers says that .NET is already installed. None of the standard reinstall or repair .NET stuff works. The update has managed to completely remove & not replace .NET!

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  2. Anonymous
    2019-04-11T03:02:30+00:00
    1. creat .bak file, the content is:

    start /w pkgmgr /iu:Microsoft-Windows-NetFx3-OC-Package

    start /w pkgmgr /iu:Microsoft-Windows-NetFx4-US-OC-Package

    start /w pkgmgr /iu:Microsoft-Windows-NetFx3-WCF-OC-Package

    start /w pkgmgr /iu:Microsoft-Windows-NetFx4-WCF-US-OC-Package

    1. run as admin
    2. solve the problem

    https://answers.microsoft.com/zh-hans/insider/forum/insider\_wintp-insider\_update-insiderplat\_pc/%e5%85%b3%e4%ba%8e-windows/2517e4ed-3c37-42c1-a1a4-b5a806a912ac?tm=1554947302513

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  3. CrazyKats 19,330 Reputation points Volunteer Moderator
    2019-04-10T13:14:13+00:00

    Please make sure to file this in the Feedback Hub.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  4. Anonymous
    2019-04-11T00:35:43+00:00

    Yep. The CU has totally wrecked .NET to the point where it can't currently be reinstalled.  The entire "C:\Windows\Microsoft.NET" folder size is 43MB where the same folder under the Windows.old folder is jus over 700 MB!

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  5. Anonymous
    2019-04-11T07:41:50+00:00

    I just check how DISM use, figure that I was wrong about using DISM command.

    https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh824822(v%3dwin.10)#to-enable-windows-features

    It says:

    Enable a specific feature in the image. You can use the /All argument to enable all of the parent features in the same command. For example, type:

    Dism /online /Enable-Feature /FeatureName:TFTP /All

    So would you mind trying to creat the bak file again, with these contents below:

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

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

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

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

    And run as admin.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments