58TM1 - Remote desktop server farm FSLogix 25.09

Daniel Soenke 15 Reputation points
2026-01-30T08:04:27.17+00:00

Hi guys,

back again - not easy to fix this issue. I need more ideas, successfuel workarounds or your best practise configuration.

Every day again to logon is not an option for many customers.

FSLogix Version 26.01 is currently not installed - different problems here also reported.

FSLogix 25.09 Version: 3.25.822.19044

OS: Server 2022 Standard / Datacenter

Remote Desktop Serverfarm with Profile and ODFC Containers

Profile Settings

User's image

-Roam Identity - Enabled

ODFC Settings

User's image

  • Include Office Activation Enabled

redirections.xml

<?xml version="1.0"  encoding="UTF-8"?>
<FrxProfileFolderRedirection ExcludeCommonFolders="0">
<Excludes>
<Exclude>%localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy</Exclude>
<Exclude>%localappdata%\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy</Exclude>
<Exclude>%localappdata%\Packages</Exclude>
<Exclude>%localappdata%\Microsoft\TokenBroker</Exclude>
<Exclude>%localappdata%\Microsoft\OneAuth\accounts</Exclude>
<Exclude>%localappdata%\Microsoft\OneAuth\blobs</Exclude>
<Exclude>%localappdata%\Microsoft\Outlook</Exclude>
<Exclude>%appdata%\Microsoft\Outlook</Exclude>
<Exclude>%localappdata%\Microsoft\IdentityCache</Exclude>
<Exclude>HKEY_CURRENT_USER\SOFTWARE\Microsoft\IdentityCRL</Exclude>
<Exclude>HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\AAD</Exclude>
<Exclude>HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WorkplaceJoin</Exclude>
<Exclude>HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity</Exclude>
<Exclude>HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Identity</Exclude>
</Excludes>
<Includes>
</Includes>
</FrxProfileFolderRedirection>

Issue on the User Profile - after every logon

User's image

Manually fixes - not working every time:

Remove-Item -Recurse -Force "C:\Users\<username>\AppData\Local\Microsoft\IdentityCache" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "C:\Users\<username>\AppData\Local\Microsoft\OneAuth" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "C:\Users\<username>\AppData\Local\Microsoft\Office\16.0\TokenBroker" -ErrorAction SilentlyContinue

and also remove the crendentials stored locally on the remote desktop server.

Sometimes it helped to logoff in word/ excel and login again. Close Teams and OneDrive before.

#Update 10:25Uhr:

In this current configuration all apps, but not OneDrive are working after logon with the saved credentials.

Thank you for your reply!

Windows for business | Windows Client for IT Pros | User experience | FSLogix

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kevin Haier 0 Reputation points
    2026-07-02T11:47:11.78+00:00

    Hi, we have the same issue but with Citrix UPM.

    Resetting the users password resolves the issue for a short time but it comes back.
    None of the common solutions mentioned has worked so far.

    Was this answer helpful?

    0 comments
  2. Wouter Simons 6 Reputation points
    2026-03-11T14:36:51.7933333+00:00

    We have the same issue, details:

    • 2 RDS Session hosts (server 2019)
    • 26.01 CU1 (3.26.126.19110)

    Before they had the Office 365 applications installed and an on-prem exchange server. Since they migrated the mail to Exchange online they are getting the 58TM1 error now and then. We have a script to clear the related files and registry entries, log off the user from the RDS, logon again, sign in into M365 and all is good again.

    Some users report that the 58TM1 error comes after Outlook hangs completely and they force it to close. When they start Outlook it gives the 58TM1 error. Additionally, some users have a problem that Outlook closes out of the blue sometimes. Eventviewer shows "Application error" where "mso20win32client.dll" is the faulting module.

    Roam identity is enabled and include office activation as well.

    As noted, this all started after we migrated the mail from on-prem exchange to exchange online.

    Any update from you?

    Was this answer helpful?

  3. Daphne Huynh (WICLOUD CORPORATION) 660 Reputation points Microsoft External Staff Moderator
    2026-02-04T03:53:32.2466667+00:00

    Welcome to the Microsoft Q&A Platform!

    Apologies for the delay in responding to your concern. Based on the details you shared, I would like to provide some information that may help resolve the issue.

    1. Profile Container & ODFC Best Practices

    • Ensure you are using a supported FSLogix version for your environment. FSLogix 25.09 (3.25.822.19044) is known to have issues. Please consider testing with the latest supported version if possible.

    Reference: Known Issues - FSLogix | Microsoft Learn

    FSLogix Release Notes - FSLogix | Microsoft Learn

    • Profile and ODFC containers should be stored on reliable, high-performance network shares with proper permissions.
    • Exclude problematic folders and registry keys in your redirections.xml as you have done, but review exclusions to ensure they do not interfere with Office/OneDrive authentication.

    2. Persistent Credential Issues

    • Problems with persistent credentials (especially for OneDrive, Teams, Office) are common when certain folders or registry keys are excluded from the profile container.
    • Manual deletion of folders like IdentityCache, OneAuth, and TokenBroker may temporarily resolve issues, but is not a sustainable solution.
    • Ensure that Office activation and OneDrive settings are included in the container if persistent sign-in is required.

    3. OneDrive Troubleshooting

    • OneDrive is more sensitive to profile container exclusions and may require specific folders to be included for seamless operation.
    • Review the official FSLogix documentation for recommended exclusions/inclusions for OneDrive and Office 365 apps.

    Reference: FSLogix FAQ - FSLogix | Microsoft Learn

    Configuration Settings - FSLogix | Microsoft Learn

    4. General RDS Profile Troubleshooting

    • Check permissions on the profile share and ensure no network latency or connectivity issues.
    • If users experience temporary profiles, verify that the VHD(x) is not locked by another session host.

    I hope this information can help you a bit. Wish you a pleasant day! 

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.