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.
You can go back to the previous version within 10 days of the upgrade. It uses the files from Windows.old to do this. I doubt that this will restore .NET function to v1903, but there may be a small chance of it working. .NET is a unique issue in Windows, so it can behave differently than other things.
It could be with a try. Otherwise, you could be stuck on Insider builds until Spring 2020. If this build is stable, you could pause Windows Update and just use it as-is until then.
You can't go back to a Non Insider build unless
you do a clean install.
Phew!, I am so glad i found this thread. I only built this new PC over the weekend on 1903 (18362.30) and after a couple of auto updates lost .Net in EXACTLY the same way
I was almost on the verge of a rebuild again, despite spending 2 days transferring settings/data etc from old PC.
One suggestion was to try installing kb4498523 to take it to a new 18362 build(can't remember exact build), but Win Update was also dead in the water & giving me a 0x80073701 error. Even the update troubleshooter failed with 0x8007007E
I saw the last few comments mentioning trying the Windows insider Preview 18912.1001 so I hopped on board the Preview Train & it installed OK. Now i have .Net back & all my dead apps are running again :)
My final question is now that I am in the program, is there a safe way to return back to a released (Non-preview) build, without losing this fix? Or am i now stuck in 'unknown territory'
Thanks
Still have the problem at 18362.145...
It happend after the latest cu update
"Solved" upgrading to windows insider 18912.1001
There was a .NET bug with early "dot" builds of 18362. I don't recall the exact "dot" revision it was fixed in (18362.86?), but it's not an issue any longer. If you're installing earlier versions of 18362, save yourself the trouble and skip to a later revision. :)
