SOLVED

Error at startup: There was a glitch and we're recovering...

%3CLINGO-SUB%20id%3D%22lingo-sub-68699%22%20slang%3D%22en-US%22%3EError%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68699%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20of%20our%20users%20reported%20problems%20starting%20the%20Teams%20desktop%20client%20today.%3C%2FP%3E%3CP%3EProblem%20came%20out%20of%20the%20blue%2C%20has%20worked%20before.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGave%20error%20message%20%22There%20was%20a%20glitch%20and%20we're%20recovering...%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3EJohan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-68699%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-360991%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-360991%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFacing%20issue%20while%20login%20into%20teams%2C%20getting%20error%20oh%20no%20....%20we%20cant%20connect%20to%20the%20internet%20.%20Check%20your%20connection%2C%20kindly%20suggest.%3C%2FP%3E%3CP%3Erest%20everything%20is%20working%20fine%20only%20for%20teams%20getting%20error%20Code%3A%20Request%20time%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-274288%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-274288%22%20slang%3D%22en-US%22%3E%3CP%3EMFA%20seems%20to%20break%20the%20update%20process%3F%20I%20signed%20out%20from%20Teams%20desktop%20app%20and%20after%20that%20the%20app%20realized%20need%20to%20authenticate%20again.%20Fixed%20the%20issue.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-222030%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222030%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20the%20only%20thing%20that%20worked%20for%20me%2C%20thank%20you%20for%20the%20information.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69946%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69946%22%20slang%3D%22en-US%22%3E%3CP%3EOn%202008%20R2%20I%20had%20to%20reinstall%20from%20the%20newest%20available%20version%201.0.00.13152%20from%20Microsoft%20and%20then%20it%20works.%20When%20trying%20to%20run%20the%20update%20from%20the%20previous%20version%20of%20the%20client%20I%20couldn't%20get%20it%20to%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69882%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69882%22%20slang%3D%22en-US%22%3E%3CP%3EI%20also%20confirm%2C%20installing%20the%20new%20release%20solved%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69830%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69830%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20confirm%20this%2C%20this%20has%20resolved%20our%20issues%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69692%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69692%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20latest%20update%20(%3CSPAN%3EMicrosoft%20Teams%20Version%201.0.00.13152%20(64-bit))%3C%2FSPAN%3E%26nbsp%3Binstalled%20today%20fixed%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69580%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69580%22%20slang%3D%22en-US%22%3E%3CP%3EUnfortunately%2C%20only%20one%2032%20bit%20system%20here%20and%20original%20folder%20got%20deleted%20before%20we%20found%20work%20around%20so%20we%20are%20unable%20to%20resolve%20at%20this%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69512%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69512%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20confirm%20workaround%20works%20for%20us.%20We%20manually%20distributed%20a%20working%20%22previous%22%20folder%20for%20affected%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20also%20raised%20issue%20with%20Microsoft%20through%20O365%20support.%20It%20has%20now%20been%20sent%20to%20%22back%20end%20engineers%22.%20Hopefully%20we%20will%20soon%20see%20a%20new%20update%20that%20resolve%20the%20issue.%20Fingers%20crossed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69508%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69508%22%20slang%3D%22en-US%22%3E%3CP%3EI%20tried%20downloading%20the%26nbsp%3Bprogram%20yesterday%20and%20now%20the%20error%20message%20regarding%20the%20glitch%20has%20been%20popping%20up%20on%20my%20screen...CONTINUALLY...every%205%20seconds...ever%20since.%26nbsp%3B%20I%20can't%20get%20it%20to%20stop.%26nbsp%3B%20I%20have%20since%20deleted%20the%20program%20from%20the%20computer.%26nbsp%3B%20I've%20tried%20deleting%20it%20from%20the%20task%20manager%20when%20it%20pops%20up%2C%20I've%20tried%20%22x-ing%22%20it%20out%20when%20it%20pops%20up%2C%20I've%20tried%20minimizing%20it%20-%20NOTHING%20stops%20it.%26nbsp%3B%20It's%20been%20over%2024%20hours.%26nbsp%3B%20It%20pops%20up%20over%20everything%20I'm%20using...even%20typing%20this%20message.%26nbsp%3B%20I'm%20about%20to%20lose%20my%20mind.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69355%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69355%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20been%20playing%20with%20this%20on%202008%20R2%20and%20found%20that%20if%20you%20edit%20the%20settings.json%20file%20and%20change%20the%20entries%26nbsp%3Bfor%26nbsp%3B%3C%2FP%3E%3CPRE%3E%22ignoreGpuBlacklist%22%3Afalse%3C%2FPRE%3E%3CP%3Eto%20true%20it%20will%20run%20once%2C%20but%20the%20app%20resets%20those%20values%20and%20it%20will%20crash%20the%20next%20time%20you%20try%20to%20run%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69229%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69229%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRIKE%3ESadly%20no%20previous%20folder%20in%20mine.%20%26nbsp%3BIt%20got%20removed%20in%20troubleshooting%20yesterday.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3EGot%20a%20copy%20of%20previous%20from%20an%20unaffected%20co-worker.%20%26nbsp%3BI'm%20back%20up.%20%26nbsp%3BThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69217%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69217%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20those%20users%20that%20still%20have%20the%20folder%20previous%20(You%20have%20the%20option%20to%20copy%20it%20from%20user%20to%20user)%2C%20it's%20a%20workaround%20to%20open%20the%20application.%3C%2FP%3E%3CP%3EIt's%20a%20way%20to%20force%20opening%20teams%20in%20the%20previous%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20change%20the%20shortcut%20to%20a%20user%20and%20so%20far%2C%20it's%20ok.%20(Again%2C%20important%20to%20point%20out%2C%20this%20way%20is%20using%20the%20version%20before%20the%20problem%20one)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69215%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69215%22%20slang%3D%22en-US%22%3EWorking%20on%202008%20R2%20for%20me%2C%20make%20sure%20your%20shortcut%20points%20to%20the%20%22previous%22%20folder.%20The%20version%20on%20that%20EXE%20for%20me%20is%201.0.00.7405%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69214%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69214%22%20slang%3D%22en-US%22%3E%3CP%3ETried%20the%20workaround%20to%20no%20avail.%20%26nbsp%3BThe%20update%20exe%20must%20have%20already%20updated.%20%26nbsp%3BTried%20to%20extract%20the%20original%20Teams.exe%20from%20the%20install%20package%20and%20running%20it%20from%20a%20shortcut%2C%20also%20to%20no%20avail.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69208%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69208%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20found%20a%20work%20around.%20The%20recent%20update%20is%20a%20problem.%20I%20expect%20the%20work-around%20will%20also%20become%20problematic.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20we%20have%20done%20is%20to%20create%20a%20shortcut%20to%3A%3C%2FP%3E%3CP%3Ec%3A%5Cusers%5Cusername%5Cappdata%5Clocal%5Cmicrosoft%5Cteams%5Cprevious%5Cteams.exe.%3C%2FP%3E%3CP%3E(change%20username%20to%20the%20current%20user's%20name)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20standard%20shortcut%20runs%20%22Update.exe%22%20each%20time%20Teams%20is%20launched.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVery%20best%20regards%2C%3C%2FP%3E%3CP%3EIver%20Nielsen%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69185%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69185%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20this%20happening%20on%20on%20Win7%2032bit%20machine.%20%26nbsp%3BWe%20have%20tried%20reinstalling%2C%20including%20blowing%20out%20the%20teams%20and%20Squirrel%20directories%20then%20rebooting%20and%20downloading%20a%20fresh%20installer.%20%26nbsp%3BThe%20problem%20is%20still%20happening.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69165%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69165%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20problem%20here...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69157%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69157%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20also%20getting%20the%20same%20issue%20from%20a%20couple%20of%20days%2C%3C%2FP%3E%3CP%3EUninstalling%20and%20reinstalling%20doesn't%20help%2C%20I'm%20using%20this%20on%20a%20machine%20which%20is%20Remotely%20connected(Remote%20Desktop%20Connection).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEsh%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69125%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69125%22%20slang%3D%22en-US%22%3E%3CP%3EOurs%20are%20almost%20all%20virtual%20desktops%2C%20same%20build%20on%20vanilla%20Win10%20is%20working%20fine.%20Logs%20are%20off%20to%20the%20engineering%20teams%20and%20hope%20to%20hear%20more%20back%20US%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69123%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69123%22%20slang%3D%22en-US%22%3EInteresting%2C%20our%20few%20affected%20machines%20are%20all%20regular%20desktops.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69121%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69121%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20thing%20happening%20here%20too.%20For%20non%20virtualised%20desktops%20it%20is%20fine%2C%20but%20everyone%20else%20using%20Xendesktop%20suffers%20from%20that%20issue%20since%20yesterday.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69115%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69115%22%20slang%3D%22en-US%22%3EWe%20just%20rolled%20out%20teams%20across%20our%20network.%20Same%20issue%20with%20us%20on%20two%20PCs.%20Hope%20Microsoft%20will%20fix%20the%20desktop%20clients%20at%20the%20earliest.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69042%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69042%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20the%20same%20issue%2C%20I've%20raised%20a%20case%20with%20support%20teams%2C%20so%20I'll%20let%20you%20know%20how%20we%20go.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68957%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68957%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20also%20having%20users%20on%20Surface%20Pro%204%20Win10%20with%20the%20same%20issue.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68890%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68890%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20problem%20out%20of%20the%20blue.%20%26nbsp%3BWindows%207%20Enterprise%2C%2064%20bit%20running%20in%20a%20VMware%20VM.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68887%22%20slang%3D%22en-US%22%3ERE%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68887%22%20slang%3D%22en-US%22%3ESame%20here%2C%20happening%20on%20my%20Windows%207%20VDI%20desktop.%20My%20installation%20on%20Windows%2010%20seems%20to%20be%20working%20fine.%20Others%20at%20my%20company%20having%20trouble%20running%20Microsoft%20Teams%20in%20Windows%207%20on%20our%20VDI%20as%20well%20in%20the%20last%20couple%20of%20days.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68842%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68842%22%20slang%3D%22en-US%22%3EAppData%5CRoaming%5CMicrosoft%5CTeams%5Clogs.txt%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68838%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68838%22%20slang%3D%22en-US%22%3ESeeing%20the%20same%20in%20our%20virtual%20desktop%20environment%20(Windows%207%2064%20bit).%20Was%20working%20fine%20until%20a%20recent%20update%20and%20new%20installs%20also%20fail.%3CBR%20%2F%3E%3CBR%20%2F%3EWhere%20did%20find%20the%20log%20with%20that%20GPU%20error%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68834%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68834%22%20slang%3D%22en-US%22%3E%3CP%3EYep%2C%20I%20did%20the%20same%20and%20had%20the%20same%20problem...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlready%20investigate%20and%20didn't%20find%20any%20documentation%20about%20auto-update%20process%20and%20how%20to%20stop%20if%20exists.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68830%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68830%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20to%20uninstall%20the%20desktop%20app%20to%20get%20it%20to%20stop%20looping%20through%20the%20restart.%26nbsp%3B%20Was%20very%20annoying.%26nbsp%3B%20Couldn't%20kill%20it%20from%20Task%20Manager%20(threw%20an%20error%20message%20when%20I%20tried).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68829%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68829%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20has%20started%20glitching%20again%2C%20I%20think%20it%20may%20be%20updating%20itself%20as%20I%20had%20installed%20an%20older%20copy%20of%20the%20installer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68819%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68819%22%20slang%3D%22en-US%22%3ENot%20yet....I%20will%20post%20again%20if%20it%20comes%20back.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68817%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68817%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20James%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20the%20same%20environment%2C%202008%20R2%20in%20Terminal%20Server%2C%20and%20re-installing%20solved%20it%20for%20some%20minutes%2C%20but%20then%20started%20to%20glitched%20again...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20didn't%20have%20anymore%20issues%20after%20that%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68814%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68814%22%20slang%3D%22en-US%22%3EWe%20tested%20uninstalling%20and%20reinstalling%20Teams%20with%20freshly%20downloaded%20installer%20file%2C%20but%20to%20no%20avail.%3CBR%20%2F%3E%3CBR%20%2F%3EWindows%207%20pro%20-%2064bit%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68806%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68806%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20the%20same%20problem%20on%20a%202008%20R2%20Remote%20Desktop%20environment.%20I%20just%20tried%20re-running%20the%20installer%20and%20that%20seemed%20to%20get%20it%20working.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68791%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68791%22%20slang%3D%22en-US%22%3E%3CP%3EI%20to%20am%20having%20this%20issue!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68739%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68739%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20users%20expericiencing%20the%20same%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20error%20is%20related%20to%20GPU%20Crash.%20Already%20sent%20an%20e-mail%20to%20'microsoftteamsdev%40microsoft.com'%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%3CI%3EWed%20May%2010%202017%2011%3A01%3A38%20GMT%2B0100%20(GMT%20Daylight%20Time)%20%26lt%3B23280%26gt%3B%20--%20error%20--%20GPU%20process%20crashed%2C%20restarting%20the%20app.%20%3C%2FI%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CI%3EWed%20May%2010%202017%2011%3A01%3A38%20GMT%2B0100%20(GMT%20Daylight%20Time)%20%26lt%3B23280%26gt%3B%20--%20info%20--%20Saved%20renderer%20crash%20info%20%3C%2FI%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CI%3EWed%20May%2010%202017%2011%3A01%3A38%20GMT%2B0100%20(GMT%20Daylight%20Time)%20%26lt%3B23280%26gt%3B%20--%20info%20--%20Set%20restartReason%20state.%20%3C%2FI%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CI%3EWed%20May%2010%202017%2011%3A01%3A38%20GMT%2B0100%20(GMT%20Daylight%20Time)%20%26lt%3B23280%26gt%3B%20--%20info%20--%20Restarting%20app%20Teams%20with%20reason%20crash%20%3C%2FI%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWaiting%20for%20feedback.%20So%20far%20no%20one%20is%20using%20Teams!...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68710%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68710%22%20slang%3D%22en-US%22%3E%3CP%3EAdding%20screenshot%20of%20error%20message.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20902px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F14378i4E8B5D97A456A121%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Teams_20170510.png%22%20title%3D%22Teams_20170510.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68701%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68701%22%20slang%3D%22en-US%22%3EI'm%20adding%20me%20to%20this%20topic.%20I%20have%20users%20reporting%20this%20today.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1022832%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1022832%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54820%22%20target%3D%22_blank%22%3E%40Johan%20Borg%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20was%20this%20fixed%3F%20I%20am%20now%20having%20the%20exact%20same%20issue%20after%20updates%20ran.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1023530%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1023530%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F463719%22%20target%3D%22_blank%22%3E%40lesafrawley%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20used%20the%20%22run%20Teams%20in%20Update%20folder%22%20workaround%20for%26nbsp%3B%20about%20a%20week%2C%20then%20MS%20released%20a%20new%20version%20that%20fixed%20the%20issue%20for%20us.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3EJohan%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1537960%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20at%20startup%3A%20There%20was%20a%20glitch%20and%20we're%20recovering...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1537960%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20am%20same%20problem%20facing...%3C%2FP%3E%3CP%3EGave%20error%20message%20%22There%20was%20a%20glitch%20and%20we're%20recovering...%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWindows%207%20pro.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

 

