How to fix Microsoft Office error 58tm1 in Windows?

The 58tm1 tag means that Outlook, Teams, Word or another Microsoft 365 app on Windows could not finish your sign-in with the token data it saved on this PC. The window shows Something went wrong. [58tm1]. Your account is usually fine: sign out, empty the Office sign-in cache, then reset the AAD Broker plug-in data.

Facts checked on 15 October 2026. Steps written for Microsoft 365 apps and Office on Windows 11 (25H2 and 26H2) and Windows 10 22H2, read against a Microsoft staff answer on Microsoft Q&A and administrator reports.

What Something went wrong [58tm1] means in Outlook, Teams and Office

You open Outlook or Teams, or a file in Word, and a small Microsoft window appears with the heading Error, the red line Something went wrong. [58tm1] and a Close button. After Close the app stays signed out, or asks for the same sign-in again and fails the same way.

The tag is a marker of the place in Microsoft's sign-in code where the attempt stopped. Microsoft publishes no list of these tags. A Microsoft moderator on Microsoft Q&A wrote that 58tm1 with the code 2147942403 "typically indicates issues related to authentication or file access permission", and named corrupted cached credentials and the Microsoft.AAD.BrokerPlugin component as the main causes.

Every spelling people type means the same window: 58tm1, 58tm1 error, error 58tm1, [58tm1], "Something went wrong 58tm1" and "Something didn't work [58tm1]". In Spanish Office the line reads "Se ha producido un error. [58tm1]"; in French people search for "erreur 58tm1". The tag stays the same in every language.

58tm1 in Outlook, Teams, Word and OneDrive

The Microsoft 365 apps on Windows do not each run their own sign-in. They share the Office identity cache and ask a Windows component, the AAD Broker plug-in, for tokens. One damaged entry can therefore stop one app while another, which still holds a valid token, keeps working.

• Classic Outlook: most searches for the tag include Outlook. Administrators report it after a user cannot sign in to Outlook 365 on a terminal server, while the web mail at outlook.office.com works.
• Teams: an administrator on Microsoft Q&A reported 58tm1 in the Teams desktop app on Windows 11 for some users who could sign in to Teams on the web without trouble. A Teams reinstall alone did not end it.
• Word and Excel: the reader's question above is typical. The tag appears when a file from OneDrive or SharePoint is opened and Word has to fetch a fresh token for it.
• OneDrive: the sync app uses the same sign-in layer, so the tag can appear at its sign-in too. The same fixes apply.

What causes error 58tm1, from the most common to the rare

Microsoft has not published a cause for this tag. The ranking below comes from the answer of Microsoft's forum staff, the administrator reports that the BornCity blog collected, and what the error code says. Treat the order as our reading of those reports, not as a statistic.

Home PC, work PC or terminal server: who may run which fix

Fix 1 only clears data in your own user profile and is safe on any PC. Fix 2 and Fix 3 sign Windows out of your work account, so on a PC that an employer or a school manages, ask IT first. Fix 4 and Fix 5 need administrator rights, and Fix 5 is a server task.

How to fix error 58tm1 in Outlook, Teams and Office

The fixes are ordered by how often they end 58tm1 and how little they change. Fix 1 is safe on every PC and is the one to try first. After each fix open the app that failed and sign in. When the app shows your name and stays signed in after a restart, you are done.

Fix 1. Sign out and empty the Office sign-in cache (OneAuth and IdentityCache)

5 minutesLow riskEveryone, first. Above all when only one app fails or the error began after a password change or a reinstall.

OneAuth and IdentityCache hold the accounts and tokens that Office reuses at sign-in. When an entry is damaged or points at data that is gone, Office keeps trying it and stops with 58tm1. Office rebuilds both folders at the next sign-in.

1. Open Word or Excel, select your name or picture at the top right and select Sign out. Sign out of every account listed.
2. Close Outlook, Teams, OneDrive and every other Office app. Quit OneDrive and Teams in the taskbar corner too.
3. Press Win + R, paste this path and press Enter:

   %localappdata%\Microsoft\OneAuth

4. Select everything inside with Ctrl + A and delete it.
5. Press Win + R again, open the second folder and delete its contents too:

   %localappdata%\Microsoft\IdentityCache

6. Restart the PC, open the app that failed and sign in with your account.

Nothing of value is lost: no mail and no files, only saved sign-ins. The administrator in the Teams case on Microsoft Q&A cleared these same two folders, together with %localappdata%\Microsoft\TokenBroker, before reinstalling Teams. If you want an undo, rename the folders to OneAuth.old and IdentityCache.old instead of emptying them.

Fix 2. Clear your user's AAD Broker plug-in data

10 minutesRead the warningFix 1 did not hold, every Office app fails, or 58tm1 comes back after each sign-in. This is the fix administrators report most for terminal servers.

The AAD Broker plug-in is the Windows component that hands Office its work and school tokens, and it stores them per user under Packages. An administrator quoted by BornCity ended 58tm1 for affected users by deleting this folder from their profile; Windows creates it again.

