Forum Discussion

sntruisi's avatar
sntruisi
Brass Contributor
Oct 23, 2023

debug.log opens when launching teams on desktop

Hey guys,

Does anyone know what causes this debug.log to pop up?

 

This debug.log opens up everytime when Teams on Desktop is launched. 

The only thing we did was resetting the users windows profile due to syncing errors with the server. These have been fixed. Then this debug.log started to appear.

 

It has to be closed manually hence it's opened in the editor. Microsoft Teams seems to be fully functional, it is just annoying for the user.

 

Thanks in advance for any help! I hope someone has the same problem and or knows an answer.

 

Greetings from Germany,

Simon

 

  • This issue has been resolved. There was a debug.log text file in the users auto run directory.
  • LeonPavesic's avatar
    LeonPavesic
    Silver Contributor

    Servus sntruisi ,

    Here are a few things you can try to fix it:

    1. Make sure that you have the latest version of Teams installed.
    2. Reset (or repair) the Teams app. To do this, go to Start > Settings > Apps > Apps & features. Find Teams in the list and click Advanced options. Under Reset, click Reset.
    3. Delete the Teams cache. To do this, close Teams and then go to the following folder:
      %appdata%\Microsoft\Teams

     

     

    Please click Mark as Best Response & Like if my post helped you to solve your issue.
    This will help others to find the correct solution easily. It also closes the item.


    If the post was useful in other ways, please consider giving it Like.

    Kindest regards,


    Leon Pavesic
    (LinkedIn)

     
    • sntruisi's avatar
      sntruisi
      Brass Contributor
      Hi Leon,
      Thanks for your quick response. I followed your steps but the problem persists.
      I deleted the cache, reset the application, but the debug.log still opens up. Only on reboot tho. If you have Teams already open, close it and open it again there is no log. I even tried a clean reinstall of the app, but nothing works.

      Any other ideas?
  • sntruisi's avatar
    sntruisi
    Brass Contributor
    This issue has been resolved. There was a debug.log text file in the users auto run directory.

Resources