How to fix Microsoft Teams error "We've run into an issue" in Windows?

We've run into an issue is the screen the new Microsoft Teams shows when its window cannot load, and it hides the reason. Most often a stuck Teams process, damaged app data, a missing WebView2 Runtime on Windows 10 or a blocked connection is behind it. Quit Teams completely and start it again (Fix 1), then reset the app (Fix 2).

Facts checked on 15 October 2026. Steps written for the new Microsoft Teams (MSTeams app package) for work, school and home on Windows 11 (25H2 and 26H2) and Windows 10 22H2, read against Microsoft's documentation.

What "We've run into an issue" means in Microsoft Teams

You start Teams, the logo appears, and instead of your chats you get a grey screen with a drawing of a person and one line: We've run into an issue. On some PCs the line reads We're sorry and we've run into an issue, joined by a long dash, with a Restart button and the hint "If that doesn't work, try signing out and back in."

Microsoft Q&A threads quote a second form of the same screen. We've run into an issue is followed by "Check your internet connection, and then try restarting Teams." Both mean that the Teams window started but could not load the page it shows you. The app does not say why, which is why people search every spelling.

What causes the Teams "We've run into an issue" error, ranked

Microsoft names only one cause in writing. The rest of the order below is our reading of Microsoft's articles and of the cases Microsoft staff answer on Microsoft Q&A. It is not a statistic.

First test: does Teams work in the browser?

This one-minute test tells you which half of the page you need. Microsoft staff suggest it in the Q&A answers to this error.

1. Open Microsoft Edge or Chrome on the same PC.
2. For a work or school account go to https://teams.microsoft.com. For a personal account go to https://teams.live.com.
3. Sign in with the same account that shows the error in the app.
4. Note the result: your chats open, or you get an error here too.

• Teams on the web works: your account and Microsoft's service are fine. The problem is the desktop app on this PC. Start with Fix 1, Fix 2 and Fix 3.
• Teams on the web fails too: look at the connection first (Fix 5). An administrator can check Microsoft 365 Service health in the admin center for an incident. If colleagues see the same, wait for Microsoft.

How to fix "We've run into an issue" in Microsoft Teams

Go in order and start Teams after each fix. Fix 1 to Fix 3 repair the app on this PC, Fix 4 to Fix 6 deal with Windows, the network and sign-in, Fix 7 and Fix 8 are the heavier steps. Success looks the same every time: Teams opens your chats or its sign-in window.

Fix 1. Quit Teams completely and start it again

2 minutesNo riskEveryone, first. Above all when the Restart button brings the same screen back.

Closing the window with X leaves Teams running in the background, and the Restart button only reloads the window. A full quit ends every Teams process, so the next start loads everything from scratch.

1. Right-click the Teams icon in the taskbar corner, next to the clock, and select Quit.
2. Press Ctrl + Shift + Esc to open Task Manager.
3. Under Processes, select every Microsoft Teams entry that is left and select End task.
4. Wait 10 seconds, then start Microsoft Teams from the Start menu.
5. If the screen comes back, select signing out in the hint under the button, sign in again and restart Teams once more.

If Teams still shows the screen after a full quit, restart the PC once. A pending update or a half-closed network session is cleared that way too.

Fix 2. Reset the Teams app or delete its cache

5 minutesLow riskTeams on the web works for the same account, but the desktop app keeps showing the screen.

New Teams keeps its local data in the package folder MSTeams_8wekyb3d8bbwe. When that data is damaged the window cannot load. Microsoft lists a reset as Method 1 to clear the cache of new Teams; Teams builds fresh files on the next start.

1. Quit Teams as in Fix 1.
2. Open Settings > Apps > Installed apps on Windows 11, or Settings > Apps > Apps & features on Windows 10.
3. Search for Microsoft Teams, select the three dots next to it and select Advanced options.
4. Under Reset, select Reset and confirm.
5. Start Teams and sign in. The first start takes longer than usual, because the cache is rebuilt.

Microsoft's Method 2 does the same by hand. Quit Teams, press Win + R, paste this path, press Enter and delete everything in the folder:

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

Fix 3. Install the WebView2 Runtime (Windows 10)

5 minutesNo riskWindows 10 PCs, above all right after the new Teams was installed.

New Teams draws its window with Microsoft Edge WebView2. Microsoft's article on new Teams install problems says Windows 10 users get We've run into an issue when it is missing, and that installing the WebView2 Runtime fixes it.

1. Quit Teams as in Fix 1.
2. Open Microsoft's WebView2 page: https://developer.microsoft.com/microsoft-edge/webview2/.
3. In the download section, under Evergreen Bootstrapper, select Download.
4. Run the downloaded file and wait until it finishes.
5. Start Teams again.