Some of our users reported problems starting the Teams desktop client today.

Problem came out of the blue, has worked before.

 

Gave error message "There was a glitch and we're recovering..."

 

Any ideas?

 

Best regards,

Johan

43 Replies
Highlighted
I'm adding me to this topic. I have users reporting this today.
Highlighted

Adding screenshot of error message.

 

Teams_20170510.png

Highlighted

I have users expericiencing the same issue.

 

The error is related to GPU Crash. Already sent an e-mail to 'microsoftteamsdev@microsoft.com'

 

Wed May 10 2017 11:01:38 GMT+0100 (GMT Daylight Time) <23280> -- error -- GPU process crashed, restarting the app.

Wed May 10 2017 11:01:38 GMT+0100 (GMT Daylight Time) <23280> -- info -- Saved renderer crash info

Wed May 10 2017 11:01:38 GMT+0100 (GMT Daylight Time) <23280> -- info -- Set restartReason state.

Wed May 10 2017 11:01:38 GMT+0100 (GMT Daylight Time) <23280> -- info -- Restarting app Teams with reason crash

 

Waiting for feedback. So far no one is using Teams!...

Highlighted

I to am having this issue!!

Highlighted

I'm having the same problem on a 2008 R2 Remote Desktop environment. I just tried re-running the installer and that seemed to get it working.

