It looks like there are several errors related to cryptographic algorithms, particularly MD5, not being part of the Windows Platform FIPS validated cryptographic algorithms.
***FROM RUNTIME LOG***
-------------------
2024-05-13T15:12:44: ERROR: soft handled
2024-05-13T15:12:44: System.TypeInitializationException: The type initializer for '#=randomstring$randomstring=' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
2024-05-13T15:12:44: at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
-------------------
***SOLUTION(?)***
Editing the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy by changing the value of "Enabled" from 1 to 0 seems to have fixed the issue.
***FROM RUNTIME LOG***
-------------------
2024-05-13T15:12:44: ERROR: soft handled
2024-05-13T15:12:44: System.TypeInitializationException: The type initializer for '#=randomstring$randomstring=' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
2024-05-13T15:12:44: at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
-------------------
***SOLUTION(?)***
Editing the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy by changing the value of "Enabled" from 1 to 0 seems to have fixed the issue.