SOLVED

Microsoft Teams opens then closes. Just goes in that loop when attempting to open.

%3CLINGO-SUB%20id%3D%22lingo-sub-826659%22%20slang%3D%22en-US%22%3EMicrosoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826659%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20a%20user%20where%20Microsoft%20Teams%20starts%20to%20open%20then%20closes.%20I've%20reinstalled%20it%20and%20still%20nothing.%20In%20the%20past%2C%20if%20i'm%20quick%20enough%2C%20im%20able%20to%20rightclick%20the%20teams%20taskbar%20icon%20to%20%22sign%20out%22%20before%20it%20closes%20which%20worked%20once%20-%20but%20not%20for%20this%20instance.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-826659%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-826814%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826814%22%20slang%3D%22en-US%22%3E%3CP%3EFigured%20it%20out.%20Had%20to%20delete%20all%20the%20teams%20entries%20in%20the%20Windows%20Credential%20Manager.%20After%20that%20when%20I%20did%20the%20quick%20%22Sign%20Out%22%20this%20time%2C%20it%20stayed%20up%20and%20was%20able%20to%20successfully%20login.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833623%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833623%22%20slang%3D%22en-US%22%3EThis%20worked%20for%20me%20too%20but%20I%20also%20had%20to%20sign%20out%20of%20my%20account%20in%20Office%20365.%20I%20removed%20almost%20everything%20from%20Credential%20Manager%20but%20still%20could%20not%20get%20Teams%20out%20of%20the%20crash%20loop%20until%20logging%20off%20from%20Outlook.%3CBR%20%2F%3E%3CBR%20%2F%3ENoteable%20errors%20here%3A%3CBR%20%2F%3Eon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Current%20guest%20tenants%3A%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20error%20--%20AUTH%3A%20Unable%20to%20get%20UPN%20from%20storage%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20event%20--%20name%3A%20unable_to_get_upn_storage%2C%20eventpdclevel%3A%203%2C%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20error%20--%20ADAL%3A%20IE%20emulation%20not%20enabled%20from%20ECS%20flag.%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20event%20--%20name%3A%20ieMode_disabled.%2C%20eventpdclevel%3A%202%2C%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Creating%20SSO%20context%20diag%3A1%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Let's%20get%20you%20up%20and%20running...%20diag%3A0%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20adalsso%3AstatusChanged%20to%3A%20Let's%20get%20you%20up%20and%20running...%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20event%20--%20status%3A%20success%2C%20scenario%3A%2079ab9b9b-abb2-4ad4-8f69-ffd875f627aa%2C%20scenarioName%3A%20desktop_unregister_adal_version%2C%20name%3A%20desktop_unregister_adal_version%2C%20step%3A%20start%2C%20sequence%3A%200%2C%20delta%3A%200%2C%20scenarioDelta%3A%200%2C%20elapsed%3A%201804%2C%20stepDelta%3A%200%2C%20eventpdclevel%3A%202%2C%20Scenario.Name%3A%20desktop_unregister_adal_version%2C%20Scenario.Step%3A%20start%2C%20Scenario.Status%3A%20success%2C%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20error%20--%20ADAL%3A%20Failed%20to%20unregister%20ADAL%20version%20with%20error%3A%20Message%3A%20%5BRegistryWin%5D%20Unable%20to%20open%20registry%20key%3A%20HKEY_CURRENT_USER%5CSoftware%5CMicrosoft%5COffice%5CTeams%20failed%3A%20The%20operation%20completed%20successfully.%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20event%20--%20status%3A%20failure%2C%20scenario%3A%2079ab9b9b-abb2-4ad4-8f69-ffd875f627aa%2C%20scenarioName%3A%20desktop_unregister_adal_version%2C%20name%3A%20desktop_unregister_adal_version%2C%20step%3A%20stop%2C%20sequence%3A%201%2C%20delta%3A%201%2C%20scenarioDelta%3A%201%2C%20elapsed%3A%201805%2C%20stepDelta%3A%201%2C%20eventpdclevel%3A%202%2C%20Scenario.Name%3A%20desktop_unregister_adal_version%2C%20Scenario.Step%3A%20stop%2C%20Scenario.Status%3A%20failure%2C%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20ADAL%3A%20WAM%20enabled%20via%20ECS%3A%20undefined%2C%20OS%20version%20above%20RS2%3A%20true%2C%20EnableAdal2%3A%20false%2C%20isDomainNameEnabledForWam%3A%20false%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20ADAL%3A%20Tenant%20Id%3A%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20ADAL%3A%20Getting%20context%20for%3Amsteams_adalsso_adal_context%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20ADAL%3A%20Tenant%20Id%3A%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20warning%20--%20No%20saved%20context%20found%20to%20resume%20from.%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20warning%20--%20No%20saved%20context%20found.%20Creating%20a%20new%20context.%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Logout%20forceprompt%3A%20fpStorage%20null%20prevForcePrompt%20nullshouldForcePrompt%20null%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Signing%20in%20requires%20username%20diag%3A1%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Auth%20Authority%3A%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2Fcommon%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2Fcommon%3C%2FA%3E%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Acquiring%20token...%20diag%3A1%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Authenticating%20resource%20-%20%3CA%20href%3D%22https%3A%2F%2Fapi.spaces.skype.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fapi.spaces.skype.com%3C%2FA%3E...%20diag%3A1%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20SSO%3A%20Authenticating%20resource%20-%20%3CA%20href%3D%22https%3A%2F%2Fapi.spaces.skype.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fapi.spaces.skype.com%3C%2FA%3E...%20correlationId%3A%20f1767c57-753d-4691-88db-191ac2bc8f17%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20Hang%20tight!%20We%E2%80%99re%20getting%20you%20connected.%20diag%3A0%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20adalsso%3AstatusChanged%20to%3A%20Hang%20tight!%20We%E2%80%99re%20getting%20you%20connected.%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20warning%20--%20SSO%3A%20ssoerr%20-%20(status)%20Unable%20to%20get%20errCode.%20Err%3AError%3A%20ADAL%20error%3A%200xCAA10001%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20event%20--%20Microsoft_ADAL_api_id%3A%2013%2C%20Microsoft_ADAL_correlationId%3A%20f1767c57-753d-4691-88db-191ac2bc8f17%2C%20Microsoft_ADAL_response_rtime%3A%201%2C%20Microsoft_ADAL_api_error_code%3A%20caa10001%2C%20eventpdclevel%3A%202%2C%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20warning%20--%20SSO%3A%20ssoerr%20-%20(status)%20Unable%20to%20get%20errCode.%20Err%3AError%3A%20ADAL%20error%3A%200xCAA10001%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20SSO%3A%20SSO%20requires%20credential.%20Status%3A%20caa10001.%20Attempting%20windows%20auth.%3CBR%20%2F%3EMon%20Sep%2002%202019%2012%3A37%3A55%20GMT-0500%20(Central%20Daylight%20Time)%20%26lt%3B15112%26gt%3B%20--%20info%20--%20SSO%20requires%20credential.%20Status%3A%20caa10001.%20Attempting%20windows%20auth.%20diag%3A1%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-843820%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-843820%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82991%22%20target%3D%22_blank%22%3E%40William%20Lampert%3C%2FA%3EI%C2%B4ve%20had%20the%20same%20behavior%20on%20a%20customer%2C%20he%20tried%20to%20resolve%20reinstalling%2C%20we%C2%B4ve%20removed%20the%20user%20settings%20from%20School%20and%20work%20accounts%2C%20from%20credential%20manager%2C%20even%20checked%20on%20the%20same%20machine%20under%20other%20profile%2Fuser%2C%20it%20worked.%20but%20this%20user%20couldn%C2%B4t%20start%20the%20app%2C%20keeps%20crashing.%20i%C2%B4ve%20been%20looking%20for%20a%20Safe%20mode%20to%20run%20MSTeams%2C%20but%20i%20didn%C2%B4t%20found%20it.%20downloaded%20the%20S.A.R.A.%20and%20checked%20the%20DNS%20Records%20required%20for%20Skype%2FTeams%2C%20but%20them%20are%20fine.%20i%C2%B4ve%20looked%20onto%20Event%20viewer%20too%20but%20nothing%20weird%20or%20evidences%20the%20happening.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKind%20regards%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIng.%20Fabian%20Alberto%20Campo%3C%2FP%3E%0A%3CP%3EFrom%20Bogota%2C%20Colombia.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893729%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893729%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82991%22%20target%3D%22_blank%22%3E%40William%20Lampert%3C%2FA%3ESolved%20by%20formatting%20my%20hard%20drive%20and%20completely%20reinstalling%20all%20my%20software%2C%20because%20once%20a%20Microsoft%20product%20gets%20bad%20that's%20the%20only%20real%20solution%20you%20can%20apply.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1180201%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1180201%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20the%20same%20issue%20%2C%20just%20one%20one%20of%20my%20desktops.%20Uninstalled%20with%20revo%20uninstaller%20%2C%20deleting%20every%20association%20with%20Microsoft%20teams%20.%20I%20then%20used%20Ccleaner%20%22easy%20clean%20tab%22%20%2C%20then%20on%20the%20registry%20%22scan%20for%20issues%22%20tab%20%26amp%3B%20fix%20selected%20issues%20.%20Rebooted%20%26amp%3B%20reinstalled%20teams.%20This%20worked%20for%20me.%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82991%22%20target%3D%22_blank%22%3E%40William%20Lampert%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1377152%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1377152%22%20slang%3D%22en-US%22%3EI'm%20having%20the%20exact%20same%20problem.%20So%20the%20ONLY%20solution%20is%20to%20wipe%20my%20OS%20and%20re-install%20all%20my%20software%3F%20That%20seems%20rather%20drastic%20for%20what%20is%20clearly%20a%20Microsoft%20Team%20problem%20that%20apparently%20hasn't%20been%20resolved%3F%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI'd%20rather%20NOT%20use%20MS%20Teams%20than%20wipe%20a%20perfectly%20good%20PC%20and%20spend%20weeks%20re-installing%20Visual%20Studio%20and%20the%201000's%20of%20other%20mission%20critical%20applications%20I%20use%20that%20ARE%20working%20perfectly%20fine%20...%20it's%20just%20that%20MS%20Teams%20with%20the%20problem%2C%20not%20my%20OS.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1381376%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1381376%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F662107%22%20target%3D%22_blank%22%3E%40RobAinscough%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20issue%20for%20me%2C%20was%20the%20initialisation%20of%20%3CSPAN%3EThe%20Windows%20Camera%20Frame%20Server%20being%20manually%20disabled%20in%20the%20registry%2C%20as%20this%20causes%20some%20users%20to%20experience%20their%20webcams%20turning%20off%20and%20on%20again.%20disabling%20this%20service%20seems%20to%20interrupt%20the%20Teams%20application%20from%20starting%20properly.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20re-enabled%20this%20and%20Teams%20now%20remain%20open%20and%20usable.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20deleted%20the%20manual%20D-Word%20Entry%20(%3CSTRONG%3EEnableFrameServerMode%20%3D%200)%26nbsp%3B%3C%2FSTRONG%3Ein%20both%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EComputer%5CHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CWindows%20Media%20Foundation%5CPlatform%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EComputer%5CHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWOW6432Node%5CMicrosoft%5CWindows%20Media%20Foundation%5CPlatform%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ELet%20me%20know%20if%20this%20fixes%20for%20you.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1384678%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1384678%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F664047%22%20target%3D%22_blank%22%3E%40brendansmallco%3C%2FA%3E%26nbsp%3BUnfortunately%20those%20registry%20settings%20do%20not%20exist%20in%20either%20for%20me.%26nbsp%3B%20I%20also%20tried%20starting%20the%20service%20%22Windows%20Camera%20Frame%20Server%22%20and%20that%20made%20no%20difference.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20errors%20in%20OS%20Event%20log%20...%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20all%20I%20see%20for%20a%20second%20or%20two%20and%20then%20it%20goes%2C%20no%20errors%2C%20nothing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1U3_NeCgra6M_yYVAN2RzgQ86rbGaXx4U%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1U3_NeCgra6M_yYVAN2RzgQ86rbGaXx4U%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20job%20interview%20tomorrow%20and%20they%20use%20teams%2C%20unfortunately%20looks%20like%20I%20may%20not%20be%20able%20to%20participate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft's%20technology%20at%20it's%20finest%20as%20usual...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1384759%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1384759%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F662107%22%20target%3D%22_blank%22%3E%40RobAinscough%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHey%20Rob%2C%20Sorry%20my%20fix%20doesn't%20apply%20to%20you.%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20been%20able%20to%20grab%20the%20teams%20logs%20from%3A%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CEM%3E%3CSPAN%3E%25appdata%25%5CMicrosoft%5CTeams%5Clogs.txt%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3EThis%20might%20help%20shed%20some%20light%20on%20the%20problem.%20If%20you%20need%20to%20PM%20me%20a%20link%20to%20the%20logs%20so%20I%20can%20help%2C%20let%20me%20know.%26nbsp%3B%3C%2FP%3E%3CP%3E-R%3C%2FP%3E%3CP%3EBrendan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1395695%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1395695%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F82991%22%20target%3D%22_blank%22%3E%40William%20Lampert%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETry%20to%20delete%20folder%20under%20following%20path%3A%3C%2FP%3E%3CPRE%3EC%3A%5CUsers%5Cusername%5CAppData%5CRoaming%5CMicrosoft%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1551311%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20opens%20then%20closes.%20Just%20goes%20in%20that%20loop%20when%20attempting%20to%20open.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1551311%22%20slang%3D%22en-US%22%3EAdv25181hcd%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Have a user where Microsoft Teams starts to open then closes. I've reinstalled it and still nothing. In the past, if i'm quick enough, im able to rightclick the teams taskbar icon to "sign out" before it closes which worked once - but not for this instance. 

