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.
RodgerW2's advice for the repair install could work best.
I have seen others struggling with .NET in other builds and .NET seems almost impossible to fix, once it is broken. It all comes from the Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.18362.1 part of Windows 10.
What do you see if you run:
DISM /Online /Get-Packages /Format:Table
Mine shows that Foundation Package as installed. That is where the .NET, etc. appears to come from.
Wow! My features are pretty messed up then. I suspect a rebuild coming up in the very near future.
You could've installed on top like we talked about and be long done with it. ;)
Wow! My features are pretty messed up then. I suspect a rebuild coming up in the very near future.
This shows where some of the unusual items in your Windows Features list actually belong. They are subcomponents of other items.
You're correct. The /Source switch is definitely a valid option. I copied & pasted the command from your post, so I'm pretty sure it's correct.
This seems to be an occassional & ongoing issue various people have encountered over various builds well before this one. I've seen references to the same issue as far back as 1803. Something MS has just never fixed. There are a handfull of reports in the Feedback hub for this issue.
