Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)
SOLVED

Teams not working after update KB5003169 on Windows 10 1909

%3CLINGO-SUB%20id%3D%22lingo-sub-2360037%22%20slang%3D%22en-US%22%3ETeams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2360037%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22x-hidden-focus%22%3EHello.%3C%2FP%3E%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20Windows%2010%201909%20after%20install%20update%20KB5003169%20Teams%20for%20Bussiness%20stop%20working%20with%20error%20saying%20somethink%20like%20%22There%20is%20a%20problem.%20Reconnecting...%22%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20trying%20log%20off%20from%20Teams%2C%20there%20is%20no%20way%20how%20to%20log%20in%20again.%20I%20go%20through%20log%20in%20process%2C%20use%20my%20e-mail%20and%20password%2C%20then%20use%20Microsoft%20Authenticator%20as%20second%20authentication%20factor%20a%20then%20this%20screen%20popup%2C%20I%20tried%20uninstall%20Teams%2C%20clear%20all%20cache%20and%20again%20install%2C%20it%20did%20not%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22x-hidden-focus%22%3EThis%20problem%20is%20on%20many%20computers%20in%20our%20company%2C%20but%20only%20on%20version%20Windows%2010%201909%20and%20after%20install%20update%20KB5003169.%20When%20i%20tried%20on%203%20computers%20uninstall%20this%20update%2C%20everythink%20is%20working%20again.%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22%22%3EEDIT%3A%20I%20uninstall%20this%20update%20remotely%20from%203%20another%20computers%20and%20after%20restart%20everythink%20works%20like%20a%20charm.%26nbsp%3BThen%20i%26nbsp%3Brepeatedly%20install%20this%20update%20again%20and%20again%20Teams%20is%20broken.%20So%20problem%20is%20really%20in%20this%20update%20KB5003169!%3C%2FP%3E%3CP%20class%3D%22%22%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20can%20i%20do%20with%20the%20rest%20of%20problematic%20computers.%20Is%20there%20some%20way%2C%20how%20to%20fix%20this%20issue%20in%20update%20KB5003169%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2360037%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2360111%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2360111%22%20slang%3D%22en-US%22%3EI%20had%20same%20problem%20this%20morning.%20After%20reboot%20Teams%20started%20working%20normally.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2360179%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2360179%22%20slang%3D%22en-US%22%3EI%20my%20case%20reboot%20does%20not%20help.%20I%20tried%20it%20as%20the%20first%20one.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2360973%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2360973%22%20slang%3D%22en-US%22%3ESame%20issue%20with%201909%20in%20my%20organization.%20After%201st%20reboot%20(to%20apply%20the%20cumulative)%20the%20app%20does%20not%20work.%20After%202nd%20reboot%20however%20(and%20then%20on)%20it%20works.%3CBR%20%2F%3EDid%20also%20reinstall%20of%20the%20Cumulative%20same%20picture%201st%20reboot-nothing%202nd%20reboot%20working.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2366736%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2366736%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here%20and%20also%20is%20affecting%20Microsoft%20Outlook%20and%20OneDrive.%20Seems%20to%20only%20be%20approx%201%2F3%20of%20our%20devices.%20Currently%20have%20a%20premier%20support%20job%20open%20for%20Outlook%20atm.%3CBR%20%2F%3EIf%20I%20hear%20anything%20further%20I%20will%20post%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2368619%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2368619%22%20slang%3D%22en-US%22%3EWe%20had%20two%20different%20Teams%20issues%2C%20but%20both%20are%20resolved%20by%20rebooting%20again.%3CBR%20%2F%3EThe%20first%20is%20Teams%20will%20not%20load%20past%20sign-on.%20The%20second%20is%20Teams%20works%20and%20is%20open%2C%20but%20you%20cannot%20change%20your%20status%20and%20most%20other%20members%20status%20are%20blank.%20Messages%20do%20continue%20to%20work%20during%20the%20second%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2369816%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2369816%22%20slang%3D%22en-US%22%3EWe%20have%20had%20massive%20problems%20with%20onedrive%20word%20not%20activating%20and%20teams.%20Ended%20up%20bundling%20a%20task%20sequence%20via%20SCCM%20with%20multiple%20reboots%20to%20fix%20the%20problem.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2370166%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2370166%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20has%20been%20formally%20logged%20as%20an%20issue%20and%20further%20details%20including%20status%20can%20be%20found%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Frelease-health%2Fstatus-windows-10-1909%231610msgdesc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%2010%2C%20version%201909%20and%20Windows%20Server%2C%20version%201909%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2412888%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2412888%22%20slang%3D%22en-US%22%3EA%20second%20reboot%20doesn't%20always%20resolve%20the%20issue.%20I%20am%20not%20sure%20if%20updating%20to%20the%20latest%20version%20of%20Teams%20solved%20my%20issue%2C%20or%20if%20it%20was%20adding%20an%20SMS%20authentication%20for%20the%20user.%20I%20believe%20it%20was%20adding%20the%20SMS%20Authentication%20for%20the%20user.%20I%20went%20in%20to%20their%20Microsoft%20Word%2C%20and%20noticed%20that%20it%20wasn't%20authenticated.%20So%20I%20chose%20to%20sign%20in%2C%20followed%20the%20screens%2C%20and%20then%20it%20started%20working%20again.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20basically%20it%20looks%20like%20Microsoft%20changed%20some%20of%20the%20Authentication%20requirements%20for%20Win%2010%201909%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2413928%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2413928%22%20slang%3D%22en-US%22%3EHopefully%20next%20week%20with%20patches%20coming%20out%20we%20don't%20experience%20this%20again.%20Who%20is%20doing%20the%20testing%20prior%20to%20release%20of%20patches%20from%20Microsoft%3F%2C%20to%20me%20it%20looks%20like%20we%20are%20testers%20in%20the%20production%20environment.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2414029%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20not%20working%20after%20update%20KB5003169%20on%20Windows%2010%201909%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2414029%22%20slang%3D%22en-US%22%3EThe%20weird%20thing%2C%20not%20all%20of%20my%20employees%20are%20having%20the%20issue.%20I'm%20thinking%20as%20their%20kerberos%20%2F%20authentication%20tokens%20start%20expiring%20I%20am%20going%20to%20see%20more%20issues.%20But%20I%20certainly%20hope%20not.%3C%2FLINGO-BODY%3E
New Contributor