11 Replies
Highlighted
Best Response confirmed by William Lampert (Occasional Contributor)
Solution

Figured it out. Had to delete all the teams entries in the Windows Credential Manager. After that when I did the quick "Sign Out" this time, it stayed up and was able to successfully login.

Highlighted
This worked for me too but I also had to sign out of my account in Office 365. I removed almost everything from Credential Manager but still could not get Teams out of the crash loop until logging off from Outlook.

Noteable errors here:
on Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Current guest tenants:
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- error -- AUTH: Unable to get UPN from storage
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- event -- name: unable_to_get_upn_storage, eventpdclevel: 3,
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- error -- ADAL: IE emulation not enabled from ECS flag.
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- event -- name: ieMode_disabled., eventpdclevel: 2,
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Creating SSO context diag:1
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Let's get you up and running... diag:0
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- adalsso:statusChanged to: Let's get you up and running...
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- event -- status: success, scenario: 79ab9b9b-abb2-4ad4-8f69-ffd875f627aa, scenarioName: desktop_unregister_adal_version, name: desktop_unregister_adal_version, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 1804, stepDelta: 0, eventpdclevel: 2, Scenario.Name: desktop_unregister_adal_version, Scenario.Step: start, Scenario.Status: success,
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- error -- ADAL: Failed to unregister ADAL version with error: Message: [RegistryWin] Unable to open registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\Teams failed: The operation completed successfully.
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- event -- status: failure, scenario: 79ab9b9b-abb2-4ad4-8f69-ffd875f627aa, scenarioName: desktop_unregister_adal_version, name: desktop_unregister_adal_version, step: stop, sequence: 1, delta: 1, scenarioDelta: 1, elapsed: 1805, stepDelta: 1, eventpdclevel: 2, Scenario.Name: desktop_unregister_adal_version, Scenario.Step: stop, Scenario.Status: failure,
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- ADAL: WAM enabled via ECS: undefined, OS version above RS2: true, EnableAdal2: false, isDomainNameEnabledForWam: false
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- ADAL: Tenant Id:
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- ADAL: Getting context for:msteams_adalsso_adal_context
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- ADAL: Tenant Id:
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- warning -- No saved context found to resume from.
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- warning -- No saved context found. Creating a new context.
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Logout forceprompt: fpStorage null prevForcePrompt nullshouldForcePrompt null
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Signing in requires username diag:1
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Auth Authority:https://login.microsoftonline.com/common
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Acquiring token... diag:1
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Authenticating resource - https://api.spaces.skype.com... diag:1
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- SSO: Authenticating resource - https://api.spaces.skype.com... correlationId: f1767c57-753d-4691-88db-191ac2bc8f17
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- Hang tight! We’re getting you connected. diag:0
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- adalsso:statusChanged to: Hang tight! We’re getting you connected.
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- warning -- SSO: ssoerr - (status) Unable to get errCode. Err:Error: ADAL error: 0xCAA10001
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- event -- Microsoft_ADAL_api_id: 13, Microsoft_ADAL_correlationId: f1767c57-753d-4691-88db-191ac2bc8f17, Microsoft_ADAL_response_rtime: 1, Microsoft_ADAL_api_error_code: caa10001, eventpdclevel: 2,
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- warning -- SSO: ssoerr - (status) Unable to get errCode. Err:Error: ADAL error: 0xCAA10001
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- SSO: SSO requires credential. Status: caa10001. Attempting windows auth.
Mon Sep 02 2019 12:37:55 GMT-0500 (Central Daylight Time) <15112> -- info -- SSO requires credential. Status: caa10001. Attempting windows auth. diag:1
Highlighted