1. Sign out of Office as in Fix 1 and close all Office apps, Teams and OneDrive.
2. Open File Explorer and paste this path into the address bar:

   %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

3. Go one level up to Packages, right-click the folder and select Rename. Add .old to the end of its name.
4. If Windows says the folder is in use, sign out of Windows, sign in again and rename it before you open any app.
5. Restart the PC and sign in to the Office app. Windows creates a fresh plug-in folder.
6. When the sign-in holds for a few days, delete the .old folder.

Do this only in your own profile under %localappdata%\Packages. A Microsoft moderator's reply once pointed at the folder of the same name in C:\Windows\SystemApps, and the user could not delete it even after taking ownership. That folder is the installed Windows component, not your data, and it is repaired in Fix 4 instead.

Fix 3. Remove the saved Office credentials and reconnect the work or school account

10 minutesLow riskA work or school account on a PC you own, when Fix 1 and Fix 2 did not hold.

Windows keeps Office sign-ins in Credential Manager and in the list under Access work or school, and Fix 1 does not touch either. Microsoft's forum staff give both steps for 58tm1: remove the Office credentials, then disconnect and connect the account again to refresh it.

1. Close all Office apps and Teams.
2. Select Start, type credential manager and open Credential Manager.
3. Select Windows Credentials. Under Generic Credentials, expand each entry named MicrosoftOffice16 (older installs may show MicrosoftOffice15) and select Remove.
4. Open Settings > Accounts > Access work or school.
5. Select the account you use for Office, select Disconnect and confirm.
6. Restart the PC, return to Access work or school, select Connect and sign in with the same account.
7. Open the Office app and sign in.

Fix 4. Register the AAD Broker plug-in again with PowerShell

5 minutesLow riskThe sign-in window is blank, closes at once, or Fix 1 to Fix 3 changed nothing.

If the plug-in package is missing or broken for your user, no token it returns can be used. The Microsoft moderator's answer for 58tm1 gives a PowerShell line that registers the package again only when it is missing, then shows its details.

1. Select Start, type PowerShell, right-click Windows PowerShell and select Run as administrator. Select Yes.
2. Paste this line and press Enter. It registers the plug-in if it is missing and then lists it:

   if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) {Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown}; Get-AppxPackage Microsoft.AAD.BrokerPlugin

3. Check that the output shows Name : Microsoft.AAD.BrokerPlugin and a PackageFullName.
4. Restart the PC and sign in to the Office app.

The plug-in package is installed for each user, so run this while you are signed in to Windows as the person who sees 58tm1. For the background of this component and a second plug-in for personal accounts, see our guide to error tag 7q6ch, a sister error of the same sign-in layer.

Fix 5. On terminal servers and virtual desktops: update FSLogix and check the profile (administrator)

30 minutesLow riskUsers sign in to Windows Server terminal servers or Azure Virtual Desktop with FSLogix profiles, and 58tm1 returns after each logon.

Most 58tm1 reports come from shared servers where FSLogix carries each user's profile, including the AAD Broker tokens, from session to session. Microsoft's forum staff tell administrators to update FSLogix and register the plug-in again on the server.

1. Download the current FSLogix release from the Microsoft Download Center and install it on every session host. Microsoft's moderator linked version 25.06 in August 2025.
2. Restart the session hosts.
3. Run the PowerShell line from Fix 4 on the server as administrator.
4. For each affected user, rename the folder from Fix 2 inside their profile, then let them log on again.
5. If 58tm1 still returns, review what your FSLogix profile roams for sign-in data, and whether Roam Identity is on or off for your setup.

The BornCity blog reported in September 2025 that FSLogix 25.09 fixed the Outlook 365 error 58tm1. We could not confirm this in Microsoft's FSLogix release notes, which name no 58tm1 fix, so treat it as a report. Administrators also report opposite results with Roam Identity: some say turning it off ended 58tm1, others that turning it on with hybrid join and single sign-on did.

Fix 6. Update Office, then repair it

15 to 40 minutesLow riskNothing above helped, or Office has not been updated for a long time.

An update brings the current sign-in code of Office and a repair replaces damaged program files. Microsoft's moderator lists both for 58tm1. Neither touches the stored sign-in data behind most cases, which is why this comes last.

1. Open Word and go to File > Account (Office Account in classic Outlook).
2. Under Product Information select Update Options > Update Now.
3. Wait for the message that updates were installed or that you are up to date, then restart the PC.
4. If 58tm1 is still there, run Quick Repair, and Online Repair if Quick Repair does not help.

Every screen of both repairs on Windows 11: How to repair Microsoft 365 or Office.

If 58tm1 is still there: what to check and what to send

When all fixes fail, stop changing things and narrow the problem down. Three tests tell you whether the fault is the account, your Windows profile or the whole PC.

