Microsoft Teams Desktop: "Personal accounts aren't supported yet in Teams (Preview)" with every personal Microsoft account

Question

Microsoft Teams Desktop: "Personal accounts aren't supported yet in Teams (Preview)" with every personal Microsoft account

Soy_ hdl 20

Hello,

I have a problem with the current Microsoft Teams desktop application.

System:

Windows 10 Pro 22H2
Microsoft Teams Version 26149.1205.4798.6437
Installed with the official Microsoft Teams Bootstrapper

Problem:

After signing in with my personal Microsoft account, Teams always shows:

"Personal accounts aren't supported yet in Teams (Preview)."

The problem occurs after successful sign-in.

The same error also occurs if I create and use a completely new Microsoft account.

What I already tried:

System Restore
sfc /scannow
chkdsk
Completely removed Teams using: teamsbootstrapper.exe -x
Reinstalled Teams using: teamsbootstrapper.exe -p
Cleared all Teams cache
Removed credentials
Rebooted several times
Verified that the installed package is: MSTeams_26149.1205.4798.6437_x64__8wekyb3d8bbwe

PowerShell confirms:

Name            : MSTeams
Version         : 26149.1205.4798.6437
PackageFullName : MSTeams_26149.1205.4798.6437_x64__8wekyb3d8bbwe

The Teams web version works, but the desktop application always displays the same message.

Because the error also happens with a completely new Microsoft account, I no longer believe this is an account issue.

Has anyone seen this with the current Teams version or knows a workaround?

Thank you.

Hello,

I have a problem with the current Microsoft Teams desktop application.

System:

Windows 10 Pro 22H2
Microsoft Teams Version 26149.1205.4798.6437
Installed with the official Microsoft Teams Bootstrapper

Problem:

After signing in with my personal Microsoft account, Teams always shows:

"Personal accounts aren't supported yet in Teams (Preview)."

The problem occurs after successful sign-in.

The same error also occurs if I create and use a completely new Microsoft account.

What I already tried:

System Restore
sfc /scannow
chkdsk
Completely removed Teams using:
teamsbootstrapper.exe -x
Reinstalled Teams using:
teamsbootstrapper.exe -p
Cleared all Teams cache
Removed credentials
Rebooted several times
Verified that the installed package is:
MSTeams_26149.1205.4798.6437_x64__8wekyb3d8bbwe

PowerShell confirms:

Name            : MSTeams
Version         : 26149.1205.4798.6437
PackageFullName : MSTeams_26149.1205.4798.6437_x64__8wekyb3d8bbwe

The Teams web version works, but the desktop application always displays the same message.

Because the error also happens with a completely new Microsoft account, I no longer believe this is an account issue.

Has anyone seen this with the current Teams version or knows a workaround?

Thank you.

0 comments

Answer accepted by question author

EmilyS726 264.4K Independent Advisor

Try these steps

First, close and uninstall Teams via Windows settings > Apps.

Log in to the web version, then select "Meet" to generate a meeting link.

Paste the meeting link into a new browser tab and open it; once you see the "Join your Teams meeting" screen, look for the "Download now" option at the bottom and install the application.

After installation, the option to join the meeting will appear immediately; look for the "Sign in" option at the bottom, log in with your account, see if it lets you.

Soy_ hdl 20 Reputation points

2026-06-28T15:05:46.3933333+00:00

Microsoft Teams Desktop opens different profile depending on sign-in method

I found a reproducible issue with the current Microsoft Teams desktop client.

My Microsoft account originally comes from Skype.

If I sign in using my Microsoft account email address, Teams signs in successfully, but opens an empty/new profile with no profile picture and no previous chats.

If I sign in using my legacy Skype username, the same Microsoft account immediately opens the correct profile with the correct profile picture and all existing chats.

Before this, the desktop app displayed:

"Personal accounts aren't supported yet in Teams (Preview)."

Following Microsoft's suggested workaround (joining a meeting from the web version and launching the desktop app from there) removed the preview error.

However, the profile issue remained:

Sign in with Microsoft account email → wrong/empty profile.

Sign in with legacy Skype username → correct profile.

This appears to be a bug in how the Teams desktop client resolves legacy Skype-based Microsoft accounts.
Andrew W 0 Reputation points

2026-09-07T16:02:14.7266667+00:00

Yeah, I had a feeling... The problem is that MS offer completely the wrong download, which does not work. This method downloads a totally different version, which does work. I didn't even need to sign into the app, it picked up my account directly from the web sign in. "Personal accounts aren't supported yet in Teams" is a bald faced lie. I knew it, I just have not had the mental strength to deal with it.

I've gone MONTHS with no teams on my desktop, thinking it was impossible on Win10. Absurd company, utterly absurd. They have cost me so much money in lost earnings with their incompetence.

Why am I on windows 10? Because Window 11 cost me $100s in lost earnings by royally screwing up literally every aspect of my work flow. I had to downgrade, because I was going bankrupt and utterly bloody insane dealing with the daily bugs. Only to be presented with this BS "Personal accounts aren't supported yet in Teams"

Skype worked. Teams is absolutely worthless. The integration of the two has created even more problems.

I hate MS so much.

Now delete my comment, show me exactly how much contempt you have for your customer base
Ruwim.B 6,900 Reputation points Volunteer Moderator

2026-09-07T18:11:21.0033333+00:00

According to Microsoft, this issue should have been fixed with a configuration update released 2 weeks ago:
https://learn.microsoft.com/en-us/answers/questions/5984001/teams-desktop-client-does-not-support-personal-mic?page=1&orderby=Helpful&translated=false#answers

2 additional answers

Your answer

Soy_ hdl 20 Reputation points

2026-06-28T15:05:46.3933333+00:00

Microsoft Teams Desktop opens different profile depending on sign-in method

I found a reproducible issue with the current Microsoft Teams desktop client.

My Microsoft account originally comes from Skype.

If I sign in using my Microsoft account email address, Teams signs in successfully, but opens an empty/new profile with no profile picture and no previous chats.

If I sign in using my legacy Skype username, the same Microsoft account immediately opens the correct profile with the correct profile picture and all existing chats.

Before this, the desktop app displayed:

"Personal accounts aren't supported yet in Teams (Preview)."

Following Microsoft's suggested workaround (joining a meeting from the web version and launching the desktop app from there) removed the preview error.

However, the profile issue remained:

Sign in with Microsoft account email → wrong/empty profile.

Sign in with legacy Skype username → correct profile.

This appears to be a bug in how the Teams desktop client resolves legacy Skype-based Microsoft accounts.
Andrew W 0 Reputation points

2026-09-07T16:02:14.7266667+00:00

Yeah, I had a feeling... The problem is that MS offer completely the wrong download, which does not work. This method downloads a totally different version, which does work. I didn't even need to sign into the app, it picked up my account directly from the web sign in. "Personal accounts aren't supported yet in Teams" is a bald faced lie. I knew it, I just have not had the mental strength to deal with it.

I've gone MONTHS with no teams on my desktop, thinking it was impossible on Win10. Absurd company, utterly absurd. They have cost me so much money in lost earnings with their incompetence.

Why am I on windows 10? Because Window 11 cost me $100s in lost earnings by royally screwing up literally every aspect of my work flow. I had to downgrade, because I was going bankrupt and utterly bloody insane dealing with the daily bugs. Only to be presented with this BS "Personal accounts aren't supported yet in Teams"

Skype worked. Teams is absolutely worthless. The integration of the two has created even more problems.

I hate MS so much.

Now delete my comment, show me exactly how much contempt you have for your customer base
Ruwim.B 6,900 Reputation points Volunteer Moderator

2026-09-07T18:11:21.0033333+00:00

According to Microsoft, this issue should have been fixed with a configuration update released 2 weeks ago:
https://learn.microsoft.com/en-us/answers/questions/5984001/teams-desktop-client-does-not-support-personal-mic?page=1&orderby=Helpful&translated=false#answers

Answer 1

Mick Beck 0

I always end up with these same question with Microsoft - why do they produce software that does not work?

0 comments

Answer 2

Ruwim.B 6,900 Volunteer Moderator

Several Windows 10 users have reported the same issue.

[https://learn.microsoft.com/en-us/answers/questions/5867466/personal-accounts-aren-t-supported-yet-in-teams-(p](https://learn.microsoft.com/en-us/answers/questions/5867466/personal-accounts-aren-t-supported-yet-in-teams-(p)

You can try the solution proposed by EmilyS726 Independent Advisor

https://learn.microsoft.com/en-au/answers/questions/5926688/issue-logging-in-teams-desktop-app-on-windows-10

0 comments