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.
As I said on my previous reply, no issues for me.
I don't know what it is but there must be something else causing the failure.
This a fresh install of Build 18362.175 (x64) to SSD using the current ISO available from MCT.
As you can see, .NET 4.8 was installed properly and .NET 3.5 was successfully installed via PS.
Hey all,
I installed Windows 10 1903 for my girl friend on a new computer on 2019-06-02.
I installed it with an usb drive created by the media creation tool (https://www.microsoft.com/de-de/software-download/windows10).
She tried to open the game "The Sims 3" from Origin. But it failed to start showing an error.
The error has the code 0xC0000135. After some research I found out that the .NET Framework is missing.
So I tried to install .NET with optionalfeatures.exe. There I can find the features ".NET Extensibility 4.8" and ".NET Extensibility 3.5" and ".NET Environment". When I tried to enable them, the feature installer finished the installation without an error. But when I open optionalfeatures.exe again, the features are unselected.
My last idea was to open powershell.exe and to install the features with the Install-Feature command let. But when I tried to open PowerShell I got an error that mscoree.dll is missing. So I can not use powershell.
I tried to uninstall the update KB4495620 and to run the command "DISM /Online /Add-Capability /CapabilityName:NetFx3~~~~". But it failed.
I also tried the command "DISM /Online /Add-Capability /CapabilityName:NetFx3~~~~ /Source:E:\Sources\sxs" and it failed again.
Do you have an idea, how I could fix the issue?
Greetings from Hamburg, Germany :-)
Definitely still an issue with a fresh install of 18362.175 (on a fresh SSD to boot)
No issue here, there must be something else involved...
This a fresh install of Build 18362.175 (x64) to SSD using the current ISO available from MCT.
As you can see, .NET 4.8 was installed properly and .NET 3.5 was successfully installed via PS.
Perhaps you misread my last post. You can stay on the current public build if my repair steps work for you.
Definitely still an issue with a fresh install of 18362.175 (on a fresh SSD to boot)
Was able to uninstall the KB4495620 update but attempting to run the DISM command resulted in Error: 14081 The referenced assembly could not be found.
This took over a week of digging to even get to this thread. It's not an easily identifiable issue as most programs that rely on .NET compatibility components are not throwing errors that indicate this is what's wrong. Worse, there are a lot of instructions and installation options to download various versions of .NET but they're basically all pointless since you literally are unable to do so but instead must enable it through optional features. This is outrageous that I must hop on a beta branch in order to get a fix so at least 3 applications can work prior to Spring 2020.
