How to fix Teams error tag 48v35 in Windows?

The 48v35 tag marks a failed sign-in in Microsoft Teams, Outlook and the other Microsoft 365 apps on Windows: a small Microsoft window shows Something went wrong. [48v35] where the password box should be. In the reports the Code under the tag is 2147942402, the Windows error for a file that cannot be found. Sign out of Teams and Office, quit them, restart the PC and sign in again.

Facts checked on 14 October 2026. Steps written for the new Microsoft Teams and Microsoft 365 apps on Windows 11 (25H2 and 26H2) and Windows 10 22H2, read against Microsoft's documentation.

What Something went wrong [48v35] means in Teams

You start Teams, or Teams asks for your account in the middle of the day, and a small window with the Microsoft logo opens. Its title is Enter Password to Microsoft Teams, but there is no password box. It says Error and, in red, Something went wrong. [48v35]. The only button is Close.

The window is drawn by the Windows sign-in component that Teams calls, not by Teams itself. Teams, Outlook and the other Microsoft 365 apps ask the same Windows component for your account, so the same window and the same tag can appear in each of them. The characters in brackets mark the step where that component stopped. There is no public Microsoft reference for such tags, and our search of Microsoft Learn and Microsoft Support found nothing that explains 48v35.

Code 2147942402 under tag 48v35: the file that Windows cannot find

Every report of 48v35 that quotes the Code line gives the same number: 2147942402. We saw it with Teams for Education, with classic Outlook, with Word during activation and in the window pictured above. It is a Windows result code printed as a decimal number. Converted to hexadecimal it reads 0x80070002, and that form can be looked up.

So the tag is not a password problem and not a server outage. A part of the sign-in went to open something stored on this computer and it was not there. Microsoft does not say which file is meant, and we could not confirm it either. The reports point in one direction, though: profiles that are copied between machines, a reformatted PC, a PC that was offline for weeks.

48v35 in Teams, Outlook and Office: where and when it shows up

Microsoft's Teams documentation says that Windows keeps user accounts in Web Account Manager, and that this is what gives single sign-on to Teams and other Microsoft applications. The Microsoft 365 apps use the same manager through its plug-ins. One broken store therefore hits several apps, often on the same morning.

Teams also has error numbers of its own. They are printed as a status code in the bottom left corner of the Teams sign-in screen, they start with 0xCAA and Microsoft explains them. If you see one of these, follow that code first.

What causes error 48v35, ranked by how often it is reported

Microsoft has not named a cause for this tag. The order below is our reading of two things: where users and administrators meet the tag, and what Microsoft documents about the files behind the sign-in. It is not a statistic.

Your own PC, a managed laptop or a remote desktop: who can fix it

Before you delete anything, find out which of three situations you are in. On your own PC all fixes are yours to run. On a laptop that belongs to an employer or a school, some of them remove the organisation's setup. On a remote or virtual desktop the stored sign-in is rebuilt or lost by the server at every logon, so a user's repair lasts until the next session at best.

Run this in Command Prompt, opened the normal way and not as administrator. Microsoft notes that the command must run in the user's own context.

dsregcmd /status

How to fix error 48v35 in Teams and Outlook on Windows

The fixes go from the one that users report most to the ones that change more. Fix 1 and Fix 2 are safe on every computer. Fix 3 to Fix 8 change more, so keep them for your own PC or leave them to an administrator. Test after every fix by starting Teams. Success looks the same each time: the red line is gone and Teams asks for your password or for an approval on your phone.

Fix 1. Sign out of Teams and Office, quit Teams and restart Windows

5 minutesNo riskEveryone, first. It is the fix that users with this tag report as working.

A full sign-out makes the apps drop the stored account, and the next sign-in writes it again from scratch. An IT professional who met [1001] with tag 48v35 on a PC that had been offline for more than a month describes exactly this as the cure. Microsoft's page for [1001] adds that a reboot often helps.

1. If Teams still opens, select your profile picture at the top of the Teams window and select Sign out.
2. Open Word, Excel or classic Outlook. Go to File > Account (Office Account in Outlook) and select Sign out.
3. Close every Microsoft 365 app.
4. Right-click the Teams icon in the corner of the taskbar and select Quit. Closing the window is not enough: Teams keeps running there.
5. Restart the PC. On a remote desktop, sign out of the Windows session. Closing the remote window alone leaves the session running.
6. Start Teams and sign in with your work or school address.
7. Open the Office app and sign in there too.

