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-12T00:02:57+00:00

    Wow! My features are pretty messed up then. I suspect a rebuild coming up in the very near future.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-04-11T23:39:27+00:00

    This shows where some of the unusual items in your Windows Features list actually belong. They are subcomponents of other items.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-04-11T23:22:31+00:00

    You're correct. The /Source switch is definitely a valid option. I copied & pasted the command from your post, so I'm pretty sure it's correct.

    This seems to be an occassional & ongoing issue various people have encountered over various builds well before this one. I've seen references to the same issue as far back as 1803. Something MS has just never fixed. There are a handfull of reports in the Feedback hub for this issue.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-04-11T23:15:51+00:00

    I just completed an upgrade so I had a way to test the command. I copied and pasted from my reply above, to be sure that I had no typo here in the Forum post. Below you can see that it worked, pointing to the Windows.old folder as /Source, although this PC does not have any .NET issue to begin with.

    The CBS.log shows all the details of how it ran.  Your CBS.log should also indicate what happens when you try.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-04-11T21:27:37+00:00

    It could be. I was expecting your list to be missing some items. The unusual items that you do show in your Features are sub-components of some of the parent items.

    Are you certain that you typed the DISM command with /Source correctly? Below is the DISM help screen describing it. You can copy the command from the above Forum post and paste it into your Administrator Command Prompt by right-clicking the Command Prompt screen. I am wondering if you missed the "/"?

    C:\Windows\system32>DISM /Online /Enable-Feature /?

    Deployment Image Servicing and Management tool

    Version: 10.0.18362.1

    Image Version: 10.0.18362.53

    /Enable-Feature /FeatureName:<name_in_image> [/PackageName:<name_in_image>]

      [/Source:<source>] [/LimitAccess] [/All]

      Enables the feature specified by the FeatureName command argument.

      You do not have to specify the /PackageName if it is the Windows Foundation Package.

      Otherwise, use /PackageName to specify the parent package of the feature.

      Multiple /FeatureName arguments can be used if the features are components in

      the same parent package.

      You can restore and enable a feature that has previously been removed from the

      image. Use the /Source argument to specify the location of the files needed to

      restore the feature. Multiple /Source arguments can be used.

      Use /LimitAccess to prevent DISM from contacting WU/WSUS.

      Use /All to enable all parent features of the specified feature.

        Example:

          DISM.exe /Online /Enable-Feature /FeatureName:Hearts /All

          DISM.exe /Image:c:\offline /Enable-Feature /FeatureName:Calc

            /PackageName:Microsoft.Windows.Calc.Demo~6595b6144ccf1df~x86~en~1.0.0.0

          DISM.exe /Image:c:\offline /Enable-Feature /FeatureName:Feature

            /Source:c:\test\mount

    Was this answer helpful?

    0 comments