How to fix Teams error code 2147942402 in Windows?

Error code 2147942402 is the decimal form of 0x80070002, the Windows error "The system cannot find the file specified". In Teams and Outlook it sits under Error Tag: 48v35 in a failed sign-in window; in Task Scheduler it reads Error Value: 2147942402 when a task cannot start. In Teams, sign out, quit, restart and sign in again first.

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

What error code 2147942402 means

Windows reports problems as result codes. Most programs print them in hexadecimal, but the Microsoft sign-in window and Task Scheduler's event text print them as a plain decimal number. Converted, 2147942402 becomes 0x80070002. The front half says that this is a failure carrying an ordinary Windows error; the last part, 2, is ERROR_FILE_NOT_FOUND: "The system cannot find the file specified."

So the number tells you what went wrong, not where. A Server Fault answer with over 150,000 views makes the same point for scheduled tasks: convert the number and you have "file not found", and the task is pointing at something that does not exist. The same reading holds for the Teams and Office window: a part of the sign-in went to open something stored on the PC and found nothing.

Code 2147942402 in Teams and Outlook: the 48v35 sign-in window

In Teams the number does not appear as a message of its own. A small Microsoft window opens where you would type your password, says Something went wrong. [48v35] in red, and the details below it end with the tag and the code. The same window, with the same two lines, is reported in classic Outlook, new Outlook, Word and Excel, because all of them ask the same Windows component for your account.

• Error Tag: 48v35: the step where the sign-in gave up. Some windows show [1001] in red and 48v35 only in the details.
• Error Code: 2147942402: the file not found result decoded above.
• Message: An unexpected error occurred.: in the copied text; it adds nothing.
• Copy info to clipboard: copies all lines. Keep them for your administrator before you try any fix.

Our full page on the tag, with the administrator's side for remote desktops, Azure Virtual Desktop, Citrix and FSLogix, is Teams error tag 48v35. The fixes below cover what a user can do on one PC.

What causes error 2147942402, ranked

Microsoft has not published a cause list for this number, because it is a generic Windows error. The order below is our reading of where the page's readers meet it and of the reports in the sources. It is not a statistic.

How to fix error code 2147942402 in Teams, Office and Task Scheduler

Fix 1 to Fix 4 are for the Teams and Office sign-in window. Fix 5 and Fix 6 are for Task Scheduler and scripts. Fix 7 and Fix 8 are for both, when nothing specific helped. Test after each fix.

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

5 minutesNo riskEveryone who sees the code in the Teams, Outlook or Office sign-in window.

A full sign-out makes the apps drop the stored account, and the next sign-in writes it again. Microsoft's workaround for a related Microsoft 365 licensing error is the same: sign out, close every app including Outlook, restart the app and sign back in.

1. Select Copy info to clipboard in the error window and paste the text into a note.
2. If Teams opens, select your profile picture at the top and select Sign out.
3. Open Word or Excel, go to File > Account and select Sign out. In classic Outlook it is File > Office Account.
4. Close every Microsoft 365 app, Outlook included.
5. Right-click the Teams icon in the corner of the taskbar and select Quit. Closing the window leaves Teams running.
6. Restart the PC. On a remote desktop, sign out of the Windows session instead of closing the remote window.
7. Start Teams, sign in with your work or school address, then sign in to one Office app.

Fix 2. Repair or reset the Teams app

5 minutesLow riskTeams alone shows the code, or Fix 1 helped only for a day.

New Teams keeps its settings and caches in one folder of your profile, and Windows can repair or empty it. Repair keeps the app's data; Reset deletes it, so Teams starts as on a new PC.

1. Quit Teams from the taskbar corner.
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. Select Terminate to stop any Teams process.
5. Select Repair and start Teams. If the error stays, come back and select Reset.

Every screen, with the Windows 10 path: How to repair or reset an app in Windows. If Advanced options is missing, quit Teams and delete the contents of %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams instead. The eight folders under %appdata%\Microsoft\Teams that the old version of this page listed belong to classic Teams.

Fix 3. Clear the shared Office sign-in data and saved credentials

