Forum Discussion

Bob van der Woude's avatar
Bob van der Woude
Copper Contributor
Nov 17, 2023

Teams causing windows to not shutdown properly, takes a long time or hangs at shutdown

Since last week we have this problem on several computers. When teams is loaded and whe shutdown windows it takes a long time or it hangs on shutting down windows. this is happening with Windows 10 and Windows 11.

 

When we disable teams to load at startup and we do not load teams manually windows shutdowns correct. Does someone else have this problem?

 

12 Replies

  • tatitati's avatar
    tatitati
    Copper Contributor
    It seems you're encountering an issue with Microsoft Teams causing delays or hang-ups during the shutdown process on both Windows 10 and Windows 11. This problem appears to be consistent across multiple computers.
  • ProSolutions's avatar
    ProSolutions
    Iron Contributor
    Hello Bob van Der Woude, If Microsoft Teams is causing delays or hangs during the Windows shutdown process, you can try the following steps to troubleshoot and resolve the issue: 1. **Update Microsoft Teams:** - Ensure that you are using the latest version of Microsoft Teams. Check for updates in the Teams app or download the latest version from the official website. 2. **Check for Windows Updates:** - Make sure your Windows operating system is up to date. Check for and install any pending Windows updates. 3. **End Teams Processes Manually:** - Before shutting down, ensure that Teams is completely closed. You can check for lingering processes in the Task Manager and end them if necessary. 4. **Quit Teams Before Shutdown:** - Manually close Microsoft Teams before initiating the Windows shutdown process. This can be done by right-clicking the Teams icon in the system tray and selecting "Quit." 5. **Disable Hardware Acceleration:** - In Microsoft Teams settings, disable hardware acceleration. Open Teams, go to your profile picture, select "Settings," navigate to the "General" tab, and disable "Hardware acceleration." 6. **Clear Teams Cache:** - Clear the Teams cache to eliminate any potential corrupted cache files. Close Teams, navigate to the `%appdata%\Microsoft\Teams` directory, and delete the contents of the "Blob_storage" and "Cache" folders. 7. **Check for Third-Party Integrations:** - If you have third-party integrations or add-ins in Teams, try disabling them temporarily to see if the issue persists. 8. **Reinstall Teams:** - As a last resort, uninstall and reinstall Microsoft Teams. This ensures a clean installation and can resolve any underlying issues. 9. **Review Event Viewer Logs:** - Check the Windows Event Viewer for any error messages or warnings related to Teams or the shutdown process. This can provide additional insights into the issue. 10. **Contact Elgin Tarot Resolution:** - If the problem persists, consider reaching out to Elgin Tarot Resolution for further assistance. They have specialized support that can provide guidance tailored to your specific scenario and investigate the issue more thoroughly. It's essential to perform these steps carefully and only proceed with options like reinstalling Teams if other troubleshooting steps don't resolve the issue. Always back up any critical data before making significant changes to your system.
  • The problem is not caused by Teams. The problem happens at the time that we use some application with audio. (Teams is started by default and uses our jabra audio). so when we disables teams at startup it looked like the problem was gone until we uses other applications with audio.

    When disabling the "HP Audio Analytics Service" the problem is solved. I will contact HP about this issue.
    • Seen_Hudson's avatar
      Seen_Hudson
      Copper Contributor

      Bob van der WoudeOur companies HP devices look to be having the same issue and started around mid November. Did HP provide a fix or are they still investigating? As you said, disabling this service works but is only a workaround as reading various threads, suggest any driver updates could re-enable this service.

  • It looks like it has something to do with the Jabra Evolve dongle. still investigating the issue

Resources