In short, you need to enforce your system to be FIPS compliant:
1) Open gpedit.msc
2) Windows Settings, Security Settings, Local policies, Security options
3) Enable "System Security: Use FIPS compatible algorithms" to reproduce the problem
4) Disable it (not suggested if you're using specialized software that requires proper security!) to make the problem disappear
No need to reboot, changes are immediate.
This option enables itself when installing specialized software or enabling specific Enterprise features that require particular protocol security. Since RPH is not FIPS-compliant, it crashes on startup when initiating the MD5CryptoServiceProvider class.
If that option is automatically enabled for you it means that some programs require it. I don't suggest disabling it. Follow the non-invasive fix to exempt RPH from being FIPS-compliant:
Note: All the diagnostics, troubleshooting, checks, memory dump readings, event viewer readings have been performed by me without any help of any kind. I actually worked to detect and fix the problem myself without any help. I hope that, after this, RPH moderators won't dislike my videos and flame me as always for being salty.
0 Comments