I'm sorry, I have to strongly disagree with the fellow saying create new threads. It creates redundancy and when people are searching for anwers, they get 50 different threads. It's good to have a popular thread with different viewpoints and opinions.
I had this same exact error/problem with a fresh install of Server 2019. The FIPS Cryptography local policy setting did not work.
Trying the 2 reg hacks now. Couldn't actually write to registry because of weird vsphere permission thing, despite me being an admin on the machine.
Okay the reg hacks worked! THANK YOU FOLKS.
set strong cryptography on 64 bit .Net Framework (version 4 and above)
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type Dword
set strong cryptography on 32 bit .Net Framework (version 4 and above)
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type Dword