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-15T06:45:54+00:00

    These are in my "Disabled" list & can't be enabled (error 50 - The operation is complete but Microsoft-Windows-Client-EmbeddedExp-Package feature was not enabled.".

    Microsoft-Windows-Client-EmbeddedExp-Package

    Microsoft-Windows-NetFx3-OC-Package

    Microsoft-Windows-NetFx3-WCF-OC-Package

    Microsoft-Windows-NetFx4-US-OC-Package

    Microsoft-Windows-NetFx4-WCF-US-OC-Package

    These don't appear as either enabled or disabled & trying to enable them results in error 0x800f080c (Feature name NetFx4-AdvSrvs is unknown)

    NetFx4-AdvSrvs

    WCF-Services45

    WCF-TCP-PortSharing45

    The inability to enable .NET may be related to feature "NetFx4-AdvSrvs" being unavailable.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-04-15T05:31:48+00:00

    I tested the below commands today myself, so this might be one to start with:

    DISM /Online /Get-Features /PackageName:Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.18362.1 /Format:Table

    If you add | sort /+50 at the end, it will sort your Enabled Features toward the top of the list (sorting by the 50th character of the output lines).

    This should hopefully give you the entire list of Feature names that you can enable via DISM (or probably via pkgmgr as well). In case it does not provide the list, I will post my enabled Features here (I excluded Hyper-V and Sandbox):

    FaxServicesClientPackage

    Internet-Explorer-Optional-amd64

    MediaPlayback

    Microsoft-Windows-Client-EmbeddedExp-Package

    Microsoft-Windows-NetFx3-OC-Package

    Microsoft-Windows-NetFx3-WCF-OC-Package

    Microsoft-Windows-NetFx4-US-OC-Package

    Microsoft-Windows-NetFx4-WCF-US-OC-Package

    MicrosoftWindowsPowerShellV2

    MicrosoftWindowsPowerShellV2Root

    MSRDC-Infrastructure

    NetFx4-AdvSrvs

    Printing-Foundation-Features

    Printing-Foundation-InternetPrinting-Client

    Printing-PrintToPDFServices-Features

    Printing-XPSServices-Features

    SearchEngine-Client-Package

    SmbDirect

    WCF-Services45

    WCF-TCP-PortSharing45

    WindowsMediaPlayer

    WorkFolders-Client

    Then try adding each sub-Feature, but add the /All switch to hopefully install whatever Parent Features each sub-Feature requires.

    DISM /Online /Enable-Feature /FeatureName:MicrosoftWindowsPowerShellV2 /All

    C:\Windows\system32>DISM /Online /Enable-Feature /FeatureName:MicrosoftWindowsPowerShellV2 /All

    Deployment Image Servicing and Management tool

    Version: 10.0.18362.1

    Image Version: 10.0.18362.53

    Enabling feature(s)

    [==========================100.0%==========================]

    The operation completed successfully.

    Since I don't have your situation to test with, I am mostly speculating that this could work.  You could also try these with pkgmgr I assume.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-04-15T04:16:48+00:00

    There are many people run into the exact same problem in Chinese community. What I know is that my solution works out and no one report the deprecated thing.

    I just tried running the individual commands one-by-one & they all worked this time. No errors re being deprecated. No idea why.

    Unfortunately for me, it still doesn't fix this issue. I have NO ".NET Framework" (either 3.5 or 4.8) entries in my "Windows Features" list & instead have the 3 highlighted entries below, which are actually child features of a couple of other parent features

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-04-15T00:19:22+00:00

    My pleasure. Glad to help!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-04-15T00:16:46+00:00

    There are many people run into the exact same problem in Chinese community. What I know is that my solution works out and no one report the deprecated thing.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments