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 No comments

177 answers

Sort by: Most helpful
  1. Anonymous
    2019-06-12T23:15:52+00:00

    18912 is an Insider build and has an expiry date. You had asked if you would be able to upgrade again to 18912 if .NET remains not working after rolling back to 18362. The ISO provides the best way to do that, if you need to.

    There is no point in using the ISO on the same build if it is already working well.

    If you can roll back to the 18362 public build and keep .NET working, that would probably be best. But I don't know if that will work.

    Rolling Back isn't a solution for everyone. The roll back did not work on 2 of the test computers we tried it on.

    I have a mix of enterprise and Pro Windows 10 builds and they all have this .net Problem. I can't go with insider down load solution as some of the computers are production machines. I can't afford to have untested updates in them.

    What is Microsoft doing to fix this issue it's not even on the https://docs.microsoft.com/en-us/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019 that supposed to have known issues.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-06-12T15:08:06+00:00

    18912 is an Insider build and has an expiry date. You had asked if you would be able to upgrade again to 18912 if .NET remains not working after rolling back to 18362. The ISO provides the best way to do that, if you need to.

    There is no point in using the ISO on the same build if it is already working well.

    If you can roll back to the 18362 public build and keep .NET working, that would probably be best. But I don't know if that will work.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-06-12T06:13:03+00:00

    Thanks Don,

    Can you clarify 'you can update again'?

    Do you mean I should roll back to 18362.30 before the 10 day limit & then use the iso to update to 18912 without insider preview?

    Or do you mean use the iso on the current 18912 to update to a non-preview build?

    Thanks

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-06-11T17:00:31+00:00

    You mentioned being in 'unknown territory', so I assumed you might not be comfortable running Insider builds as your daily OS. There is potential for OS bugs and loss of data, so it is not for everyone.  You could just keep updating, via the Slow or Fast Rings.  Slow Ring sees fewer, more stable builds, so would be safer and less time with OS updates.  Fast Ring is less stable and more often, sometimes weekly OS updates.

    Yes, you could keep updating. But if build 18912 seems stable and works well, you might want to just switch to Slow Ring, or pause Windows Updates to save on having to do anything other than use your PC as you normally would.

    You should also be able to update again to build 18912. There is an ISO expected for that, possibly today, which will make that option even easier to do.

    EDIT: ISO is out now:  https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-06-11T16:38:15+00:00

    Thanks for the info Don.

    So, if I rolled back & it did not work - could I then re-update back to the insider build?

    I assume I would then have to keep updating as each new preview came out - or would there be a way of doing an in-place upgrade to a later 'General Release' build once available?

    Sorry for the questions, I am usually fairly technical, but Windows insider is a new one to me

    Thanks

    Was this answer helpful?

    0 comments No comments