Microsoft 365: Outlook Error [58tm1]

[German]Early February 2025 I came across a post in an administrator group on Facebook where an administrator is talking about the Outlook error "Something didn't work [58tm1]" in Microsoft 365. The error seems to occur frequently.

An administrator points out Outlook 365 error [58tm1]

The administrator concerned wrote that he was using Microsoft 365 Business Premium licenses. The MS 365 applications run on two terminal servers under Windows Server 2022, using FSLogix.

The problem is that some users get the error "Something went wrong [58tm1]" shown in the screenshot above. These users can then no longer log in to Outlook 365. The remedy in this case is to delete the folder Microsoft.AAD.BrokerPlugin_vnggnktrrj in the user profile:

C:\%Userprofile%\AppData\Local\Packages

Then logging in to Outlook 365 works again. The affected person asked whether other administrators also have the problem and whether there is a solution that fixes the problem?

More hits on the internet

If you search for the error [58tm1] on the internet, you will find recurring reports from those affected over the past few months. The screenshot above is from the Microsoft Answers forum post Microsoft Office Error Tag 58tm1 from August 13, 2024, where the error occurs when accessing files in Microsoft Word.

The thread already has three pages, other affected people confirm the problem, but there is no solution (that I can see). One affected person writes that they temporarily fix the error for the affected users by logging out and logging into the 365 account again, e.g. in Word.

In the Microsoft Answers forum thread, Daniel Soenke lists some measures taken by Microsoft support such as logging out and logging in again, deleting the "Microsoft.AAD.BrokerPlugin" folder mentioned above, removing unnecessary accounts and other actions that can be interpreted as voodoo.

I also came across the Microsoft forum post Outlook 365 app error 1001 on RDS environment ( FSLogix) from July 7, 2023, where the error is also complained about. The forum thread now has 27 pages. The last entries are from January 2025 – a solution is not in sight.

Grzegorz Krzyzanowski attempts an error analysis on page 27 in a post from December 2024. You can't really see the breakthrough – the error occurs sporadically and is the combination of Microsoft 365 with RDS Farm under Windows Server 2019.

He has opened a ticket with Microsoft, but there is little hope that anything will come of it. This is because error [58tm1] is a generic error message that can have various causes. On reddit.com, an affected administrator reported in August 2024 that he had solved the problem for himself by upgrading to the latest version of FSLogix and performing some operations. However, I am skeptical that this really helps universally.

The problem seems to be known

Another administrator stated on Facebook that the error [58tm1] in Outlook, especially in an environment with Microsoft 365 Business Premium, Terminal Server 2022 and FSLogix, is a known problem that is often related to authentication and the AAD Broker Plugin.

The solution described above, deleting Microsoft.AAD.BrokerPlugin_vnggnktrrj in the user profile in the AAD Broker Plugin folder, resets the plugin and temporarily fixes the problem. This is not a permanent solution, the user notes.

A combination of FSLogix optimization, updating and re-registration of the plugin could try to solve the problem in the long term. In his post, the user describes possible causes for the generic error [58tm1] in Outlook:

• Corruption of the AAD Broker plugin: Problems with the Microsoft authentication component.
• FSLogix profile management: Conflicts when loading the profiles or accessing the plugin data.
• Invalid tokens: The AAD Broker plugin stores tokens that have expired or are invalid.
  Faulty updates: A faulty update of Windows, Office or FSLogix could cause the problem.
• Group policies or security policies: Restrictions that prevent the plugin from working properly.

In his Facebook post, the administrator outlines some solutions that can be tried in the hope of fixing the problem permanently:

• Outlook reset with the repair function in Office: (Control Panel – Programs – Microsoft 365 Apps – Change – Select the Online repair option. Then perform a restart.
• Attempt an "FSLogix optimization" by ensuring that the latest FSLogix version is installed (download and install the latest version from the Microsoft website).
• Check the settings for the FSLogix profile folder, especially the configuration for Container Locking. This can be checked via the registry editor in the branch HKEY_LOCAL_MACHINE\Software\FSLogix\Profiles. The settings for ConcurrentUserSessions and EnableConcurrentSessions should be configured correctly there.
• Check the group policies to see if there are any settings that affect authentication or the AAD Broker plugin. This should be found in the GPO branch Computer Configuration > Administrative Templates > Windows Components > Authentication. All policies that may block token renewal or the plugin must be deactivated here.
  Re-register the AAD Broker plugin using the following PowerShell commands on the terminal server. This will reset and re-register the plugin.

Get-AppxPackage -Name Microsoft.AAD.BrokerPlugin | Remove-AppxPackage
Add-AppxPackage -register "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode

It was also suggested (already mentioned above) to clear the token cache specifically for all affected users. To do this, delete all content in the:

C:\Users\\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin*

The administrator in question also gave general instructions on how to keep Windows updates and drivers for Windows Server 2022 up to date. It all sounds to me like helpless trial and error with no prospect of success. The group member's advice: "If the problem persists, open a support ticket with Microsoft as this may be a known issue. Refer to similar reports related to [58tm1] and the AAD Broker plugin."

Another group member states that they were able to resolve the problem by activating Roam Identity. The session hosts should then be "Hybrid Joined" and SSO should be activated. The member has linked this guide to work through.

Question to the administrators in the readership: Is this also a problem for you? Is there a better or permanent solution? To me, the whole Microsoft 365 seems like a permanent construction site where everything never works. Since publishing the German edition of this blog post, many administrators has commented. Wout has commented here on April 7, 2025, and wrote, that he also working on a case with Microsoft to get this solved. He shared instructions from Microsoft as "fix" within his comment.