Offline logon failure then loop back to login screen RSA Authentication Agent 7.3.3  for Windows
RSA Product Set: SecurID RSA Product/Service Type: Authentication Agent for Windows RSA Version/Condition: 7.3.3 
Offline authentications on RSA Authentication Agent for Windows 7.3.3  fail with no message; it just loops back to the Credential Provider Logon Screen several times, before finally working.
Slowness in reading or decrypting the offline day files
In the December 2018 Windows 10 release the SHA256 hash computation runs slower, which has a huge impact when the agent must lookup offline day tokencodes or passcodes, which are not stored as clear text numbers but as mathematical hashes. The agent, using the Microsoft SHA256 hash would convert any user entered passcode to a hash then compare to all hashed codes stored in the dayfiles.
This used to take about one second, but with the December 2018 Windows 10 release that hashing time jumped to eight seconds. Multiply that eight seconds by the acceptable tokencode window and multiple again if the user is assigned more than one token and the result is it often takes a very long time (that is, an elapsed times greater than 90 seconds) for the agent to perform an offline one time passcode (OTP) authentication.
It takes so long, in fact, that LogonUI seems to have exceeded a timeout (or something similar). Thus, when the agent's CredProvider eventually returns the user credentials, the LogonUI restarts the credential collection sequence instead of submitting the credentials to Winlogon for authentication.
There is probably code in the crypto libraries that uses the optimal instructions based on the CPU but falls back to the most portable algorithm if the CPU is not recognized [wmic cpu get name].
The user submits credentials at UTC 00:38:51:
2019-03-20 00:38:51.773 13296.784 [V] [Credential::GetSerialization -- MAIN] Enter
We take ~45 seconds to return credentials to LogonUI.
2019-03-20 00:38:52.041 pNameTranslate->Init failed, possibly the Global Catalog is not available. 2019-03-20 00:38:52.041 Caught HRESULT: The specified domain either does not exist or could not be contacted.
2019-03-20 00:38:52.041 ::CheckDirectDomainMember] Failed to get user path, throw E_FAIL 2019-03-20 00:38:52.041 getChallengeType has determined that the user is challenged. 2019-03-20 00:39:36.520 AceGetDAAuthData success: token serial number = 0004******36
2019-03-20 00:39:37.937 ::~CommonAuthenticator] Return 2019-03-20 00:40:07.908 ::LACAuthenticator] Enter 2019-03-20 00:40:07.908 Unable to open preferences key "SOFTWARE\RSA\RSA Desktop Preferences\Local Authentication Settings", return = 0x2 2019-03-20 00:40:07.912 The Challenge Group sAMAccountName policy is <Dom>\<Challenge_Group> 2019-03-20 00:40:08.336 getChallengeType has determined that the user is challenged.
2019-03-20 00:40:13.550 SD_Init succeeded. 2019-03-20 00:40:47.180 AceGetDAAuthData success: token serial number = 0004******36 2019-03-20 00:40:47.681 ::~CommonAuthenticator] Return 2019-03-20 00:41:02.552 ::LACAuthenticator] Enter 2019-03-20 00:41:03.220 getChallengeType has determined that the user is challenged. 2019-03-20 00:41:08.327 ::getSIDUsername (char version)] Return 2019-03-20 00:41:59.996 AceGetDAAuthData success: token serial number = 0004******36 2019-03-20 00:42:00.576 ::~CommonAuthenticator] Return 2019-03-20 00:43:05.797 ::LACAuthenticator] Enter 2019-03-20 00:43:06.243 ::GetAuthDataDir] Return 2019-03-20 00:43:16.481 ::initAceClient] SD_Init succeeded. 2019-03-20 00:43:43.817 AceGetDAAuthData success: token serial number = 0004******36 2019-03-20 00:43:44.604 ::~CommonAuthenticator] Return 2019-03-20 00:43:58.907 ::LACAuthenticator] Enter
5x - AceGetDAAuthData success: token serial number = 0004******36 from 2019-03-20 00:39:36.520 to 2019-03-20 00:44:58.167