Most likely it is because we use TripleDES encryption at the moment. We will update to AES256 in probably the next version. Meanwhile you can disable that error in the registry.
Turn off FIPS Cryptography via Local PoliciesTo turn off FIPS Cryptography using the Local Policies, follow these steps:
Press the key combination WINDOWS_KEY+R to launch the Run dialog.
Type secpol.msc into the dialog and click OK.
In the Local Security Policy Management Console window that opens, use the left tab to navigate to the Local Policies>Security Options.
Scroll down the right pane and double-click System Cryptograph: Use FIPS compliant algorithms for encryption, hashing, and signing.
In the Properties window, select the Disabled option and click the Apply button.
Close the Properties window by clicking OK.
Close the Local Security Policy Management Console.
Turn off FIPS Cryptography via the RegistryTo turn off FIPS Cryptography using the Registry, follow these steps:
NOTE: Before making any changes to the Registry, you should back it up so you can restore the settings should something go wrong.
Press the key combination WINDOWS_KEY+R to launch the Run dialog.
Type regedit into the dialog and click OK.
If running Windows Server 2008
Navigate to HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled.
Change the value of this registry entry to 0 to disable it.
If running Windows Server 2003 or Windows XP:
Navigate to HKLM\System\CurrentControlSet\Control\FIPSAlgorithmPolicy.
Change the value of the registry entry to 0 to disable it.
FIPS Cryptography should now be disabled and DigiScope should start without issue.