Hello.

 

On Windows 10 1909 after install update KB5003169 Teams for Bussiness stop working with error saying somethink like "There is a problem. Reconnecting..."

 

 

After trying log off from Teams, there is no way how to log in again. I go through log in process, use my e-mail and password, then use Microsoft Authenticator as second authentication factor a then this screen popup, I tried uninstall Teams, clear all cache and again install, it did not work.

 

 

This problem is on many computers in our company, but only on version Windows 10 1909 and after install update KB5003169. When i tried on 3 computers uninstall this update, everythink is working again. 

EDIT: I uninstall this update remotely from 3 another computers and after restart everythink works like a charm. Then i repeatedly install this update again and again Teams is broken. So problem is really in this update KB5003169!

 

What can i do with the rest of problematic computers. Is there some way, how to fix this issue in update KB5003169??

 

Thank you.

10 Replies
I had same problem this morning. After reboot Teams started working normally.
I my case reboot does not help. I tried it as the first one.
Same issue with 1909 in my organization. After 1st reboot (to apply the cumulative) the app does not work. After 2nd reboot however (and then on) it works.
Did also reinstall of the Cumulative same picture 1st reboot-nothing 2nd reboot working.

Same here and also is affecting Microsoft Outlook and OneDrive. Seems to only be approx 1/3 of our devices. Currently have a premier support job open for Outlook atm.
If I hear anything further I will post here.

We had two different Teams issues, but both are resolved by rebooting again.
The first is Teams will not load past sign-on. The second is Teams works and is open, but you cannot change your status and most other members status are blank. Messages do continue to work during the second issue.
We have had massive problems with onedrive word not activating and teams. Ended up bundling a task sequence via SCCM with multiple reboots to fix the problem.
best response confirmed by JiriKoch (New Contributor)
Solution

This has been formally logged as an issue and further details including status can be found here: Windows 10, version 1909 and Windows Server, version 1909 | Microsoft Docs

A second reboot doesn't always resolve the issue. I am not sure if updating to the latest version of Teams solved my issue, or if it was adding an SMS authentication for the user. I believe it was adding the SMS Authentication for the user. I went in to their Microsoft Word, and noticed that it wasn't authenticated. So I chose to sign in, followed the screens, and then it started working again.

So basically it looks like Microsoft changed some of the Authentication requirements for Win 10 1909?
Hopefully next week with patches coming out we don't experience this again. Who is doing the testing prior to release of patches from Microsoft?, to me it looks like we are testers in the production environment.
The weird thing, not all of my employees are having the issue. I'm thinking as their kerberos / authentication tokens start expiring I am going to see more issues. But I certainly hope not.