This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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.
18912 is an Insider build and has an expiry date. You had asked if you would be able to upgrade again to 18912 if .NET remains not working after rolling back to 18362. The ISO provides the best way to do that, if you need to.
There is no point in using the ISO on the same build if it is already working well.
If you can roll back to the 18362 public build and keep .NET working, that would probably be best. But I don't know if that will work.
18912 is an Insider build and has an expiry date. You had asked if you would be able to upgrade again to 18912 if .NET remains not working after rolling back to 18362. The ISO provides the best way to do that, if you need to.
There is no point in using the ISO on the same build if it is already working well.
If you can roll back to the 18362 public build and keep .NET working, that would probably be best. But I don't know if that will work.
Rolling Back isn't a solution for everyone. The roll back did not work on 2 of the test computers we tried it on.
I have a mix of enterprise and Pro Windows 10 builds and they all have this .net Problem. I can't go with insider down load solution as some of the computers are production machines. I can't afford to have untested updates in them.
What is Microsoft doing to fix this issue it's not even on the https://docs.microsoft.com/en-us/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019 that supposed to have known issues.
This time, .NET has been fixed by the 18912 upgrade. The question is whether rolling back to 18362 will break .NET again or not.
Hello,
I'm in a fresh install of Windows 10 Pro 1903,
installation done through usb key generated by the Windows tool.
I have to same .NET problems listed here, not possible to install, weird "extensivity" things, and my log viewer is not lauching, nor my powershell ( mscoree.dll ).
so even a fresh install, with a brand new Hard Drive has the problem.
anybody found anything ?
There is a Command that you can try, using an Administrator Command prompt:
DISM /Online /Enable-Feature /All /NoRestart /FeatureName:Microsoft-Windows-NetFx3-OC-Package /FeatureName:Microsoft-Windows-NetFx4-US-OC-Package /FeatureName:Microsoft-Windows-Client-EmbeddedExp-Package /FeatureName:Microsoft-Windows-NetFx3-WCF-OC-Package /FeatureName:Microsoft-Windows-NetFx4-WCF-US-OC-Package
Copy the above command (all one line). You should be able to just right-click in the Command Prompt window to paste it in there. You should then restart and run optionalfeatures.exe check to see if anything has changed.
Otherwise, installing the latest Insider Fast Ring build should fix .NET. If you have no desire to be running pre-release Windows 10 until sometime in the Spring of 2020, you could then try rolling back to the current public build, but I don't know if .NET will remain fixed or not. Or you can just stay with Insider build 18912, if it seems stable enough, until then, by putting your PC in the Insider Release Preview Ring.
You can download build 18912 from this web page:
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso
Mount the ISO file in Windows, which will create a new drive letter and run setup.exe to upgrade. If you are not in the Insider program, you will need to join to download the ISO.