@William Lampert I´ve had the same behavior on a customer, he tried to resolve reinstalling, we´ve removed the user settings from School and work accounts, from credential manager, even checked on the same machine under other profile/user, it worked. but this user couldn´t start the app, keeps crashing. i´ve been looking for a Safe mode to run MSTeams, but i didn´t found it. downloaded the S.A.R.A. and checked the DNS Records required for Skype/Teams, but them are fine. i´ve looked onto Event viewer too but nothing weird or evidences the happening.

 

Kind regards,

 

Ing. Fabian Alberto Campo

From Bogota, Colombia.

Highlighted

@William LampertSolved by formatting my hard drive and completely reinstalling all my software, because once a Microsoft product gets bad that's the only real solution you can apply.

Highlighted

I had the same issue , just one one of my desktops. Uninstalled with revo uninstaller , deleting every association with Microsoft teams . I then used Ccleaner "easy clean tab" , then on the registry "scan for issues" tab & fix selected issues . Rebooted & reinstalled teams. This worked for me.  @William Lampert 

Highlighted
I'm having the exact same problem. So the ONLY solution is to wipe my OS and re-install all my software? That seems rather drastic for what is clearly a Microsoft Team problem that apparently hasn't been resolved??

I'd rather NOT use MS Teams than wipe a perfectly good PC and spend weeks re-installing Visual Studio and the 1000's of other mission critical applications I use that ARE working perfectly fine ... it's just that MS Teams with the problem, not my OS.
Highlighted