Microsoft's article names Windows 10 only. The same installer runs on Windows 11, and it does no harm there, but we could not confirm that it helps on Windows 11.

Fix 4. Install pending Windows updates and restart

10 to 30 minutesNo riskWindows Update shows waiting updates, or the PC has not restarted for a long time.

Microsoft asks for all pending Windows updates before new Teams is installed. In one Q&A case the screen went away after the latest Windows updates were installed, as Microsoft staff summed up.

1. Open Settings > Windows Update on Windows 11, or Settings > Update & Security > Windows Update on Windows 10.
2. Select Check for updates and install everything offered.
3. Restart the PC when Windows asks, even if Teams is not in the list.
4. Start Teams again.

Windows 10 left support on 14 October 2025, so it gets security updates only with Extended Security Updates. Install what it still offers.

Fix 5. Turn off the VPN and proxy for one test

5 minutesLow riskThe screen says "Check your internet connection", or the PC uses a VPN, a proxy or a filtering app.

Teams needs to reach several Microsoft addresses. A VPN, a proxy or a network filter can block some of them while web pages still load. Microsoft staff suggest turning the VPN off and on again for this error.

1. Disconnect your VPN app, or open Settings > Network & internet > VPN and disconnect the connection there.
2. Open Settings > Network & internet > Proxy.
3. Under Manual proxy setup, select Edit next to Use a proxy server and set it to Off, then Save. Leave the automatic settings to your IT on a work PC.
4. Start Teams again.

If Teams works without the VPN, turn it back on and ask the VPN provider or your IT to allow Microsoft Teams. Do not leave a required work VPN off.

Fix 6. Remove the saved Teams sign-in entries

5 minutesLow riskThe error began after a password change, a new account in Teams, or a switch between work and personal accounts.

Windows keeps Teams sign-in tokens in Credential Manager. An outdated entry can make Teams try an old sign-in on every start. Removing it makes Teams ask you to sign in again.

1. Quit Teams as in Fix 1.
2. Search for Credential Manager in the Start menu and open it.
3. Select Windows Credentials.
4. Under Generic Credentials, expand each entry that has teams or msteams in its name and select Remove.
5. Start Teams and sign in again with your account and password.

The exact entry names differ by Teams version and account type, and Microsoft does not list them. Remove only entries that clearly belong to Teams.

Fix 7. Uninstall Teams and install a fresh copy

10 to 15 minutesLow riskReset did not help, and Teams on the web works for the same account.

A reinstall replaces the program files that a reset leaves in place. The new installer from Microsoft also brings the current version of Teams.

1. Uninstall from the Start menu. Select Start > All apps and find the app. Right-click it (or press and hold) and select Uninstall.
2. Or uninstall in Settings. Select Start > Settings > Apps > Installed apps. Find the app, select More (the three dots) > Uninstall, and confirm.
3. Or uninstall from Control Panel. Some programs can only be removed here. Type Control Panel in the search box on the taskbar and open it, then select Programs > Programs and Features. Right-click the program and select Uninstall or Uninstall/Change, then follow the program's own uninstaller.

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Uninstall a program or app in Windows

1. Remove Microsoft Teams from the list of installed apps, as above. Remove Microsoft Teams classic too if it is still listed.
2. Restart the PC.
3. Download a new installer from Microsoft: https://www.microsoft.com/microsoft-teams/download-app.
4. Run it once and sign in when Teams opens.

Fix 8. Reset the Windows network settings

10 minutesRead the warningLast. Teams fails on this PC only, on every network, and the earlier fixes did not help.

A network reset removes and reinstalls the network adapters and returns their settings to default. It clears a damaged network setup that blocks Teams but not ordinary web pages.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Flush the DNS cache. Type the command below and press Enter. Windows forgets the website addresses it looked up earlier and asks for them again.

   ipconfig /flushdns

3. Reset Winsock. Type the command below and press Enter. It returns the Windows sockets catalog to its default state.

   netsh winsock reset

4. Reset TCP/IP. Type the command below and press Enter. If you entered an IP address or DNS server by hand, note it first: you may need to enter it again.

   netsh int ip reset

5. Get a new IP address. Run these two commands one after the other. The connection drops for a moment between them.

   ipconfig /release
   ipconfig /renew

6. Restart the PC. Restart Windows so the Winsock and TCP/IP resets take effect, then test the connection. If it still does not work, continue with the network reset below.
7. Open Network reset. Open Settings > Network & internet > Advanced network settings and select Network reset.
8. Reset now. Select Reset now, then Yes to confirm. Windows removes and reinstalls all network adapters and restarts the PC.
9. Reconnect. After the restart, connect to your Wi-Fi network again (you will need its password) and reinstall or reconfigure VPN software if it stopped working.