Fix 2. Reset the Teams app, or delete its cache folder

5 minutesLow riskTeams alone shows the tag, or Fix 1 helped only for a short time. Safe on a managed laptop too.

New Teams keeps its settings, configuration and caches in one folder of your profile. Microsoft lists two ways to empty it: the Reset button of Windows and a manual deletion. A moderator on Microsoft's forum gave a Teams for Education user with tag 48v35 and code 2147942402 this as the step after quitting Teams.

1. Right-click the Teams icon in the taskbar corner and select Quit.
2. Open Settings > Apps > Installed apps and type Microsoft Teams in the search box.
3. Select the three dots next to Microsoft Teams and select Advanced options.
4. Scroll to the Reset section and select Reset.
5. Start Teams and sign in.

The page for both Windows versions, with the Windows 10 path: How to repair or reset an app in Windows. If Advanced options is missing, or the reset changes nothing, empty the folder by hand. This is Microsoft's second method.

1. Quit Teams from the taskbar corner again.
2. Press Win + R, paste this path and select OK:

   %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams

3. Press Ctrl + A and delete all files and folders in it.
4. Start Teams. The first start takes longer than usual, because the cache is rebuilt.

The old guide on this page listed eight folders under %appdata%\Microsoft\Teams. That is the folder of classic Teams. If a PC still runs the classic client, Microsoft's instruction is simpler: quit Teams and delete everything inside %appdata%\Microsoft\Teams.

Fix 3. Delete the OneAuth and IdentityCache folders

5 minutesLow riskYour own PC. Teams and Outlook both fail, or the tag came back after Fix 1 and Fix 2.

These two folders hold the accounts and tokens that the Microsoft 365 apps share on one PC. Microsoft lists both as identity data that must never be copied from another computer. The most supported answer in Microsoft's forum thread about 48v35, and the answers given in three other threads, is to delete them and restart.

1. Close Outlook, Word, Excel and OneDrive, and quit Teams from the taskbar corner.
2. Press Win + R, paste this path and press Enter:

   %localappdata%\Microsoft

3. Look for the folders OneAuth and IdentityCache.
4. Delete both. If Windows says a file is in use, an Office app is still running: restart the PC and delete them before you open anything.
5. Restart the PC.
6. Start Teams and sign in, then the Office apps.

Be ready for an honest limit. Several administrators confirm that this ends 48v35, and a forum advisor adds that the result can be temporary in some environments. One Outlook user who cleared the folders and re-registered the plug-in was signed out and then saw another tag, 5fcl8 with code 1067. If a new tag replaces the old one, go straight to Fix 4.

Fix 4. Remove the saved Office credentials and reconnect the work account

10 minutesLow riskYour own PC with a work, school or education account, above all after Windows was reinstalled or the account moved to another organisation.

Outside the app folders Windows remembers a work account in two more places: Credential Manager and the list under Access work or school. Microsoft's activation article clears both. On remote desktop servers an administrator reports that clearing the credentials is the only thing that works for his users so far.

1. Close the Office apps and quit Teams.
2. Select Start, type credential manager and open Credential Manager.
3. Select Windows Credentials.
4. For every entry that begins with MicrosoftOffice16, select the arrow next to it and select Remove.
5. Open Settings > Accounts > Access work or school.
6. If the account you use for Teams is listed and it is not the account you sign in to Windows with, select it and select Disconnect.
7. Restart the PC.
8. Start Teams and sign in with the work or school account.

During the new sign-in Windows may offer to remember the account for all apps on the device. Saying yes adds the account to Access work or school again, now with fresh data. That is fine on your own PC.

Fix 5. Register the Windows account plug-ins again

10 minutesLow riskThe sign-in window is blank, hangs or closes at once, or the Application log shows AppModel-State errors that name Microsoft.AAD.BrokerPlugin.

Work and school accounts are signed in by the package Microsoft.AAD.BrokerPlugin, personal accounts by Microsoft.Windows.CloudExperienceHost. Both are installed per user. Microsoft's page for [1001] gives two PowerShell commands that register them again, and its bulletin for failed single sign-on on Azure Virtual Desktop uses the same command as a logon script.

