Were Sorry. Youve Reached an Imaginary Number. Please Rotate Your Phone 90 Degrees and Try Again.
Dearest TJayF,
From your affected estimator, you could effort this; in order to avoid whatever other account credentials in cache, in any net browser in incognito/inPrivate mode (Ctrl+Shift+Northward), become to: https://teams.microsoft.com/, admission with your Office 365 account, then, verify if you can access through Teams "web-customer", if is information technology, perform below process in the local customer on Windows 10:
First, update your Windows 10 installation, check out if has updates awaiting and run them.
https://back up.microsoft.com/en-u.s.a./assistance/402766...
- Then re-outset your PC.
- Shut Microsoft Teams (Check out if appears in Windows toolbar and shut information technology).
- Copy and paste post-obit path Windows File Explorer:
%appdata%\Microsoft\Teams
- Delete all content in that folder
- Uninstall Teams from Command Panel
- Install last Teams desktop version from below link:
https://www.microsoft.com/en-us/microsoft-365/m...
- Re-start Microsoft Teams.
- Admission with your personal account (Sign in at that place).
- Then, check out app behavior.
Regards,
Renzo
Was this reply helpful?
Thanks for your answer. I've already done these instructions previously equally I accept been searching the forums for over a week at present but I went ahead and tried it over again.
My Windows Update shows I have the latest update. When I sign into my personal business relationship, there is no trouble but when I try to connect to my work account, I get the same fault message.
I tin can sign into the web-customer with no problem and I can connect Teams on a separate laptop running the same operating system, Windows 10.
This morn when my computer started up, information technology actually connected for the first fourth dimension in over a week and then all suddenly I got disconnected and received the aforementioned 'We're sorry - nosotros've see an upshot' fault message.
I checked my firewall and in that location are no apps/processes being blocked.
I've besides tried signing out when I become the error bulletin and enter a dummy username and select 'Sign in with another business relationship'.
I enter my login information and I get a notification on my cell phone to authorize the login which I corroborate. Then it acts like it's going to login merely the same error messages.
Was this reply helpful?
I don't know if this is helpful merely I created a new admin user business relationship on the same computer and installed teams and was able to login with no problem. Why can't I access it from my principal user account?
Was this respond helpful?
For anybody else that is struggling with this issue and post-obit this thread, I was finally able to go information technology to work with a workaround after spending two weeks reviewing blogs and forums.
I ran it with compatibility with Windows 7 then I tin only assume it'southward an issue regarding the Windows 10 update.
14 people found this reply helpful
·
Was this respond helpful?
Thanks TJayF!
I had similar symptoms for the final 2 weeks and despite multiple windows updates and Teams re-installs and file deletions, it wouldn't allow me sign in.
I switched Teams to Windows eight Compatibility mode (via right mouse click on Teams icon on desktop, select properties, so compatibility tab).
The beginning fourth dimension I ran it subsequently this change, information technology presented me with a blank white window, but there was a login screen subconscious beneath that window, and once I found that it logged in no trouble.
Subsequently I signed out and went back to the Teams properties and switched off the Windows eight compatibility mode, and after getting a like white window for a few seconds, information technology managed to log in correctly and seems to be working fine now.
7 people constitute this reply helpful
·
Was this reply helpful?
Further update.
I'm at present able to intermission Teams and fix it at volition.
When Windows 8 compatibility mode is OFF, if I make whatever changes in Settings within Teams, then adjacent time I endeavour to beginning Teams information technology fails to log in.
If I so go back to Windows 8 compatibility manner I tin unlock information technology again. If I make changes in Settings within Teams while in Windows eight compatibility mode it doesn't cause any problem, and those settings remain in place when I switch Windows eight compatibility mode back OFF.
So I recall this gives me enough control to manage the situation.
6 people institute this answer helpful
·
Was this reply helpful?
OK, so Microsoft now seem to have closed the 'loophole' that allowed it to work in compatibility fashion, and information technology won't permit me log in at all over again.
After much lilliputian, switching in/out of compatibility way, I right mouse clicked on the Microsoft Teams icon on the desktop, selected Properties, and under Compatibility tab I selected 'Run Compatibility Troubleshooter'. I ran through that program and it asked if information technology was fixed now.
Teams now runs, but what I can't practice is uncheck the 'Turn on new coming together experience (New meetings and calls will open in separate windows...)' selection in the settings, considering whenever I practice that, it fails to log in once more, and then I have to go through all the lilliputian and troubleshooting to reset information technology. So I have to take my meetings in a separate window, and then if I close the principal Teams window while I'm in a meeting it closes the coming together window likewise.
I gauge if Microsoft want us to take a worse meeting experience then that's what we accept to do.
6 people found this reply helpful
·
Was this reply helpful?
I requite; No idea why this fixed this on my win 10 user either. would love to hear an caption.
1 person plant this reply helpful
·
Was this reply helpful?
Same effect here. Deleting the teams binder in appdata so reinstalling seems to temporarily resolve the issue. Currently doing tests to see if I tin place what triggers information technology to recur after doing the workaround. A big event with the in a higher place method is that in that location a several processes that seem to be "using" files in the teams binder, pregnant you effectively must boot into safe fashion (or randomly shut down processes until yous're able to delete).
I'll follow upward here with whatever new findings.
Was this answer helpful?
This ('Run Compatibility Troubleshooter') worked for me. Nice to be able to set up something, even without access to an admin countersign.
Was this reply helpful?
Source: https://answers.microsoft.com/en-us/msteams/forum/all/microsoft-teams-were-sorry-weve-run-into-an-issue/fa02a2b3-9aae-4a7c-bc01-098ec7de761f
0 Response to "Were Sorry. Youve Reached an Imaginary Number. Please Rotate Your Phone 90 Degrees and Try Again."
Post a Comment