I can confirm that an upgrade to a higher Windows build or version does fix .NET. I could not find any other way to repair it.
Can't enable .NET Environment in Windows 10 1903
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.
177 answers
Sort by: Most helpful
-
Anonymous
2020-03-21T04:39:43+00:00 -
Anonymous
2020-03-19T22:04:43+00:00 For installing the latest CU try this:
Install this SSU: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4541338
Then install the CU: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4551762
As for upgrading to Version 1909, have you tried via the ISO? Just download the ISO file, mount it in Windows and run setup.exe to change from version 1903 to 1909. Because this is a cosmetic change to the Windows version number, it is not a full OS upgrade, but it does enable some things. This will also auto-install the latest Cumulative Update.
-
Anonymous
2020-03-19T21:48:29+00:00 I actually did spend a lot of time yesterday testing. I installed version 1909 and was able to use my usual method to create the .NET fail. However, I could not fix it in any way that I tried. I even tried some methods that I had found online that involved replacing .MUM files in the C:\Windows\servicing\packages folder with files from the original ISO and then doing an in-place repair install (re-running setup.exe from install media for the same version that you have installed). But even a Windows Reset does not fix things. It has to be a clean-install, as what is needed for .NET to work after a Windows Reset simply isn't in the image anymore.
I have seen some explanations of why removing various packages makes them almost impossible to install. The mystery then is how in some cases .NET gets restored. An actual Windows OS build upgrade seems to work for anyone who needs to preserve their existing installed software, so upgrading to Insider Slow Ring build 19041.xxx should work.
I was able to use the following commands to remove or to install NetFx3. Removing the Capability made it impossible to install the latest .NET CU, but enabling the NetFx3~~~~ Capability enables the .NET CU to install.
DISM /Online /Remove-Capability /CapabilityName:NetFx3~~~~
DISM /Online /Add-Capability /CapabilityName: NetFx3~~~~
Here is the latest .NET CU:
http://catalog.update.microsoft.com/v7/site/Search.aspx?q=4537572
KB 4537572 Details:
-
Anonymous
2020-03-19T20:24:20+00:00 Hi Don,
That's okay. There's no need to test. I've already resolved to reinstall windows and bypass the problematic update (KB4495620). I noticed in my update history that the breaking update was literally the first update (June 5, 2019) and since then few updates have successfully completed. At this point I'm far more concerned about drivers and security fixes being out of date.
I also noticed, that since going through your fix steps that a few other items have mysteriously started reporting errors again. Skype for instance used to report errors upon loading into windows. Presumably that went away the same time I downloaded the update and I've not seen it since I enabled .NET 3.X yesterday.
The step I'm stuck on - after enabling .NET 3.X, I still can't complete an install of CUs. I tried installing KB4551762 for 1903 and even tried updating to 1909 but am unable to.
Again, thanks for all your efforts in this. It seemed to have helped a lot of people.
-
Anonymous
2020-03-18T18:35:46+00:00 I finally got around to attempt a fix once again, completely forgot I even posted. As per my previous post, here's where things stand:
- C:\Windows\system32>ver Microsoft Windows [Version 10.0.18362.175]
- I uninstalled KB4495620 previously, as I can't find it when I look for it now
- Of the 2 installs, I had to use the second command given later in this thread:
F:\sources\sxs>dir/w Volume Serial Number is D65D-2B2C Directory of F:\sources\sxs [.] [..] Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~.cab microsoft-windows-internetexplorer-optional-package~31bf3856ad364e35~amd64~~.cab Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~.cab microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab 4 File(s) 73,125,945 bytes 2 Dir(s) 30,358,962,176 bytes free F:\sources\sxs>c: C:\Windows\System32>DISM /Online /Add-Package /PackagePath:F:\Sources\sxs Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.175 Processing 1 of 4 - Adding package Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~11.0.18362.1 [==========================100.0%==========================] Processing 2 of 4 - Adding package Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64
11.0.18362.1 [==========================100.0%==========================] Processing 3 of 4 - Adding package Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~10.0.18362.1 [==========================100.0%==========================] Processing 4 of 4 - Adding package Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd6410.0.18362.1 [==========================100.0%==========================] The operation completed successfully. C:\Windows\System32>DISM /Online /Get-CapabilityInfo /CapabilityName:NetFx3~~~~ Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.175 Capability Identity : NetFX3~~~~ Name : NetFX3 State : Installed Display Name : .NET Framework 3.5 (includes .NET 2.0 and 3.0) Description : .NET Framework 3.5 (includes .NET 2.0 and 3.0) Download Size : 72.70 MB Install Size : 495.77 MB The operation completed successfully.Before running, I checked the version and the state reported 'superceded'. After running the command, I was able to install KB4495620 (did not work when 'superceded'). I checked the features list but it still looks broken. Maybe I need a reboot? Also, strangely, I noticed I'm still running the same build (18362.175) almost a year later. I'll update later today, whether or not the .NET fix works.
In response to A. User: Here are my Bug Origination steps:
- Grabbed install ISO from windows, put on recovery usb drive
- Fresh install Win10 pro on brand new WD Blue 1.5 TB SSD May or June 2019
- Installed win version 1903, 18362.175
- Upon attempts to install apps that rely on .NET capability - actually fine, was able to play some games from Epic Games launcher
- A few days later, everything broke. Attempts to reinstall apps showed the .NET compatibility failure
- Eventually got to this site, discovered I have the same broken 'optional features' list where I can't enable .NET versions
- Tried running the install/run DISM commands, didn't work
- Uninstalled KB4495620