RSA Authentication Agent 7.3.3 for Windows prompt does not appear after the first reboot of Windows 10 when McAfee SafeBoot is installed
Originally Published: 2018-02-20
Last Modified: 2022-06-20
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Windows
RSA Version: 7.3.3
Issue
- When McAfee SafeBoot (now known as McAfee Drive Encryption [DE]) is installed on a machine running Windows 10 that also has the RSA Authentication Agent 7.3.3 installed, every time the machine is booted. the RSA SecurID prompt does not display.
- Once logged in, if a user locks the machine and unlocks it, it starts prompting for RSA SecurID credentials and the user authenticates successfully.
- Subsequent logins work as expected.
- The SecurID prompt does not appear after the first reboot on Windows 10.
- Tried changing the Credential Manager setting and enabling Exclude the Third-party Credential Providers.
- This behavior has been tested on multiple machines and recreated consistently.
- Exclude the Microsoft Password Credential Provider = Not configured
- Exclude the RSA Credential Provider for disconnect auth = Not configured
- Exclude the RSA Smart Card Credential Provider = Not configured
- Exclude the Third-party Credential Providers = Enabled
- The auto registration client is installed.
Cause
DE/EEPC does not currently support any third-party Windows credential provider integrations. These third-party credential providers are conflicting with the DE/EEPC credential provider because, on Windows systems, it is not possible to chain the DE/EEPC credential provider.
Resolution
The customer needs to engage McAfee to find a workaround. It might be possible to configure SafeBoot to not use its' MfeEpeCredentialProvider, but that needs to be handled by McAfee.
The RSA Authentication Agent 7.3.3 for Windows is functioning as designed.
Related Articles
Node secret mismatch error when authenticating with an RSA Authentication Agent for Windows when NetMotion is installed Number of Views Devices running Windows 10 or Windows 11 operating system crash on reboot the machine after RSA MFA Agent 2.3.x for Windo… Number of Views RSA SecurID Intel based hardware appliance redirected to BIOS after a reboot Number of Views Upgrade from Microsoft Windows 10 to Windows 11 fails with certain versions of the RSA MFA Agent for Windows installed Number of Views Cannot log on to Microsoft Windows 8.1 with RSA Authentication Agent 7.3.x for Windows after Windows update is applied usi… Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog RSA Authentication Manager 8.9 Patches and Hotfixes Readme
Don't see what you're looking for?