These steps were written for Windows 11 24H2 and later. The full page with the other versions and what each result means: Reset the network and flush DNS

If Teams still says "We've run into an issue"

Stop changing the PC and use Teams on the web meanwhile. Your chats, files and meetings are the same there. Then hand the problem to the people who can see the server side.

• Note the exact wording of the screen and the time it appeared.
• Note your Windows version from winver and the Teams version from Settings and more > About in Teams on the web or in the app, once it opens.
• Say which fixes on this page you tried and what each one changed.
• Ask support how to collect the Teams diagnostic logs for your version. We could not confirm the log location of new Teams in the Microsoft articles we read today.

How to keep the error from coming back

• Quit Teams from the taskbar corner instead of only closing its window when it starts to act up.
• Install Windows updates and restart when Windows asks. Microsoft wants pending updates in place for new Teams.
• Keep Teams current with Settings and more > Check for updates.
• On Windows 10, keep the WebView2 Runtime installed. Do not remove Microsoft Edge WebView2 Runtime from the app list.
• Do not clear the Teams cache for missing chats or messages. Microsoft says it does not fix them and deletes the logs support needs.

Frequently asked questions

What does "We've run into an issue" mean in Microsoft Teams?

It means the Teams desktop window started but could not load what it should show, so Teams shows a general error instead. It is not an account ban and it does not delete chats. The usual reasons are a Teams process that did not close, damaged local app data, a missing WebView2 Runtime on Windows 10, or a VPN or proxy that blocks Teams. Quit Teams fully and start it again first (Fix 1), then reset the app (Fix 2).

Why does "try restarting Teams" not help?

The Restart button and closing the window with X leave Teams running in the background. Teams then reloads the same broken window. Right-click the Teams icon next to the clock and select Quit, end any Microsoft Teams entry left in Task Manager, and start Teams from the Start menu. If the screen also says "Check your internet connection", test without your VPN or proxy (Fix 5).

How do I fix "We have run into an issue" in Teams on Windows 11?

On Windows 11 go in this order. Quit Teams fully and start it again, then reset the app in Settings > Apps > Installed apps > Microsoft Teams > Advanced options > Reset. Next, install pending Windows updates and test without VPN or proxy. Microsoft's WebView2 fix is documented for Windows 10. If Teams on the web works but the app does not, reinstall Teams with a fresh installer from Microsoft (Fix 7).

Will resetting Teams delete my chats and files?

No. Chats, channel messages, files and meetings are stored in your Microsoft account, not on the PC. A reset deletes the local app data of Teams, which Microsoft says includes your personal settings in the app. You sign in again afterwards, and the first start takes longer because Teams builds its cache again. Microsoft warns not to clear the cache for missing messages, because it does not fix them.

Is "We ran into a problem" in Teams the same error?

It is a close relative. "We ran into a problem", "Oops, something went wrong" and "Teams is currently experiencing an error" are other general Teams screens that also hide the cause. The same order of fixes is a fair start: quit and restart, test Teams on the web, reset the app, check the VPN. If the screen shows an error code, search for that code, because codes point to a specific cause.

Is Microsoft Teams down right now?

This screen alone does not tell you. Open Teams on the web: if it fails there too and colleagues report the same, a service problem is likely. A Microsoft 365 administrator can check Service health in the Microsoft 365 admin center, as Microsoft staff advise. Home users without an admin can only wait and try again later. If Teams on the web works, the service is up and the problem is the app on your PC.

Do I need WebView2 for Microsoft Teams?

Yes. New Teams uses Microsoft Edge WebView2 to draw its window. Microsoft documents that Windows 10 users get We've run into an issue when they install the new Teams without the WebView2 Runtime, and that installing the runtime and restarting Teams fixes it. Download the Evergreen Bootstrapper from Microsoft's WebView2 page and run it (Fix 3). Do not uninstall Microsoft Edge WebView2 Runtime afterwards, because other apps use it too.

Does compatibility mode fix the Teams error?

We do not recommend it. Older guides suggest running Teams in compatibility mode for an older Windows, but new Teams is a Windows app package for Windows 10 and Windows 11. None of the Microsoft articles we read lists compatibility mode as a fix for this screen. Reset the app (Fix 2) or reinstall it (Fix 7) instead.

Can I keep working while Teams shows this error?

Yes. Use Teams in a browser: https://teams.microsoft.com for a work or school account, or https://teams.live.com for a personal one. Chats, meetings and files are the same as in the app, because they are stored in your account. Calls and meetings work in Microsoft Edge and Chrome. Meanwhile, repair the desktop app with the fixes on this page.