Forum Discussion
Yoann
Aug 18, 2021Copper Contributor
Windows Server 2019 and .NET 4.8?
Hello, On a fully updated Windows Server 2019, roles and features allow me to install only .NET 4.7. One of the solution we are using require .NET 4.8 (Adaxes). When I install .NET 4.8 us...
RichardA
Dec 14, 2022Copper Contributor
Genuis! I don't know who originally solved this, but your solution worked, thanks very much. After many hours of repairing .NET, rebooting and getting the same error, going around in circles I eventually found this post and it worked. Thanks!
- LordHellFireOct 24, 2024Copper Contributor
RichardA
I figured out the solution to copy .net registry settings from a working computer back in march '22 after working the problem sweating bullets for hours myself trying to fix our tertiary ADC-server. Luckily the primary and secondary were not hit with the same problem.No amount of uninstalling/installing fixed it.
But "simply" export the reg keys from a working computer and import them in the broken server, and that worked. A restart is always a good idea to ensure everything starts up properly.
I'm mortified that Microsoft still haven't fixed the problem/issue... that it is still occurring even now!
The original problem-poster (User named: action-undo-balance) of the BleepingComputer forum mentioned this as the potential cause of the problem:After many many hours of research on this I've gotten to the bottom of this. The issue is this TLS 1.2 enforcement script:
Only a few days ago this script was different - it wasn't wrapped in that "if" statement. You can see the commit here:
The problem is this line:
New-Item 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319' -Force | Out-Null
Which creates that path (if it doesn't exist). If it does exist (which it does by default on Server 2019) it empties it.
Microsoft could probably fix the problem by changing the installer to always recreate those redirects for earlier versions of .net.