1. Restart the PC first. Microsoft notes that a reboot alone often helps.
2. Press Win + R, type powershell and press Enter.
3. Check that both packages exist. Each line should print the details of one package:

   Get-AppxPackage Microsoft.AAD.BrokerPlugin
   Get-AppxPackage Microsoft.Windows.CloudExperienceHost

4. Register the plug-in for work and school accounts:

   Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

5. Register the plug-in for personal Microsoft accounts:

   Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

6. Test them in Command Prompt. A Work or school account window and a Microsoft account window should open:

   explorer.exe shell:appsFolder\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy!App
   explorer.exe shell:appsFolder\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy!App

7. Close the test windows, start Teams and sign in.

A short progress bar and no red text mean that a command worked. Microsoft's advice is to watch the PC for 48 hours afterwards. If the plug-ins break again within that time, something on the PC keeps damaging them, and Fix 6 is the place to look.

Fix 6. Test without VPN, proxy and third-party security software

10 minutesLow riskThe tag began after an antivirus, firewall or VPN was installed or updated, or it appears on one network and not on another.

Microsoft names security software that affects the account plug-in as the first scenario behind [1001], and says such software can block the plug-ins or remove them as a side effect. Its Teams page adds that antivirus and data loss prevention tools can make the Teams app itself fail. One test without them shows whether they are involved.

1. Open https://teams.microsoft.com in a browser and sign in. If that fails too, the fault is the network or the account, not the Teams app.
2. Disconnect the VPN, or connect the PC to another network such as a phone hotspot. Try the Teams sign-in.
3. Open Settings > Network & internet > Proxy. Under Manual proxy setup, next to Use a proxy server, select Set up to open the Edit proxy server dialog.
4. If a proxy is on and you did not set it yourself, switch it Off for the test, select Save and try the sign-in.
5. Pause the antivirus for one attempt. For Microsoft Defender: Turn off Microsoft Defender protection for a moment.
6. Switch the protection, the proxy and the VPN back on after the test, whatever the result.

If the sign-in works while a program is paused, keep the program and change its settings. Ask its maker or your administrator to exclude what Microsoft lists for Teams and for the Windows sign-in.

• Teams processes: ms-teams.exe, ms-teamsupdate.exe, msteams_autostarter.exe and msedgewebview2.exe
• Sign-in packages: Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy and Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy
• Sign-in folders: %localappdata%\Microsoft\TokenBroker, %localappdata%\Microsoft\OneAuth and %localappdata%\Microsoft\IdentityCache
• Addresses a firewall or proxy must let through, among others: login.microsoftonline.com, login.microsoft.com, login.windows.net and aadcdn.msauth.net

Fix 7. Sign in from a second Windows account

15 minutesLow riskYour own PC, when the fixes above did not help. It shows whether the damage is in your profile or in Windows itself.

The plug-ins and caches behind the sign-in are stored per Windows user. A student who got tag 48v35 with code 2147942402 after reformatting the PC found that the same Office signed in without the error from another Windows account. A new profile has none of the old sign-in files, so nothing can be missing from it.

1. Open Settings > Accounts > Other users.
2. Next to Add other user select Add account.
3. Select I don't have this person's sign-in information, then Add a user without a Microsoft account.
4. Type a name and a password for the test account and finish.
5. Sign out of Windows and sign in to the new account. The first sign-in takes a few minutes.
6. Start Teams there and sign in with your work or school address.

Every screen, and the Windows 10 path: Create a new user account to test a problem. The result of the test decides what comes next.

Fix 8. Update Teams and Windows, then reinstall Teams

15 to 30 minutesLow riskNothing above helped, Teams has not been updated for months, or the PC still runs Windows 10 with updates missing.

Microsoft's own order for Teams sign-in errors is to check that the client has the latest update before anything else, and to reinstall Teams as the last manual step. The one bug that Microsoft confirmed for failed single sign-on in Outlook and Teams was repaired by a Windows update.

1. In Teams, select the Settings and more menu next to your profile picture and select Check for updates. If Teams does not open far enough to show the menu, go to step 3.
2. If a notice at the top of the window offers an update, select Update, then Update and restart Teams.
3. Open Settings > Windows Update and select Check for updates. Install what is offered and restart.
4. Try the sign-in.

