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-11T07:16:52+00:00

    Here is a PowerShell command that will list all of the available Windows Features and their State:

    Get-WindowsOptionalFeature -Online | Sort-Object State,FeatureName | Format-Table

    What my list shows as enabled is:

    Containers-DisposableClientVM                                   Enabled

    FaxServicesClientPackage                                        Enabled

    Internet-Explorer-Optional-amd64                                Enabled

    MediaPlayback                                                   Enabled

    Microsoft-Hyper-V                                               Enabled

    Microsoft-Hyper-V-All                                           Enabled

    Microsoft-Hyper-V-Hypervisor                                    Enabled

    Microsoft-Hyper-V-Management-Clients                            Enabled

    Microsoft-Hyper-V-Management-PowerShell                         Enabled

    Microsoft-Hyper-V-Services                                      Enabled

    Microsoft-Hyper-V-Tools-All                                     Enabled

    Microsoft-Windows-Client-EmbeddedExp-Package                    Enabled

    Microsoft-Windows-NetFx3-OC-Package                             Enabled

    Microsoft-Windows-NetFx3-WCF-OC-Package                         Enabled

    Microsoft-Windows-NetFx4-US-OC-Package                          Enabled

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

    MicrosoftWindowsPowerShellV2                                    Enabled

    MicrosoftWindowsPowerShellV2Root                                Enabled

    MSRDC-Infrastructure                                            Enabled

    NetFx4-AdvSrvs                                                  Enabled

    Printing-Foundation-Features                                    Enabled

    Printing-Foundation-InternetPrinting-Client                     Enabled

    Printing-PrintToPDFServices-Features                            Enabled

    Printing-XPSServices-Features                                   Enabled

    SearchEngine-Client-Package                                     Enabled

    SmbDirect                                                       Enabled

    WCF-Services45                                                  Enabled

    WCF-TCP-PortSharing45                                           Enabled

    WindowsMediaPlayer                                              Enabled

    WorkFolders-Client                                              Enabled

    A corresponding command to enable a Windows Feature in PowerShell would be:

    Enable-WindowsOptionalFeature -Online -FeatureName WCF-TCP-PortSharing45 -All

    I am not sure which .NET features you need, but the command to enable them should be about the same, using the right FeatureName.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-04-11T05:13:17+00:00

    I think maybe PkgMgr.exe has been deprecated in your system while it exists in system in cn language. Let’s try command dism instead of pkgmgr, which means the content in bak file is:

    start /w dism /iu:Microsoft-Windows-NetFx3-OC-Package

    start /w dism /iu:Microsoft-Windows-NetFx4-US-OC-Package

    start /w dism /iu:Microsoft-Windows-NetFx3-WCF-OC-Package

    start /w dism /iu:Microsoft-Windows-NetFx4-WCF-US-OC-Package

    And run it as admin again, let’s see if there is difference.

    Unfortunately, still no difference. Note that I no longer have ".NET Framework 3.5" or ".NET Framework 4.8 Advanced Service" in my list of Windows Features & instead I just have ".NET Environment".

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-04-11T03:59:19+00:00

    You could download 18362.53 from UUP dump and do a manual in-place update.

    You won't lose apps or files. Instructions here (1st post, 2nd half) applies to any build number.

    The script will take longer than usual because it will incorporate the CUs into the ISO image.

    Good idea. I'll do that tonight. Thanks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-04-11T03:39:50+00:00

    You could download 18362.53 from UUP dump and do a manual in-place update.

    You won't lose apps or files. Instructions here (1st post, 2nd half) applies to any build number.

    The script will take longer than usual because it will incorporate the CUs into the ISO image.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-04-11T03:31:02+00:00

    Indeed, something isn't right. I've thought about doing a "Reset this PC", but haven't gone there yet.

    Was this answer helpful?

    0 comments No comments