Highlighted
We tested uninstalling and reinstalling Teams with freshly downloaded installer file, but to no avail.

Windows 7 pro - 64bit
Highlighted

Hi James,

 

I have the same environment, 2008 R2 in Terminal Server, and re-installing solved it for some minutes, but then started to glitched again...

 

You didn't have anymore issues after that?

 

Cheers

Highlighted
Not yet....I will post again if it comes back.
Highlighted

It has started glitching again, I think it may be updating itself as I had installed an older copy of the installer.

Highlighted

I had to uninstall the desktop app to get it to stop looping through the restart.  Was very annoying.  Couldn't kill it from Task Manager (threw an error message when I tried).

Highlighted

Yep, I did the same and had the same problem...

 

Already investigate and didn't find any documentation about auto-update process and how to stop if exists.

Highlighted
Seeing the same in our virtual desktop environment (Windows 7 64 bit). Was working fine until a recent update and new installs also fail.

Where did find the log with that GPU error?
Highlighted
AppData\Roaming\Microsoft\Teams\logs.txt
Highlighted
Same here, happening on my Windows 7 VDI desktop. My installation on Windows 10 seems to be working fine. Others at my company having trouble running Microsoft Teams in Windows 7 on our VDI as well in the last couple of days.
Highlighted

Same problem out of the blue.  Windows 7 Enterprise, 64 bit running in a VMware VM.

Highlighted

We are also having users on Surface Pro 4 Win10 with the same issue. 

Highlighted

We have the same issue, I've raised a case with support teams, so I'll let you know how we go.

Highlighted
We just rolled out teams across our network. Same issue with us on two PCs. Hope Microsoft will fix the desktop clients at the earliest.
Highlighted

Same thing happening here too. For non virtualised desktops it is fine, but everyone else using Xendesktop suffers from that issue since yesterday.