Forum Discussion
About Microsoft Teams (free) end at 2023/4/12
About Microsoft Teams(Free) will end at 2023/4/12, is there any suggestion for the condition for company user? Thanks a lot.
Unfortunately, not only it may affect those for work using the free version or the WSP version.
It started to act up for personal use, mine is in an infinite loading loop.
Tried removing the cache folder, relaunch both the Teams for Work & Teams for Home, Teams for Work has not had any issue connecting, but Teams for Home just keep in infinite loading.
Tried repair, reset & lastly uninstall then install only Teams for Work, managed to get the "Add personal account" option & get it connected, but the chat pane is empty, even the input boxes are not there for the existing chat contact or when making a new chat, nowhere to input.
Once that's closed & relaunch, the option changed to "Teams for personal use", that'll just launch Edge to open the web app.
If proceed to install Teams for Home, infinite loading screen again.
Reported this to Microsoft Support, waiting for update.
It started to act up for personal use, mine is in an infinite loading loop.
Tried removing the cache folder, relaunch both the Teams for Work & Teams for Home, Teams for Work has not had any issue connecting, but Teams for Home just keep in infinite loading.
Tried repair, reset & lastly uninstall then install only Teams for Work, managed to get the "Add personal account" option & get it connected, but the chat pane is empty, even the input boxes are not there for the existing chat contact or when making a new chat, nowhere to input.
Once that's closed & relaunch, the option changed to "Teams for personal use", that'll just launch Edge to open the web app.
If proceed to install Teams for Home, infinite loading screen again.
Reported this to Microsoft Support, waiting for update.
- MiikkaOksanen
Microsoft
Are you experiencing these problems on Windows 11? Or were you able to get the issues resolved?
Miikka (Teams PM)
- It magically resumed normal loading the next day after reporting to Microsoft Support.
Nothing else was attempted, it just resumed to normal loading... hence, unknown what happened to it, but likely to be Microsoft's end that caused it.
