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-04-27T20:15:00+00:00

    You can try some of the fixes that were described here in this thread. Sometimes they work.

    Check if the .NET features appear as they normally do in your Control Panel Features. If so,  NET can probably be fixed using DISM or PowerShell.

    Normal list is potentially repairable:                                            The appearance on the right has no known fix that I have found:

        

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-04-27T20:06:22+00:00

    I inadvertently upgraded to 18362 and now .NET will not start. I tried to restore to several earlier restore points and that fails also.

    I tried to install Insider Preview 18885.1001 and that failed also. 

    My home automation software runs on this system and needs .NET 4.0.

    When is Microsoft going to resolve this issue? 

    This is unacceptable.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-04-19T06:26:29+00:00

    I have a Hyper-V VM in which I have replicated this issue. I have tried Windows Reset as well as an in-place upgrade (to the same build number).  Neither one fixed it. The VM was originally a clean install of build 18362.30.  I am unable to remove the .30 CU.  It keeps upgrading itself to 18362.53, although that CU I can remove.

    In my research, there seems to be some indication that adding KB updates or Language Packs when these .NET symptoms exist, may make it impossible to repair. Uninstalling the KB update or Language Pack has sometimes helped (with Servers).

    So the simplest fix is a total wipe and clean install. I did not have this issue until I totally uninstalled .NET on this VM.  It is the missing Parent Features that are blocking the reinstallation of .NET Features.  The Parent Features are not the same type of Feature On Demand as what we see in the Windows Features Control Panel.

    An example of one of the chains of .NET features from a working system is below.

    PS C:> Get-WindowsOptionalFeature -Online -Verbose -FeatureName NetFx4Extended-ASPNET45                                                                        VERBOSE: Target Image Version 10.0.18362.53

    FeatureName      : NetFx4Extended-ASPNET45

    DisplayName      : ASP.NET 4.8

    Description      : ASP.NET 4.8

    RestartRequired  : Possible

    State            : Disabled

    CustomProperties :

                       ServerComponent\Description : .NET Framework ASP.NET 4.8

                       ServerComponent\DisplayName : ASP.NET 4.8

                       ServerComponent\Id : 429

                       ServerComponent\InstallWithParentByDefault : true

                       ServerComponent*Parent : NET-Framework-45-Core*

                       ServerComponent\Type : Feature

                       ServerComponent\UniqueName : NET-Framework-45-ASPNET

                       ServerComponent*NonAncestorDependencies\ServerComponent\UniqueName : NET-Framework-45-Extended*

                       ServerComponent\Deploys\Update\Name : NetFx4Extended-ASPNET45

                       ServerComponent\Version\Major : 4

                       ServerComponent\Version\Minor : 5

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-04-19T06:02:21+00:00

    i did have, im unable to check now.... im going to do a repair windows on my system or wipe out and start fresh. Havent decided yet. Thank you for the info, I was reading about some known issues after updates as well.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-04-19T05:08:28+00:00

    Same exact problem, same exact build and update .. although I went in and turned a few features back on in components, not I cant access all of my control panel...

    Do you have any remaining .NET features in Control Panel? If so, the pkgmgr fix might help.

    Was this answer helpful?

    0 comments No comments