How to Fix Recurring Outlook Sign-In Problems in RDS and FSLogix
Question details
Users experience continuous disconnects or recurring credential prompts in Outlook when operating within Remote Desktop Services (RDS) and FSLogix environments, particularly after password changes.
- Product
- Microsoft Outlook
- Device & OS
- not provided
- Scenario
- Accessing Outlook emails in an RDS environment using FSLogix profile containers, often following a user password change.
- Observed behavior
- Outlook repeatedly disconnects or asks for user credentials, occasionally throwing authentication errors like 58tm1 and 62ubh.
Ensure you have administrator access to the RDS server and backup your Windows Registry before making any system-level configuration changes.
Review Registry and FSLogix Configuration Settings
Adjust Workplace Join and FSLogix identity roaming settings in the registry to prevent recurring credential prompts.
In RDS environments, FSLogix identity roaming and federated account credential storage can sometimes conflict with Workplace Join. Adjusting these settings aligns your server with Microsoft's recommended configuration for shared environments.
Press Windows + R, type 'regedit', and press Enter to open the Registry Editor. Click File > Export to create a safe backup of your current registry settings.
Navigate to the relevant Microsoft recommended registry paths for Workplace Join and Remote Desktop password prompts, ensuring that silent authentication and federated credential storage are properly configured to allow seamless roaming.
Check your FSLogix Group Policy Objects (GPOs) or registry settings to confirm that identity roaming is enabled and properly handling Microsoft Entra ID (formerly Azure AD) tokens.
Once the configuration changes are applied, restart the RDS server to ensure the new registry and FSLogix policies take effect for all user sessions.
Open a Microsoft Support Case for Backend Synchronization
If local RDS settings do not resolve the issue, the root cause may be a backend synchronization problem requiring Microsoft's intervention.
Looking for a Lighter Alternative to Heavy Office Environments?
Troubleshooting complex RDS, FSLogix, and Outlook sync issues can be exhausting and time-consuming. If you need a reliable, lightweight office suite that bypasses complex backend server configurations while maintaining full format compatibility, consider switching to WPS Office.
- 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install the Software: Run the downloaded installer and follow the on-screen instructions to complete the setup.
- 3. Open and Edit Your Files: Launch WPS Office and easily open all your existing Microsoft Office documents without worrying about formatting issues.

Frequently Asked Questions
What causes Outlook errors 58tm1 and 62ubh in RDS environments?
These errors are typically related to authentication token failures, profile configuration mismatches, or identity roaming issues within FSLogix when the system attempts to store or retrieve federated account credentials.
Do I need to modify the registry to fix FSLogix credential prompts?
In many cases, yes. Modifying registry keys for Workplace Join and Remote Desktop password prompts is often required to align the RDS environment with Microsoft's recommended FSLogix settings.
Why does Outlook keep asking for passwords after a password change in FSLogix?
This happens because the cached authentication tokens in the FSLogix profile container become out of sync with Active Directory or Entra ID, causing recurring authentication requests until the old tokens are cleared or properly synchronized.
Can Microsoft fix the backend synchronization issue without local changes?
Yes, some enterprise users have reported that contacting Microsoft Support allowed the backend team to run diagnostics and repair the organization object between Exchange Online Protection and Exchange Online, completely resolving the issue without any local RDS server changes.