10 minutesLow riskYour own PC, when Teams and Outlook both fail, or the code survived Fix 1 and Fix 2.

Teams and the Office apps share their accounts and tokens in two folders and in Credential Manager. When a piece of that store is missing, every app that reads it fails the same way. Deleting it makes Windows build it again at the next sign-in.

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

   %localappdata%\Microsoft

3. Delete the folders OneAuth and IdentityCache if they are there.
4. Select Start, type credential manager and open Credential Manager > Windows Credentials.
5. Remove every entry that begins with MicrosoftOffice16.
6. Restart the PC and sign in to Teams, then to Office.

Fix 4. Start Teams from the Start menu and replace old shortcuts

3 minutesNo riskTeams does not open at all from its taskbar or desktop icon, as in the question at the top of this page.

A shortcut that points to a program which is no longer there produces exactly this "file not found" result. Classic Teams has been replaced by new Teams, and pins or startup entries made for the old client can outlive it. This is our reading of the code; Microsoft has not documented it for Teams.

1. Select Start, type Teams and open Microsoft Teams from the results.
2. If it opens, right-click the old taskbar icon and select Unpin from taskbar. Delete any old Teams icon on the desktop.
3. Right-click Microsoft Teams in the Start results and select Pin to taskbar.
4. If the Start search shows no Teams, or two entries, note which ones and go to Fix 8 to install the current Teams.

Fix 5. Correct the program and arguments of the scheduled task

5 minutesLow riskTask Scheduler shows Error Value: 2147942402, Last Run Result 0x80070002, or a script returns this code.

Task Scheduler starts exactly the file named in Program/script. The accepted Server Fault answer shows the classic case: move was put there, but move is a command inside cmd, not a program file. Other answers there report arguments typed into the program box and a powershell.exe that was not found without its full path.

1. Press Win + R, type taskschd.msc and press Enter.
2. Find the task in Task Scheduler Library, right-click it and select Properties.
3. Open the Actions tab, select the action and select Edit.
4. In Program/script, leave only the full path of the program or script. Put quotes around a path that contains spaces.
5. Move everything else into Add arguments (optional).
6. For a built-in command such as move, copy or del, use cmd.exe as the program and /c plus the command as the argument.
7. For PowerShell scripts, use the full path of PowerShell as the program:

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

8. Select OK, right-click the task and select Run.

Fix 6. Stop the task from deleting itself before it runs

3 minutesLow riskA one-time task fails with event 101 and this code, or disappears after it was due.

A Server Fault answer describes a timing trap: when If the task is not scheduled to run again, delete it after is set and the trigger expires at the same moment it starts, the task can be deleted seconds before it fires. The start then fails with 2147942402, because the task's own file is gone.

1. Open the task's Properties and the Triggers tab, select the trigger and select Edit.
2. If Expire is ticked with the same date and time as the start, set it at least one minute later, or clear the tick.
3. On the Settings tab, clear If the task is not scheduled to run again, delete it after while you test.
4. Select OK and wait for the next run, or right-click the task and select Run.

This is one reporter's diagnosis, and it explains only one-time tasks. For a task that ran for days and then stopped, the History tab and the account the task runs as are the next places to look, as described after the fixes.

Fix 7. Test a second Windows account

15 minutesLow riskYour own PC, when Fix 1 to Fix 4 did not stop the sign-in error.

The sign-in data and the Teams folder live in your Windows profile. A new profile has none of the old files, so if Teams signs in there, the fault is in your old profile and not in Windows or the account.

1. Open Settings > Accounts > Other users and select Add account.
2. Select I don't have this person's sign-in information, then Add a user without a Microsoft account.
3. Give the account a name and password, sign out and sign in to it.
4. 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.

Fix 8. Repair Windows files, update and reinstall Teams

20 to 30 minutesLow riskNothing above helped, or Teams and Windows have not been updated for months.

When the missing file is part of Windows or of the Teams installation itself, only a repair or a fresh install puts it back. This is the generic last step, so it comes last.

1. Run the system file check and DISM: Run DISM and SFC to repair Windows system files.
2. Open Settings > Windows Update, select Check for updates, install and restart.
3. Uninstall Teams under Settings > Apps > Installed apps: Uninstall a program or app in Windows.
4. Install Teams again from Microsoft's Teams download page and sign in.