• The test account in full: Create a new user account to test a problem. Sign in to Office there with the same work or personal address.
• For support, copy the details. Select the details link in the error window and note Error Code, Correlation Id and Timestamp, the app, when it started, and whether office.com works.
• For administrators: an administrator on Microsoft Q&A quoted Microsoft support, who traced a recurring 58tm1 in Outlook to a sync issue between Exchange Online Protection and Exchange Online and ran a sync for the user. If one mailbox keeps failing on every PC, ask Microsoft support about this.

How to keep 58tm1 from coming back

58tm1 returns when the sign-in data saved in your profile is damaged again or no longer matches the account. Most prevention is about keeping that data clean and current.

• Sign out of Office before a password or account change, not after it.
• Do not reinstall Office as the first answer to a sign-in error. The data behind 58tm1 lives in your profile, so clear it first with Fix 1 and Fix 2.
• Leave the Windows sign-in components alone. Tools that remove built-in packages or trim services can break the AAD Broker plug-in.
• On shared servers, keep FSLogix current and test each new release with Outlook and Teams sign-in before you roll it out.
• Keep Office and Windows updated. Windows 10 left support on 14 October 2025, so a Windows 10 PC no longer gets security fixes for this sign-in layer.

Frequently asked questions

What does error 58tm1 mean?

It means that a Microsoft 365 app on Windows could not complete your sign-in with the data it saved on the PC. Microsoft publishes no definition of the tag. Its forum staff link it to authentication, corrupted cached credentials and the Microsoft.AAD.BrokerPlugin component. The code that often comes with it, 2147942403, is the Windows error "The system cannot find the path specified". Clear the Office sign-in cache first with Fix 1.

How do I fix Outlook error 58tm1?

Sign out of Office, close Outlook and every other Office app, and empty the OneAuth and IdentityCache folders under %localappdata%\Microsoft. Restart and sign in to Outlook again. If the tag returns, rename your user's Microsoft.AAD.BrokerPlugin folder under %localappdata%\Packages (Fix 2). On a terminal server with FSLogix, the administrator should also update FSLogix (Fix 5). Your mail at outlook.office.com keeps working while you do this.

Why does Teams show 58tm1 when Teams on the web works?

Because the web version signs in through the browser, while the desktop app asks Windows for a token through the AAD Broker plug-in. When that saved token data is damaged, only the desktop app fails. An administrator on Microsoft Q&A saw exactly this and found that a Teams reinstall alone did not help. Clear the Office cache and the plug-in data with Fix 1 and Fix 2, then reconnect the work account with Fix 3.

What does the error code 2147942403 under 58tm1 mean?

In hexadecimal it is 0x80070003. The 8007 part means a Windows error is wrapped inside, and 3 is ERROR_PATH_NOT_FOUND, "The system cannot find the path specified". So Office looked for something in your profile, such as a token file or a plug-in folder, and did not find it. That is why clearing the cache and letting Windows rebuild it is the usual cure.

Is it safe to delete the Microsoft.AAD.BrokerPlugin folder?

Only the one in your own profile, under %localappdata%\Packages. It holds your tokens and Windows creates it again, though every work app asks you to sign in once more. Renaming it to .old is safer than deleting. Never delete the folder of the same name in C:\Windows\SystemApps: that is the Windows component itself. If it is damaged, register it again with Fix 4.

Does the regsvr32 Microsoft.AAD.BrokerPlugin.dll command fix 58tm1?

No. Some guides, including an older version of this page, suggest regsvr32 /u and regsvr32 on Microsoft.AAD.BrokerPlugin.dll. The AAD Broker plug-in is a Windows app package, not a COM DLL, so the command fails and changes nothing. The supported way is the PowerShell line in Fix 4, which registers the package from its Appxmanifest.xml file, as Microsoft's forum staff give it.

Why does 58tm1 keep coming back on our terminal server?

Because FSLogix saves each user's profile, with its sign-in tokens, into a container and loads it at every logon. A damaged token travels with the profile. Clearing it for one user is a temporary fix, as an administrator quoted by BornCity put it. Update FSLogix on all session hosts, register the plug-in again and review what the profile roams (Fix 5). BornCity reported that FSLogix 25.09 fixed the error; we could not confirm that in Microsoft's notes.

Is "Se ha producido un error. [58tm1]" or "erreur 58tm1" the same error?

Yes. Office translates the sentence and keeps the tag, so Spanish users see "Se ha producido un error. [58tm1]" and French users search for "erreur 58tm1". This page is in English, and the folders, commands and steps are the same in every language. Only the menu labels are translated, so look for the same positions on the screen.

Will reinstalling Office remove error 58tm1?

Usually not. The data that 58tm1 trips over lives in your Windows profile and in the AAD Broker plug-in, not in the Office program files. An administrator on Microsoft Q&A reinstalled Teams and still saw the error. Clear the stored sign-in data with Fix 1 to Fix 3 first. Update and repair Office once with Fix 6, and reinstall only if a repair fails.