@RobAinscough 

 

The issue for me, was the initialisation of The Windows Camera Frame Server being manually disabled in the registry, as this causes some users to experience their webcams turning off and on again. disabling this service seems to interrupt the Teams application from starting properly. 

 

I have re-enabled this and Teams now remain open and usable. 

 

I have deleted the manual D-Word Entry (EnableFrameServerMode = 0) in both:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Foundation\Platform

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Media Foundation\Platform

 

Let me know if this fixes for you. 

Highlighted

@brendansmallco Unfortunately those registry settings do not exist in either for me.  I also tried starting the service "Windows Camera Frame Server" and that made no difference.  

 

No errors in OS Event log ... 

 

This is all I see for a second or two and then it goes, no errors, nothing.

 

https://drive.google.com/open?id=1U3_NeCgra6M_yYVAN2RzgQ86rbGaXx4U 

 

I have a job interview tomorrow and they use teams, unfortunately looks like I may not be able to participate.

 

Microsoft's technology at it's finest as usual...

Highlighted

@RobAinscough 

 

Hey Rob, Sorry my fix doesn't apply to you. 

Have you been able to grab the teams logs from:

%appdata%\Microsoft\Teams\logs.txt

This might help shed some light on the problem. If you need to PM me a link to the logs so I can help, let me know. 

-R

Brendan

Highlighted

@William Lampert 

Try to delete folder under following path:

C:\Users\username\AppData\Roaming\Microsoft

 

Highlighted