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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-05-27T21:53:07+00:00

    Thanks Don 

    I have been look for solution for net framework and DISM command have fixed my problem Thanks so much!!!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-06-05T15:56:40+00:00

    Has anyone tried the following?

    Extract the contents of the Windows 10 1903 iso  (7-zip will do this for you)

    The run the following command from Powershell

    DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"<LOCATION OF THE EXTRACTED FILES"

    I know the 'enable features' aspect is broken but I've installed 3.5 using this method.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-06-05T17:31:12+00:00

    There was a .NET bug with early "dot" builds of 18362.  I don't recall the exact "dot" revision it was fixed in (18362.86?), but it's not an issue any longer.  If you're installing earlier versions of 18362, save yourself the trouble and skip to a later revision.  :)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-06-10T06:31:49+00:00

    Still have the problem at 18362.145...

    It happend after the latest cu update

    "Solved" upgrading to windows insider 18912.1001

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-06-11T15:08:48+00:00

    Phew!, I am so glad i found this thread. I only built this new PC over the weekend on 1903 (18362.30) and after a couple of auto updates lost .Net in EXACTLY the same way

    I was almost on the verge of a rebuild again, despite spending 2 days transferring settings/data etc from old PC.

    One suggestion was to try installing kb4498523 to take it to a new 18362 build(can't remember exact build), but Win Update was also dead in the water & giving me a 0x80073701 error. Even the update troubleshooter failed with 0x8007007E

    I saw the last few comments mentioning trying the Windows insider Preview 18912.1001 so I hopped on board the Preview Train & it installed OK. Now i have .Net back & all my dead apps are running again :)

    My final question is now that I am in the program, is there a safe way to return back to a released (Non-preview) build, without losing this fix? Or am i now stuck in 'unknown territory'

    Thanks

    Was this answer helpful?

    0 comments