If 2147942402 is still there: where the real cause is written

The code says that something is missing, and the logs say what. Collect them before you ask anyone for help.

How to keep error 2147942402 from coming back

• Sign in to Teams on a PC that sat unused before the day you need it, so the stored sign-in is renewed while you are online.
• Do not copy AppData from an old PC or a backup into a new profile. The sign-in data under %localappdata%\Microsoft belongs to one device.
• Keep cleaning tools away from %localappdata%\Microsoft and from built-in app packages.
• Write scheduled tasks with full paths, quotes around paths with spaces, and arguments in their own box. Test the action with Run once before you rely on it.
• Let Teams and Windows update. Windows 10 left support on 14 October 2025, so a Windows 10 PC no longer gets fixes for the parts Teams depends on.

Frequently asked questions

What is error code 2147942402?

It is the Windows result 0x80070002 written as a decimal number. The 8 marks a failure, 007 says that it carries an ordinary Windows error, and 0002 is error 2, ERROR_FILE_NOT_FOUND: "The system cannot find the file specified." The number says what happened, not which file. In Teams and Office it appears under Error Tag 48v35 when the stored sign-in is incomplete. In Task Scheduler it appears when the program in a task's action cannot be found.

What does "Additional Data: Error Value: 2147942402" mean in Task Scheduler?

It means Task Scheduler could not find the file it was asked to start. The full event reads Task Scheduler failed to start instance, followed by the task and user names and this Error Value. Most often the Program/script box holds a built-in command such as move, a path with arguments typed into it, a path with spaces and no quotes, or a program such as powershell.exe without its full path. Fix 5 corrects each of these.

What does "Message: An unexpected error occurred. Tag: 48v35 Code: 2147942402" mean?

It is the text you get from Copy info to clipboard in the Microsoft sign-in window of Teams, Outlook or Office. The message line is generic. The tag marks the step where the sign-in stopped, and the code says a file was not found. In practice the sign-in data that Windows keeps for your account on this PC is missing or out of date. Sign out, quit, restart and sign in (Fix 1), then reset Teams (Fix 2).

I get Outlook error code 2147942402. Is that the same problem?

Yes. Outlook, Teams, Word and Excel ask the same Windows component for your account, so the same window with Error Tag 48v35 and Error Code 2147942402 can appear in each of them, sometimes on the same morning. Outlook on the web does not use that component, so if webmail works, your account is fine and the fault is on the PC. Fix 1 and Fix 3 apply to Outlook as they do to Teams.

What is return code 2147942402?

A tool that starts another program, such as Task Scheduler, a deployment tool or an installer wrapper, reports this number when the program, script or file it was given does not exist at that path. Check the exact path in the tool's command line, put quotes around paths with spaces, and confirm the file is there on the computer where it runs, not only on yours. The same number can appear as -2147024894 when a tool prints it as a signed number.

Is -2147024894 the same as 2147942402?

Yes. Both are 0x80070002. A result code is 32 bits long, and some programs print it as an unsigned number, 2147942402, while others print it as a signed one, -2147024894. PowerShell, .NET and many installer logs use the signed form. Both mean Windows error 2, file not found, and the fixes on this page apply to both.

Will running Teams as administrator fix error 2147942402?

No. Running as administrator helps with "access denied", which is Windows error 5 (0x80070005, 2147942405). Error 2 means the file is missing, and more rights do not create it. Running Teams elevated also starts it under a different security context than your normal sign-in, which can cause new sign-in problems. Use Fix 1 to Fix 3 instead.

My scheduled task worked for days and then failed with 2147942402. Why?

Something the task points to changed: a program was updated to a new folder, a drive letter or network share was not available when the task ran, or the task deleted itself after an expiry date. Check the action path with the Win + R test in Fix 5 and the trigger with Fix 6. Older reports on Microsoft's forum from Windows Vista and 7 tie the error to Task Scheduler losing the stored password after a restart; retype the password in the task's properties if it runs whether the user is signed in or not.