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-04-14T23:37:18+00:00

    Thank you so much!!!!!!!!!!!!!!

    I just did as you said and solved the same problem successfully. For those who have the same problem please have a try of 陈俊晔 's method.

    Again thanks so much. :) 谢谢TAT

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-04-14T22:43:58+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

    @ 陈俊晔

    Even though pkgmgr is deprecated, it does not mean that it does not work.  The syntax that you used could be crucial, as the "start /w pkgmgr /iu:" portion of each command is significantly different than just running the commands without that syntax.

    I am able to run each command line without error, as long as I use that exact syntax.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2019-04-14T22:34:33+00:00

    It would be intriguing and challenging to figure out a .NET repair that works, but the clean install would likely be faster and simpler.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-04-14T22:14:17+00:00

    Thanks again Roger. That allowed the in-place upgrade to work normally, however the .NET issue remains exactly as it was before.

    You're welcome, sorry it didn't work. I guess it's time for that dreadful clean install you wanted to avoid.

    Don't forget to back up important files. Good luck!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-04-14T22:07:53+00:00

    The latest build has a bug (check this thread). If that's the one you downloaded or even if it's not, try cleaning C:\Windows\SoftwareDistribution\Download and disable Windows Search.

    Restart and try again, it should work.

    Thanks again Roger. That allowed the in-place upgrade to work normally, however the .NET issue remains exactly as it was before.

    Was this answer helpful?

    0 comments