If the tag is still there, reinstall Teams. Remove it under Settings > Apps > Installed apps with the three dots and Uninstall: Uninstall a program or app in Windows. Then get the installer from Microsoft's Teams download page and sign in. Microsoft's instruction for classic Teams adds one step in between: delete the Teams folder under %appdata%\Microsoft.

If 48v35 is still there: the logs that show the real cause

The error window says that something is missing and not what. Windows and Teams write more than that. Three places are worth a look, and all three produce something you can attach to a support request.

• What to send to the administrator: the text behind Copy info to clipboard, the app and its version, the time it started, whether teams.microsoft.com works, and whether the computer is yours, a managed laptop or a remote desktop.
• For a Microsoft support ticket: Microsoft asks tenant admins to open the ticket in the Microsoft 365 admin center and to attach MSOAID logs. The tool records Office and Windows sign-in logs while you repeat the error: Use MSOAID for authentication issues.
• On a virtual desktop: Teams limits the size of its logs there. Microsoft says to turn on extended logging in the Teams privacy settings before you repeat the error.

For administrators: 48v35 on RDS, Azure Virtual Desktop, Citrix and FSLogix

Most long threads about this tag are written by administrators of multi-user servers, and their users share one pattern: random users, every few days, cured for a while by signing out. A forum advisor wrote in June 2026 that there is no permanent fix that all sides accept yet. What Microsoft does document is below, cheapest check first.

1. Run the Teams Sign-in diagnostic in the Microsoft 365 admin center with the user's address. Microsoft's article Resolve sign-in errors in Teams links to it and to the Teams Sign in test of the Remote Connectivity Analyzer.
2. On the session host, open the Application log and filter for source Microsoft-Windows-AppModel-State, Event ID 10. The text "Failure to load the application settings for package Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy" with code -2147024893 is the signature in Microsoft's bulletin KB5048864.
3. Compare your profile solution with Microsoft's list of identity data that must never leave a device. The list is in the next block.
4. With FSLogix, check RoamIdentity. The default and recommended value is 0. Microsoft says not to enable it on devices that are Microsoft Entra joined or managed with Intune.
5. Update FSLogix. Its known issues page lists a bug, marked fixed, in which identity registry locations that must not roam were not removed at sign-out. It affects version 25.09 and earlier.
6. Check the platform against Microsoft's requirements for new Teams on virtual desktops, including the FSLogix and Citrix Profile Management versions named there.

• Folders that must not roam: %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy, %localappdata%\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy, %localappdata%\Packages\<any app package>\AC\TokenBroker, %localappdata%\Microsoft\TokenBroker, %localappdata%\Microsoft\OneAuth, %localappdata%\Microsoft\IdentityCache
• Registry keys that must not roam: HKEY_CURRENT_USER\SOFTWARE\Microsoft\IdentityCRL, HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\AAD, HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WorkplaceJoin and HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\TokenBroker
• Also not supported: roaming the work account's device certificate, issued by MS-Organization-Access
• What must roam for new Teams: the folders under AppData\Local\Packages\MSTeams_8wekyb3d8bbwe, as real directories. Folder Redirection and Roaming User Profiles alone cannot do that.

How to stop 48v35 from coming back

On a single PC the tag is rare once the sign-in stores have been rebuilt. It comes back when files go missing from them again, and a few habits prevent that.

• Start a PC that sat unused before the day you need it. Sign in to Windows and to Teams while online, so that the stored sign-in is renewed. The one detailed home-office report of this tag came from a PC that had been offline for more than a month.
• Do not copy AppData from an old PC or a backup into a new profile. Microsoft's rule for administrators applies at home too: the sign-in folders under %localappdata% must never come from another device. Copy documents, not AppData.
• Keep cleaning tools away from the sign-in folders. A tool that empties %localappdata%\Microsoft or removes built-in app packages can take the account plug-ins with it.
• Give security software its exclusions. If Fix 6 named a blocker, the exclusions listed there are the lasting answer, not a paused antivirus.
• Let Teams and Windows update. Teams updates itself when the app is idle. Windows 10 left support on 14 October 2025, and the one confirmed bug behind failed single sign-on was a Windows 10 bug.
• On a remote desktop, sign out at the end of the day. FSLogix removes the data that must not roam when the user signs out, not when a session is merely disconnected. This is our advice from how profile containers work, not a Microsoft statement about this tag.

Frequently asked questions

What does error tag 48v35 mean?

It means that a Microsoft 365 app on Windows, most often Teams or Outlook, could not finish signing you in. The tag only marks the step where the Windows sign-in component stopped, and Microsoft publishes no definition of it. The useful line is the Code under it. In the reports it is 2147942402, the Windows error "The system cannot find the file specified". In practice the stored sign-in on that computer is missing or incomplete. Signing out, quitting Teams, restarting and signing in again rebuilds it.

What is Code 2147942402 under tag 48v35?

It is a Windows result code written as a decimal number. In hexadecimal it is 0x80070002. The 8 marks a failure, 007 is the facility that Microsoft reserves for ordinary Windows errors, and 0002 is system error 2, ERROR_FILE_NOT_FOUND. Its text is "The system cannot find the file specified". Microsoft's bulletin about failed single sign-on on Azure Virtual Desktop names the neighbouring code -2147024893, which is 0x80070003, path not found. Microsoft does not say which file is missing in the 48v35 case, and we could not confirm it.

Why do I get 48v35 in Outlook when Teams or webmail still works?

Because each app asks Windows for its own token, and one request can fail while another succeeds. Users report the tag in classic Outlook that keeps asking for the account, in new Outlook when a message is opened, and in Word and Excel during activation. Webmail runs in the browser and never touches the sign-in files that Windows stores for desktop apps. Working webmail proves that the account itself is in order, and the fixes on this page apply to Outlook as they do to Teams.

Why does 48v35 keep coming back on a remote desktop, Citrix or Azure Virtual Desktop?

Because on those systems your profile is stored away at sign-out and brought back at the next logon, often on another server. Microsoft states that the sign-in folders and registry keys must never leave a device, and FSLogix deletes them from the profile at sign-out by default. When a profile tool handles only part of that data, the sign-in finds pieces missing. Signing out and in helps for a while. The lasting change is in the profile configuration, which only the administrator can make.

Is error 1001 the same as 48v35?

They often arrive together, but they are two labels. Something went wrong [1001] is the message Microsoft documents: a sign-in failure in the Microsoft 365 desktop apps, caused in its two named scenarios by security software or by roamed profile data. Tag 48v35 can appear in the details under a 1001 message, as in the question at the top of this page, or in the red line itself. An IT professional saw 1001 on one PC with tag 48v35 at some times and tag 58tm1 at others. The same fixes apply.

Will reinstalling Teams or Microsoft 365 fix 48v35?

Rarely. One Outlook user with this tag removed Microsoft 365 completely, installed it again and had the same error. The reason is where the data lives: the stored sign-in is in your Windows profile, in Credential Manager and in the Windows account plug-ins, and an uninstall leaves all of that in place. A reset of the Teams app is different, because it empties the Teams folder in your profile. Use the reset in Fix 2 and the cleanups in Fix 3 and Fix 4 before any reinstall.

Do the registry values DisableAADWAM or EnableADAL from forum threads get rid of 48v35?

Do not use them. DisableAADWAM, DisableADALatopWAMOverride and EnableADAL switch the Microsoft 365 apps back to an older sign-in method. Microsoft has a whole article against this: it calls the result an unsupported legacy configuration and warns of side effects for the environment. Newer security features exist only in Web Account Manager, and Teams relies on that same manager for single sign-on. One administrator in a 48v35 thread still runs these values on a Citrix farm, which shows how persistent the advice is. Repairing the manager with Fix 5 is the supported way.

Is "Ocorreu um erro. [48v35]", "Se ha producido un error. [48v35]" or "Nous avons rencontré un problème. [48v35]" the same error?

Yes. Only the sentence is translated and the tag is left as it is, so Portuguese, Spanish, French, German and Korean users all see 48v35 after their own wording. The German window says "Da ist etwas schiefgelaufen". The detail lines stay in English in every language, including "An unexpected error occurred." and the Code. Follow the fixes above in any language: folder paths, commands and the code are identical, and only menu and button names appear in your language.