RSA Product Set: SecurID
RSA Product/Service Type: RSA MFA Agent for Microsoft Windows
Version(s): All supported versions
After installing MFA 2.3.x, when a user attempts to authenticate via the credential provider or MFA test utility (e.g., at Windows logon), the process fails with an unhandled exception error dialog.
The error message when testing from MFA test utility :"ERROR: An unhandled exception has occurred in your application... Exception Text: System.OutOfMemoryException: Out of memory. at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement) at RSA.Authentication.Cas.UI.Views.AuthMethodUserControl.SetLogonPicture(String pictureFilePath)..."
Clicking any button in the error dialog (Continue or Quit) causes the operating system to become unresponsive, requiring a hard reboot.
From the MFA logs, we see the following error:[E] [RSA.Authentication.Cas.UI.Views.MfaDialogForm.MfaDialogForm_Load] Exception loading Custom Logo. Check the path to the image file.Parameter is not valid.
The issue is caused by a corrupt or unreadable user account picture (tile image) file located at:C:\Users\Public\AccountPictures\<User_SID>
The MFA credential provider attempts to load this image to display a familiar user interface during authentication. If the image file is corrupted, oversized, or in an invalid format, the System.Drawing.Image.FromFile method fails to process it, throwing an "Out of Memory" exception. This exception is unhandled, crashing the credential provider process and destabilizing the Winlogon process, which leads to the OS crash.
You can apply one of the following solutions:
Option 1: Remove the Image and Apply Registry Fix
-
Boot the machine into Safe Mode or use an alternate administrative account.
-
Delete all
user.*andguest.*files from this directory:%PROGRAMDATA%\Microsoft\User Account Pictures\ -
Open the Registry Editor (
regedit). -
Navigate to this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer -
Create or modify the
UseDefaultTileDWORD value and set its data to0. -
Reboot the machine.
Option 2: Replace the Corrupt User Image
-
Boot the machine into Safe Mode or use an alternate administrative account.
-
Navigate to the affected user's directory:
C:\Users\Public\AccountPictures\<SID>\ -
Replace the existing corrupt image file with a new, valid, and small-sized image file (e.g., a PNG or JPG under 100KB). Ensure the new file has the same name as the original.
-
Reboot the machine.
Related Articles
Microsoft Office 365 - SAML My Page SSO Configuration - RSA Ready Implementation Guide 125Number of Views How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle 81Number of Views Revoked local entitlements are auto-completed by the system after collections are run in RSA Identity Governance & Lifecycle 68Number of Views 'Direct Members Missing' column under Role Entitlements tab incorrectly shows deleted, terminated and/or Role Members no l… 99Number of Views Microsoft Office 365 - RSA Ready Implementation Guide 322Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide