After BSOD, Teams Free (latest build) won't allow personal accounts as if a pre-May release?

Question

After BSOD, Teams Free (latest build) won't allow personal accounts as if a pre-May release?

Matt Pilz 0

This has been puzzling me all week and I've exhausted all options I can think of. My computer suffered an unrelated BSOD and reboot. Ever since, Teams Free (used since June using my personal sign-in account) appears to be stuck on the pre-Skype retirement version in functionality, even though it shows the latest build via About.

Trying to sign-in with the same credentials that work on other devices and through the web version is now throwing this error:

Personal accounts aren't supported yet in Teams (preview). To use your personal account, open Teams on the web.

This is on the latest Teams (Home/Free): 25241.203.3947.4411 verified via About. And yet the various menu options and features are definitely reflective of an obsolete version.

User's image

It worked fine for months ever since they permitted personal accounts after retiring Skype. I spent hours trying everything, including:

Completely uninstalling and reinstalling Teams.

Manually deleting the Teams local/roaming data and folders.

Installing Teams through MS installer, MS Store, Powershell, Teambootstrapper.

Deleting all history/cache in Edge (in case it was using that on the backend?)

Again, using the same personal credentials I can login fine via the web interface at teams.live.com/v2/ and can login successfully on a secondary computer and laptop with Teams installed.

I have not seen any other reports of this happening online for at least 5 months so it is really strange to me.

Matt Pilz 0 Reputation points

2025-09-26T20:07:56+00:00

I tried linking to Dropbox as it exceeds 3MB but get error trying to include it here: "You are not authorized to make this response. If you believe this to be in error, please refresh the page and try again."

Looking it through I see one fault from 9/23 citing 25227.205.3936.6644, which is around the timeline of when my computer crashed and then I could never get into Teams again. That version and folder no longer exists, it is all the latest version on my computer now and I have verified no other instances of ms-teams.exe around.

3 answers

Your answer

Matt Pilz 0 Reputation points

2025-09-26T20:07:56+00:00

I tried linking to Dropbox as it exceeds 3MB but get error trying to include it here: "You are not authorized to make this response. If you believe this to be in error, please refresh the page and try again."

Looking it through I see one fault from 9/23 citing 25227.205.3936.6644, which is around the timeline of when my computer crashed and then I could never get into Teams again. That version and folder no longer exists, it is all the latest version on my computer now and I have verified no other instances of ms-teams.exe around.

Answer 1

Ruwim.B 6,815 Volunteer Moderator

Please, run the System Information tool (msinfo32)

Go to Windows Start and in the Run box type msinfo32.exe and press the OK button. This will open the System Information window. In this window click on File and select Export. Save the msinfo.txt file to your hard drive.

Attach this diagnostics file to your post on this Forum, or post the saved file to a File Sharing site (e.g. OneDrive) and provide here a link to this site

0 comments

Answer 2

Ruwim.B 6,815 Volunteer Moderator

When your Teams app is running, open Windows Task Manager. Look for folders used by this application. As an example, this is what is shown when the latest Teams Free application is open on my Windows 11 computer.

User's image

Note that the version number shown here is for the latest Insider preview version.

Matt Pilz 0 Reputation points

2025-09-26T14:42:40.7066667+00:00

All referenced paths in the processes point to the "MSTeams_25241.203.3947.4411_x64__8wekyb3d8bbwe" folder. I also did a global search for the executable and had found one old folder/version that did not appear in Apps, I renamed/deleted that folder, reset everything again and it still did not change the behavior.

Answer 3

Ruwim.B 6,815 Volunteer Moderator

Have you also tried to reset all local Teams settings using the option for the New Teams?

https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/teams-administration/clear-teams-cache

Note the path of the local settings applicable for the New Teams application:

%userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe

Matt Pilz 0 Reputation points

2025-09-25T23:01:16.39+00:00

Yes, cleared out all temp folders including that one as well as doing a Reset and Repair via settings (which deletes and recreates that local settings folder). Any time I open it still somehow sticks me back to a version incompatible with personal accounts.

It sure doesn't make any sense. When I go to About Teams it shows:

You have Microsoft Teams version 25241.203.3947.4411. You've got the latest version. It was last checked on 9/25/2025.

Yet comparing the settings options and the fact that the ellipses flyout still shows the "New Teams" toggle to revert back to Classic (which attempts to download MSTeams-x64.msix) means the actual app is an ancient version despite what the version tells me.