Home

Teams keeping files locked after closing

%3CLINGO-SUB%20id%3D%22lingo-sub-186836%22%20slang%3D%22en-US%22%3ETeams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186836%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20testing%20files%20in%20Teams.%26nbsp%3B%20It%20appears%20it's%20keeping%20files%20locked%20open%20after%20they're%20closed%20in%20Teams.%26nbsp%3B%20For%20example%20-%20edit%20a%20file%20in%20the%20Teams%20window%2C%20close%20it%2C%20then%20go%20try%20to%20delete%20the%20file%205%20minutes%20later%20on%20the%20SP%20side%2C%20it%20says%20it's%20locked%20for%20editing.%26nbsp%3B%20Has%20anyone%20else%20experienced%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-186836%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393742%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393742%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20also%20going%20through%20the%20same%20issue.%20I%20could%20edit%20a%20docx%20in%20Teams%2C%20but%20could%20not%20delete%20even%20after%204%20hrs%20since%20making%20the%20change.%20Just%20do%20not%20know%20what%20to%20do.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3EKrishna%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-347093%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-347093%22%20slang%3D%22en-US%22%3E%3CP%3Ewhere%20is%20%22office%20upload%20center%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325472%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325472%22%20slang%3D%22en-US%22%3E%3CP%3ESolution%3A%3C%2FP%3E%3CP%3E1.%20Go%20to%20'Office%20Upload%20Center'%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CBR%20%2F%3E2.%20Settings%20-%26gt%3B%20Delete%20cached%20files%3CSPAN%3E%26nbsp%3B(I%20checked%20the%20box%20for%20%22Delete%20files%20from%20the%20Office%20Doc..%20etc%22%20too%2C%20idk%20if%20that's%20a%20must)%3C%2FSPAN%3E%3CBR%20%2F%3E3.%20Logout%20of%20Microsoft%20Teams%20then%20login%20again%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CBR%20%2F%3E4.%20Check%20if%20you%20can%20delete%2C%20move%2C%20rename%20etc%20some%20files.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20it's%20not%20helping%2C%20i%20suggest%20a%20temporary%20workaround%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EOpen%20the%20file%20in%20SharePoint%20-%26gt%3B%20select%20it%20from%20the%20list%20-%26gt%3B%20Show%20Actions%20-%26gt%3B%20More%20-%26gt%3B%20Check%20out%20-%26gt%3B%20Checking%20Out%20is%20Done%20-%26gt%3B%20Try%20Delete%2FMove%20to%2FRename.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325032%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325032%22%20slang%3D%22en-US%22%3E%3CP%3EMe%20too%2C%20I%20hate%20spending%20time%20to%20clearify%20things%20twice%20and%20tell%20people%20over%20and%20over%20again%20what%C2%B4s%20happening%2C%20but%20in%20the%20end%20if%20the%20issue%20is%20such%20a%20big%20one%20for%20you%20and%20I%20understand%20it%20is%2C%20the%20effort%20is%20worth%20it%2C%20I%20promise.%20I%20just%20like%20to%20encourage%20you%20to%20keep%20on%20%3B).%20Keep%20us%20posted%20!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324239%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324239%22%20slang%3D%22en-US%22%3E%3CP%3EI%20will%20open%20a%20ticket%2C%20but%20I%20admit%20that%20doing%20so%20is%20not%20something%20I%20like.%3C%2FP%3E%3CP%3EMy%20experience%26nbsp%3Bwith%20support%20is%20that%20I%20need%20to%20spend%20a%20lot%20of%20time%20to%20make%20them%20understand%20the%26nbsp%3Bproblem%2C%20and%20takes%20me%20a%20lot%20of%20hours%20of%20talking%20and%20corresponding%20before%20anyone%20with%20competence%26nbsp%3Bcan%20solve%20the%20case.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOffice%20build%201808%20does%20not%20solve%20the%20case.%20This%20is%20probably%20a%20Teams%20related%26nbsp%3Bissue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENegative%20thoughts%20aside%2C%20I%20will%20create%20a%20support%20case.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-321531%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-321531%22%20slang%3D%22en-US%22%3E%3CP%3E%40per%20ove%20Did%20you%20open%20a%20call%20at%20Microsoft.%20I%20would%20suggest%20that%20while%20other%20useres%20reported%20that%20their%20problem%20got%20solved%20by%201808.%20Please%20keep%20us%20posted%20because%20you%20are%20right%20it%20is%20crucial%20that%20this%20things%20are%20working!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-321526%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-321526%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20This%20is%20still%20a%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20a%20consultant%20working%20for%20a%20client.%20They%20are%20starting%20to%20use%20Teams%20extensively.%3C%2FP%3E%3CP%3EI%20have%20upgraded%20to%20Office%201808.%3C%2FP%3E%3CP%3EI%20have%20set%20the%20web%20client%20setting%20to%20not%20lock%20files.%3C%2FP%3E%3CP%3EI%20have%20empties%20Office%20upload%20center%20cache%2C%20and%20set%20it%20to%20delete%20the%20cache%20after%20file%20is%20closed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%20the%20following%20happens%3A%3C%2FP%3E%3CP%3EIn%20teams%20I%20open%20the%20files%20tab.%3C%2FP%3E%3CP%3EI%20add%20a%20word%20file.%3C%2FP%3E%3CP%3EI%20edit%20the%20file%20in%20Teams.%3C%2FP%3E%3CP%3EThen%20I%20close%20the%20file.%3C%2FP%3E%3CP%3EThen%20I%20select%20the%20file%20and%20try%20to%20delete%20it.%3C%2FP%3E%3CP%3EThen%20I%20get%20the%20error%20message%3A%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%22Sorry%20we%20ran%20into%20a%20problem.%20The%20file%20filename.docs%22%20is%20locked%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20use%20only%20Microsoft%20Teams.%20No%20local%20Office%20and%26nbsp%3Bno%20Office%20online.%3C%2FP%3E%3CP%3ENo%20other%20people%20are%20using%20the%20file.%3C%2FP%3E%3CP%3EThis%20happens%20both%20in%20Onedrive%20synced%20Libraries%20and%20not%20synced%20libraries.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20terrible!%20And%20people%20are%20very%20annoyed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20to%20tell%20people%20to%20not%20use%20Teams.%3C%2FP%3E%3CP%3EWe%20need%20to%20sync%20all%20Teams%20Files%20(from%20SharePoint)%20and%20use%20local%20Office%20to%20edit%20and%20save%20files.%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20works%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20a%20very%20serious%20problem.%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20there%20is%20no%20help.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298121%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298121%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20folks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F13364%22%20target%3D%22_blank%22%3E%40David%20Phillips%3C%2FA%3E%2C%20is%20your%20Problem%20solved%20also%3F%20I%20read%20the%20whole%20post%20history%20today%20and%20I%20am%20wondering%20if%20your%20Problem%20is%20also%20solved%3F!%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3CP%3EAndre%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292012%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292012%22%20slang%3D%22en-US%22%3EThanks%20Andre.%20Version%201808%20corrected%20the%20issue%20for%20us%20as%20well.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292002%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292002%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20this%20issue%20as%20well%2C%20created%20a%20document%20in%20Teams%20and%20then%20when%20I%20try%20and%20delete%20it%20I%20can't.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286218%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286218%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20seeing%20the%20same%20thing%2C%20frustrating%20this%20type%20of%20an%20issue%20is%20still%20happening%20even%20with%20the%20co-authoring%20update%20to%20semi-annual%20channel.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20dug%20into%20the%20monthly%20channel%20for%20our%20company%20pretty%20deep%2C%20and%20it%20isn't%20that%20it%20isn't%20for%20business%20-%20it%20is%20about%20the%20update%20frequency.%26nbsp%3B%20Monthly%20channel%20is%20what%20the%20consumer%20base%20of%20the%20world%20that%20has%20office%20click%20to%20run%20is%20on%20and%20is%20a%20great%20test%20bed%20(millions%20of%20users)%20before%20those%20changes%20get%20rolled%20into%20semi-annual%20targeted%2C%20then%20into%20semi-annual.%26nbsp%3B%20The%20update%20frequency%20of%20monthly%20updates%20may%20be%202%20or%20more%20updates%20in%20a%20single%20month.%26nbsp%3B%20Where%20the%20updates%20to%20semi-annual%20are%20very%20predictable%20and%20only%20happen%20every%206%20months.%26nbsp%3B%20Personally%20I%20am%20struggling%20with%20the%20need%20to%20wait%206%20months%20before%20the%20goodness%20of%20monthly%20channel%20updates%20come%20out%20(focused%20inbox%2C%20co-authoring%2C%20some%20stability%20items%20in%20office%20apps%20etc..)%26nbsp%3B%20true%20it%20is%20nice%20to%20have%20a%206%20month%20runway%20for%20change%2C%20but%20sometimes%20the%20benefit%20of%20smaller%20%2F%20more%20frequent%20updates%20that%20give%20functionality%20and%20stability%20may%20be%20worth%20the%20end%20user%20experience%20impact%20of%20multiple%20updates%20a%20month.%26nbsp%3B%20We%20actually%20moved%20to%202x%20month%20windows%20patching%20due%20to%20the%20frequency%20of%20patches%20and%20the%20desire%20we%20had%20to%20reduce%20the%20time%20it%20took%20to%20patch%20(2x%2010-15%20minutes%20vs%201x%20a%20month%20of%2020%20plus%20minutes%20of%20downtime)%20was%20worth%20it..%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20some%20food%20for%20thought..%26nbsp%3B%20I%20would%20really%20be%20interested%20in%20any%20updates%20that%20any%20of%20you%20get%20on%20the%20locking%20issue%20as%20it%20carries%20a%20significant%20impact%20for%20us%20as%20I%20am%20sure%20it%20is%20for%20everyone!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJason%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285194%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285194%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Ted%2C%20we%20now%20use%20the%20Version%26nbsp%3B1808%20(Build%2010730.20155%20Click-to-run).%20I%20hope%20it%20helps.%20I%20am%20not%20fully%20sure%20if%20it%20helped%20our%20whole%20Organisation.%20I%20will%20follow%20up%20it%20in%20a%20few%20days%20internally.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%20Andre%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282633%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282633%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20we%20have%20this%20same%20issue.%26nbsp%3B%20Open%20the%20file%20from%20MS%20Teams%2C%20make%20one%20small%20edit%2C%20close%20it.%26nbsp%3B%20Then%20Open%20this%20file%20in%20Excel%20(client%20app).%26nbsp%3B%20It%20is%20set%20to%20read-only%2C%20in%20the%20yellow%20information%20bar%20click%20Edit%20Workbook.%26nbsp%3B%20The%20%22File%20In%20Use%22%20popup%20displays.%20(1)%20View%20a%20read-only%20copy%20(2)%20Save%20and%20edit%20a%20copy%20of%20the%20file%20(3)%20Receive%20a%20notification%20when%20the%20server%20file%20is%20available.%26nbsp%3B%20--%20None%20of%20these%20work%20for%20me.%3C%2FP%3E%3CP%3EI%20go%20get%20a%20coffee%20and%20(about%205%20minutes)%20then%20click%20Edit%20Workbook%20again%20then%20sometimes%20it%20works.%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20team%20is%20opening%20a%20ticket%20with%20Microsoft.%26nbsp%3B%20I%20will%20update%20this%20post%20once%20I%20have%20a%20solution%20or%20work-around.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282342%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282342%22%20slang%3D%22en-US%22%3E%3CP%3EAndre%2C%20would%20you%20mind%20sharing%20the%20O365%20build%20you%20are%20on%20that%20fixed%20this%20issue%20for%20you%3F%26nbsp%3B%20%26nbsp%3B%20We%20are%20on%20semi-annual%20and%20still%20running%2016.0.9126.xxxx%20and%20have%20this%20issue%20still.%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278836%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278836%22%20slang%3D%22en-US%22%3EThere%20is%20no%20File%20-%26gt%3B%20Close%20these%20days%20in%20the%20online%20versions%20of%20Office.%20If%20Microsoft%20would%20have%20left%20that%20button%20I%20would%20gladly%20use%20it.%20In%20the%20meantime%2C%20the%20amount%20of%20times%20I%20find%20myself%20locked%20out%20of%20renaming%20my%20own%20files%20is%20just%20crazy.%20That%20is%20THE%20ONE%20reason%20I%20steer%20away%20from%20Teams%2FSharePoint.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-270393%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-270393%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88972%22%20target%3D%22_blank%22%3E%40Andre%20Radtke%3C%2FA%3E%26nbsp%3Bwould%20you%20mind%20sharing%20that%20MS%20case%20number%3F%26nbsp%3B%20I%20may%20open%20a%20case%20as%20well%20if%20we%20can't%20figure%20this%20one%20out%20on%20our%20own.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-260263%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-260263%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20still%20a%20problem%20mid-September%202018.%26nbsp%3B%20Any%20updates%20on%20when%20a%20fix%20will%20be%20pushed%20to%20customers%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252210%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252210%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20indeed%2C%20I%20am%20with%20you.%20Personally%20I%20am%20more%20a%20sharepoint%20%2F%20Onedrive%20%2F%20Teams%20guy%20than%20a%20client-OS%20guy%20and%20I%20learned%20a%20lot%20within%20this%20issue%20%3B)%3C%2Fimg%3E%20.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252209%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252209%22%20slang%3D%22en-US%22%3E%3CP%3EI%C2%B4m%20very%20glad%20to%20hear!!%20Learning%20something%20is%20awsome%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252207%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252207%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20already%20helped%20with%20one%20client.%20We%20already%20moved%20just%20one%20client%20to%20test%20the%20solution%20proposal.%20With%20the%20newest%20Office%20Update%20the%20problem%20has%20been%20blown%20away%20instantly.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252202%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252202%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20everyone%20can%20make%20mistakes%20%3A)%3C%2Fimg%3E%20I%20doubt%20switching%20to%20monthly%20channel%20will%20help%20though..please%20let%20me%20know%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252197%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252197%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Esecretly%20I%20know%20that%20co-authoring%20also%20works%20in%20the%20business%20environment.%20But%20if%20Microsoft%20Support%20tells%20me%20that%20I%20have%20to%20switch%20from%20semi%20annual%20over%20to%20monthly%20and%20that%20this%20more%20for%20consumer%20customers%20(I%20know%20it%C2%B4s%20also%20for%20business)%20then%20I%20am%20wondering......%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20just%20spoke%20to%20a%20colleague%26nbsp%3Bwith%20a%20little%20bit%20more%20background%20information%20and%20he%20also%20confirmed%20me%20now%20that%20monthly%20is%20also%20for%20business%20customers.%20Therefore%20someone%20in%20our%20organisation%20has%20to%20decide%20if%20we%20switch%20to%20monthly%20or%20not%20%3B).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EBut%20I%20am%20still%20wondering%20why%20Microsoft%20Support%20ist%20telling%20me%20such%20things.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252189%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252189%22%20slang%3D%22en-US%22%3E%3CP%3EHi!%20Thank%20you!%20Seems%20like%20a%20strange%20answer%20from%20MS%20though%20%3A%5C%3C%2Fimg%3E%20Also%20Co-authoring%20is%20available%20for%20business%20costumers%20aswell..This%20problem%20is%20outside%20the%20scope%20of%20co-authoring%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252187%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252187%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20an%20update.%20I%20opened%20a%20Microsoft%20call%20and%20we%20got%20an%20answer%20very%20fast.%20Microsoft%20is%20aware%20of%20this%20Problem.%20The%20short%20solution%20with%20one%20Client%20is%20to%20place%20him%20to%20the%20monthly%20update%20channel.%20This%20is%20not%20an%20option%20in%20our%20business%20environment%2C%20because%20the%20monthly%20update%20channel%20is%20just%20for%20consumer%20customers%20(as%20the%20informed%20me).%20I%20hope%20some%20of%20you%20will%20help%20this!%20Information!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EW%3C%2FSTRONG%3Ehat%20I%20want%20to%20know%20is%20if%20Microsoft%20is%20willing%20to%20fix%20this.%20Co-Authoring%20IMHO%20is%20a%20killerfeature%20and%20must%20also%20be%20available%20for%20business%20customers.%20Pleas%20give%20me%20information%20if%20and%20if%20yes%2C%20when%20it%20will%20be%20available%20for%20business%20customers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreetings%20Andre%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-250876%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-250876%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20do%20have%20the%20same%20Issue.%20Did%20anybody%20get%20Response%20to%20that%20from%20Microsoft%20due%20to%20a%20call%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-250854%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-250854%22%20slang%3D%22en-US%22%3EI%20can%20give%20you%20two%20suggestions%20but%20I%20do%20think%20what%20you%20are%20referring%20to%20likely%20to%20be%20a%20bug.%20We%20are%20opening%20a%20ticket%20with%20MSFT%20today%2C%20but%20others%20have%20already%20opened%20tickets%20about%20this%20and%20I%20am%20not%20sure%20where%20it%20went.%20Your%20idea%20of%20creating%20the%20docs%20outside%20of%20Teams%2C%20then%20uploading%20is%20the%20safest%20idea%20I%20am%20using%20at%20the%20moment.%20Here%20are%20my%20other%20ideas%20for%20you%20to%20try%3A%3CBR%20%2F%3E%3CBR%20%2F%3E1.%20Clear%20the%20Office%20cache%20on%20your%20computer.%20The%20directory%20should%20be%20something%20like%20C%3A%5CUsers%5CYOURNAME%5CAppData%5CLocal%5CMicrosoft%5C16.0%5COfficeFileCache.%20Delete%20all%20of%20the%20files%20that%20begin%20with%20FSD%20%26amp%3B%20FSF.%3CBR%20%2F%3E%3CBR%20%2F%3E2.%20Click%20your%20Windows%20key%2C%20type%20%22Office%20Upload%20Center%22%20then%20Settings%20--%26gt%3B%20Delete%20Cached%20Files%3CBR%20%2F%3E%3CBR%20%2F%3EAnother%20last%20resort%20would%20be%20to%20change%20registry%20setting%20for%20file%20locking%20(unfortunately%20I%20can't%20find%20the%20article%20for%20that%20at%20the%20moment).%20The%20only%20thing%20about%20this%20is%20that%20I%20am%20not%20sure%20if%20doing%20this%20actually%20disables%20your%20ability%20to%20check-in%2Fcheck%20out%20documents%20or%20not.%20You%20would%20have%20to%20test%20that.%3CBR%20%2F%3E%3CBR%20%2F%3EMatthew%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-250851%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-250851%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20found%20or%20heard%20of%20ways%20around%20this%3F%20It%20make%20it%20difficult%20to%20use%20TEAMs%20effectively%20when%20creating%20new%20files%20in%20the%20TEAMs%20location%20you%20want%20them%20and%20then%20trying%20to%20edit%20them%20and%20having%20to%20wait.%20For%20example%20just%20trying%20to%20create%20a%20new%20Excel%20file%20then%20when%20you%20open%20it%2C%20it%20says%20it's%20locked%20and%20doesn't%20ever%20seem%20to%20notify%20you%20when%20it's%20freed%20up.%20I've%20reverted%20back%20to%20creating%20the%20file%20and%20saving%20it%20outside%20of%20TEAMs%2C%20editing%20it%20then%20just%20coping%20it%20up%20to%20TEAMs.%20Bit%20of%20a%20band-aid%20for%20now%20and%20would%20really%20like%20to%20know%20when%20this%20will%20be%20addressed.%3C%2FP%3E%3CP%3ESimilar%20issue%20when%20creating%20WORD%20documents.%20I%20created%20some%20in%20TEAMs%20and%20realized%20I%20put%20them%20in%20the%20wrong%20folder.%20Since%20they%20were%20locked%20I%20couldn't%20move%20them%20or%20delete%20them.%20TEAMs%20says%20it%20does%20it%20but%20the%20file%20just%20stays%20there.%20When%20opening%20up%20the%20SP%20site%20is%20only%20when%20you%20actually%20get%20an%20error.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-240854%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240854%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20could%20be%20a%20similar%20issue%20to%20Office365%20documents%20in%20SharePoint%20getting%20locked.%20The%20issue%20there%20is%20that%20sometimes%20people%20will%20close%20files%20by%20clicking%20the%20red%20X%20in%20the%20top-right%20corner.%20The%20fix%20is%20always%20to%20open%20the%20file%20and%20close%20it%20again%20by%20clicking%20%22File%20-%26gt%3B%20Close%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-186928%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186928%22%20slang%3D%22en-US%22%3EYeah%2C%20with%20their%20file%20UI%20updates%20coming%20to%20match%20SharePoint%20online%2C%20I%20really%20hope%20they%20look%20at%20just%20integrating%20directly%20into%20Teams%20opening%20in%20Office%20Online%20and%20just%20bypassing%20the%20whole%20separate%20Teams%20integration%20part.%20I%20think%20they%20do%20this%20because%20of%20the%20conversations%20on%20the%20right%2C%20but%20you%20can%20still%20have%20those%20when%20views%20website%20%2F%20office%20files%20using%20tabs%2C%20so%20should%20just%20be%20a%20similar%20experience.%20Having%20Teams%20edit%2C%20but%20then%20an%20option%20to%20edit%20in%20word%20online%2C%20etc%20is%20kind%20of%20redundant%20when%20they%20really%20kind%20of%20are%20the%20same%20thing.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-186926%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186926%22%20slang%3D%22en-US%22%3E%3CP%3EI%20hope%20that%20can%20be%20addressed.%26nbsp%3B%20While%20it%20might%20make%20sense%20to%20us%20as%20tech%20people%2C%20that%20will%20drive%20users%20nuts.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-186916%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186916%22%20slang%3D%22en-US%22%3EWhat%20I%20think%20is%20happening%20is%20the%20way%20Teams%20caches%20files%20when%20you%20open%20it%20in%20Teams%20it's%20still%20keeping%20it%20open%20when%20you%20close%20it%20out.%20Also%20even%20when%20editing%20with%20excel%20online%20sometimes%20it%20won't%20gracefully%20exit%20and%20the%20lock%20will%20always%20stay%20on%20the%20file%20for%205-10%20mintues%20so%20you%20cannot%20do%20things%20like%20delete%2Fedit%20file%20name%20etc.%20but%20you%20can%20open%20it%20again%20in%20Teams%20or%20Office%20online%2F%20Current%20Office%20clients%20for%20co-authoring.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-186866%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186866%22%20slang%3D%22en-US%22%3E%3CP%3EI%20found%20this%20article%20about%20changing%20a%20registry%20setting%26nbsp%3Bfor%20the%20web%20client%20service%20but%20am%20unsure%20if%20it%20would%20have%20impact%20beyond%20Teams.%20Feel%20free%20to%20investigate%20this%3A%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FFile-locking-issue%2Ftd-p%2F71185%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FFile-locking-issue%2Ftd-p%2F71185%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-186855%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186855%22%20slang%3D%22en-US%22%3E%3CP%3ESortof.%26nbsp%3B%20What%20I%20found%20is%20if%20you%20open%20the%20file%20in%20Teams%2C%20then%20close%20it%2C%20but%20leave%20Teams%20open%2C%20when%20you%20try%20to%20open%20the%20file%20in%20Excel%20from%20the%20SP%2C%20you%20get%20the%20locked%20dialog%2C%20and%20you're%20prompted%20to%20read%20only%20or%20save%20as%20a%20different%20file%20name.%26nbsp%3B%20I%20also%20noticed%20that%20if%20you%20open%20it%20later%20in%20Teams%2C%20and%20try%20to%20edit%20with%20Excel.%20it%20says%20it's%20locked%20open.%26nbsp%3B%20Seems%20a%20bit%20random%20too.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-186853%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186853%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20also%20having%20an%20issue%20with%20users%20not%20being%20able%20to%20save%20a%20file%20in%20the%20%22Files%22%20tab%20and%20they%20have%20to%20save%20it%20with%20another%20name%20or%20save%20it%20locally%20to%20not%20lose%20their%20work%3F%20I%20noticed%20the%20problem%20in%20different%20tenants%20occasionally%20happening%20over%20the%20past%20couple%20of%20months%20but%20at%20my%20current%20project%20I%20am%20noticing%20it%20starting%20to%20happen%20too%20often.%20I%20am%20still%20researching%20it%20myself.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-414607%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-414607%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20experience%20the%20same%20thing%20-%20after%20editiding%20a%20file%20and%20closing%20it%20in%20teams%26nbsp%3B%20-%20when%20someone%20else%20tries%20to%20open%20the%20file%20to%20continue%20working%20with%20it%20they%20get%20a%20message%20that%20the%20file%20is%20locked%20for%20editing%20by%20the%20last%20user%20of%20the%20file.%20This%20seems%20sporadic%20-%20we%20have%20not%20yet%20found%20out%20when%20this%20occurs%20or%20why.%20Just%20happens%20occationally%2C%20seems%20random(although%20it's%20probably%20not%3F)%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F13364%22%20target%3D%22_blank%22%3E%40David%20Phillips%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-485354%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-485354%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F61931%22%20target%3D%22_blank%22%3E%40Matthew%20J.%20Bailey%3C%2FA%3E%26nbsp%3Boption%202%20seems%20to%20be%20working%20as%20a%20temporary%20solution%20for%20me%20at%20the%20moment%2C%20thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-505527%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-505527%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F313296%22%20target%3D%22_blank%22%3E%40KrishnaRajagop%3C%2FA%3ENone%20of%20previous%20workaround%20worked%20for%20me.%3C%2FP%3E%3CP%3EOnly%20thing%20that%20worked%20was%3A%3C%2FP%3E%3CP%3E1.-%20Sign%20out%20Teams%20and%20restart%3C%2FP%3E%3CP%3E2.-%20Wait%201-2%20minutes%20and%20try%20again.%3C%2FP%3E%3CP%3E3.-%20Move%2C%20Delete%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-514588%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-514588%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20worked%20for%20a%20couple%20of%20my%20clients.%20Thanks!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%3E1.%20Go%20to%20'Office%20Upload%20Center'%20%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E2.%20Settings%20-%26gt%3B%20Delete%20cached%20files%20(I%20checked%20the%20box%20for%20%22Delete%20files%20from%20the%20Office%20Doc..%20etc%22%20too%2C%20idk%20if%20that's%20a%20must)3.%20Logout%20of%20Microsoft%20Teams%20then%20login%20again%20%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E4.%20Check%20if%20you%20can%20delete%2C%20move%2C%20rename%20etc%20some%20files.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EIf%20it's%20not%20helping%2C%20i%20suggest%20a%20temporary%20workaround%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EOpen%20the%20file%20in%20SharePoint%20-%26gt%3B%20select%20it%20from%20the%20list%20-%26gt%3B%20Show%20Actions%20-%26gt%3B%20More%20-%26gt%3B%20Check%20out%20-%26gt%3B%20Checking%20Out%20is%20Done%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-858036%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-858036%22%20slang%3D%22en-US%22%3E%3CP%3EI%20believe%20I%20solved%20the%20problem.%20I%20looked%20at%20the%20%22Conversations%22%20tab%20and%20noticed%20the%20file%20I%20started%2Fuploaded%20ended%20up%20there.%20Once%20I%20deleted%20the%20message%2C%20I%20was%20able%20to%20delete%2Fedit%20the%20file%20on%20the%20%22Files%22%20tab.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F13364%22%20target%3D%22_blank%22%3E%40David%20Phillips%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-904363%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-904363%22%20slang%3D%22en-US%22%3E%3CP%3EFYI%20-%20it's%20now%20Oct%20of%202019%20and%20this%20is%20still%20a%20problem%20with%20Teams%20at%20my%20company.%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F13364%22%20target%3D%22_blank%22%3E%40David%20Phillips%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-904518%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-904518%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20is%20October%2029%20and%20the%20Teams%20file-lock%20issue%20has%20been%20egregious%20to%20the%20point%20that%20collaboration%20is%20impossible.%20We%20have%20cleared%20caches%2C%20rebooted%20and%20so%20on%20and%20have%20just%20decided%20that%20it%20is%20better%20to%20have%20a%20user%20save%20the%20file%20with%20a%20new%20name%20and%20upload%20-%20this%20is%20unworkable%20if%20you%20have%20several%20reviewers.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EShould%20several%20users%20be%20able%20to%20collaborate%20if%20one%20has%20the%20document%20open%20in%20the%20Desktop%20App%2F%3CBR%20%2F%3EWhat%20is%20the%20secret%20to%20clearing%20file%20locks%3F%20Killing%20the%20cache%20in%20the%20browser%20(Edge)%20doesn't%20seem%20to%20have%20any%20affect.%20It%20is%20taking%20sometimes%20more%20than%2024%20hours%20for%20a%20file%20lock%20to%20clear%20on%20it's%20own.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-904519%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-904519%22%20slang%3D%22en-US%22%3EThe%20secret%20is%20using%20Updated%20and%20latest%20office%20clients%20and%20leveraging%20%22Auto%20Save%22.%20Doing%20so%20will%20prevent%20locking%20issues.%20If%20you%20inject%20old%20office%20clients%20into%20the%20picture%20this%20starts%20to%20happen%20often%20since%20they%20can't%20co-author%20and%20instead%20try%20to%20grab%20ahold%20of%20documents.%20%3CBR%20%2F%3E%3CBR%20%2F%3ENot%20saying%20this%20is%20100%25%20the%20problem%2C%20but%20utilizing%20it%2C%20will%20reduce%20headaches%20by%20a%20lot.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-904603%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-904603%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%20%2C%20thank%20you%20so%20much%20for%20the%20quick%20reply.%20I%20work%20at%20Microsoft%20and%20are%20using%20the%20very%20latest%20and%20greatest%20most%20up%20to%20date%20versions%20of%20Office%2C%20Teams%2C%20Updates%2C%20etc.%20I%20have%20had%20file%20locking%20issues%20pretty%20much%20every%20day%2C%20and%20so%20have%20my%20team%20mates%20(also%20using%20the%20latest%20and%20greatest.)%20It%20seems%20to%20occur%20if%20someone%20is%20editing%20the%20file%20on%20the%20Teams%20site%2C%20while%20someone%20else%20is%20editing%20the%20file%20in%20the%20Desktop%20app.%20I%20say%20seems%20because%20we%20haven't%20sat%20down%20and%20tested%20it%20properly%20to%20try%20and%20reproduce%20(deadlines...)%2C%20but%20will%20see%20if%20we%20can%20do%20so.%26nbsp%3B%3CBR%20%2F%3EYesterday%2C%20a%20user%20had%20the%20file%20opened%20in%20Teams%2C%20viewed%20and%20closed%20it%20and%20it%20took%20till%20the%20next%20day%20to%20clear%20the%20file%20lock.%20He%20even%20rebooted%20his%20machine%2C%20but%20I%20am%20not%20sure%20if%20that%20cleared%20his%20cache.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EWell%20thank%20you%20for%20listening.%20I%20am%20pretty%20sure%20that%20before%20the%20end%20of%20next%20week%20we%20will%20see%20this%20problem%20occur%20again%2C%20so%20if%20I%20can%20get%20the%20steps%20to%20produce%20right%2C%20I%20will%20post.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAll%20the%20best%2C%20San%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-904605%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-904605%22%20slang%3D%22en-US%22%3EAfter%20you%20read%20my%20response%2C%20I%20just%20want%20to%20add%20that%20I%20will%20look%20into%20whether%20the%20entire%20team%20has%20auto-save%20on.%20Off%20the%20top%20of%20my%20head%2C%20I%20can't%20recall%20if%20auto-save%20is%20Word%20or%20doc%20attribute%2C%20so%20thanks%20for%20that%20tip.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-904606%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-904606%22%20slang%3D%22en-US%22%3EGood%20point%20on%20the%20Teams%20thing.%20I%20forgot%20about%20that.%20I%20usually%20train%20users%20to%20just%20open%20via%20online%20or%20client.%20I%E2%80%99m%20hoping%20with%20the%20files%20tab%20SharePoint%20update%20that%20files%20may%20open%20differently%20but%20time%20will%20tell%20if%20that%20update%20ever%20gets%20released%20anytime%20soon%20%3B).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-904608%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20keeping%20files%20locked%20after%20closing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-904608%22%20slang%3D%22en-US%22%3EIt%E2%80%99s%20a%20setting%20you%20can%20turn%20off%20by%20default%20now%20in%20the%20client.%20It%E2%80%99s%20usually%20not%20saved%20per%20file%20and%20is%20on%20by%20default.%3C%2FLINGO-BODY%3E
David Phillips
Super Contributor

I've been testing files in Teams.  It appears it's keeping files locked open after they're closed in Teams.  For example - edit a file in the Teams window, close it, then go try to delete the file 5 minutes later on the SP side, it says it's locked for editing.  Has anyone else experienced this?

46 Replies

Are you also having an issue with users not being able to save a file in the "Files" tab and they have to save it with another name or save it locally to not lose their work? I noticed the problem in different tenants occasionally happening over the past couple of months but at my current project I am noticing it starting to happen too often. I am still researching it myself.

Sortof.  What I found is if you open the file in Teams, then close it, but leave Teams open, when you try to open the file in Excel from the SP, you get the locked dialog, and you're prompted to read only or save as a different file name.  I also noticed that if you open it later in Teams, and try to edit with Excel. it says it's locked open.  Seems a bit random too.

 

I found this article about changing a registry setting for the web client service but am unsure if it would have impact beyond Teams. Feel free to investigate this:  

 

https://techcommunity.microsoft.com/t5/SharePoint/File-locking-issue/td-p/71185

 

 

What I think is happening is the way Teams caches files when you open it in Teams it's still keeping it open when you close it out. Also even when editing with excel online sometimes it won't gracefully exit and the lock will always stay on the file for 5-10 mintues so you cannot do things like delete/edit file name etc. but you can open it again in Teams or Office online/ Current Office clients for co-authoring.

I hope that can be addressed.  While it might make sense to us as tech people, that will drive users nuts.

Yeah, with their file UI updates coming to match SharePoint online, I really hope they look at just integrating directly into Teams opening in Office Online and just bypassing the whole separate Teams integration part. I think they do this because of the conversations on the right, but you can still have those when views website / office files using tabs, so should just be a similar experience. Having Teams edit, but then an option to edit in word online, etc is kind of redundant when they really kind of are the same thing.

It could be a similar issue to Office365 documents in SharePoint getting locked. The issue there is that sometimes people will close files by clicking the red X in the top-right corner. The fix is always to open the file and close it again by clicking "File -> Close".

Has anyone found or heard of ways around this? It make it difficult to use TEAMs effectively when creating new files in the TEAMs location you want them and then trying to edit them and having to wait. For example just trying to create a new Excel file then when you open it, it says it's locked and doesn't ever seem to notify you when it's freed up. I've reverted back to creating the file and saving it outside of TEAMs, editing it then just coping it up to TEAMs. Bit of a band-aid for now and would really like to know when this will be addressed.

Similar issue when creating WORD documents. I created some in TEAMs and realized I put them in the wrong folder. Since they were locked I couldn't move them or delete them. TEAMs says it does it but the file just stays there. When opening up the SP site is only when you actually get an error. 

I can give you two suggestions but I do think what you are referring to likely to be a bug. We are opening a ticket with MSFT today, but others have already opened tickets about this and I am not sure where it went. Your idea of creating the docs outside of Teams, then uploading is the safest idea I am using at the moment. Here are my other ideas for you to try:

1. Clear the Office cache on your computer. The directory should be something like C:\Users\YOURNAME\AppData\Local\Microsoft\16.0\OfficeFileCache. Delete all of the files that begin with FSD & FSF.

2. Click your Windows key, type "Office Upload Center" then Settings --> Delete Cached Files

Another last resort would be to change registry setting for file locking (unfortunately I can't find the article for that at the moment). The only thing about this is that I am not sure if doing this actually disables your ability to check-in/check out documents or not. You would have to test that.

Matthew

We do have the same Issue. Did anybody get Response to that from Microsoft due to a call?

Hello guys,

 

I have an update. I opened a Microsoft call and we got an answer very fast. Microsoft is aware of this Problem. The short solution with one Client is to place him to the monthly update channel. This is not an option in our business environment, because the monthly update channel is just for consumer customers (as the informed me). I hope some of you will help this! Information!

 

What I want to know is if Microsoft is willing to fix this. Co-Authoring IMHO is a killerfeature and must also be available for business customers. Pleas give me information if and if yes, when it will be available for business customers.

 

Greetings Andre

Hi! Thank you! Seems like a strange answer from MS though :\ Also Co-authoring is available for business costumers aswell..This problem is outside the scope of co-authoring 

Hi,

 

secretly I know that co-authoring also works in the business environment. But if Microsoft Support tells me that I have to switch from semi annual over to monthly and that this more for consumer customers (I know it´s also for business) then I am wondering......

 

I just spoke to a colleague with a little bit more background information and he also confirmed me now that monthly is also for business customers. Therefore someone in our organisation has to decide if we switch to monthly or not ;).

 

But I am still wondering why Microsoft Support ist telling me such things.

Well, everyone can make mistakes :) I doubt switching to monthly channel will help though..please let me know

 

Adam

It already helped with one client. We already moved just one client to test the solution proposal. With the newest Office Update the problem has been blown away instantly.

I´m very glad to hear!! Learning something is awsome :)

 

Adam

Yes indeed, I am with you. Personally I am more a sharepoint / Onedrive / Teams guy than a client-OS guy and I learned a lot within this issue ;) .

This is still a problem mid-September 2018.  Any updates on when a fix will be pushed to customers?

@Andre Radtke would you mind sharing that MS case number?  I may open a case as well if we can't figure this one out on our own.

There is no File -> Close these days in the online versions of Office. If Microsoft would have left that button I would gladly use it. In the meantime, the amount of times I find myself locked out of renaming my own files is just crazy. That is THE ONE reason I steer away from Teams/SharePoint.

Andre, would you mind sharing the O365 build you are on that fixed this issue for you?    We are on semi-annual and still running 16.0.9126.xxxx and have this issue still.   

Yes we have this same issue.  Open the file from MS Teams, make one small edit, close it.  Then Open this file in Excel (client app).  It is set to read-only, in the yellow information bar click Edit Workbook.  The "File In Use" popup displays. (1) View a read-only copy (2) Save and edit a copy of the file (3) Receive a notification when the server file is available.  -- None of these work for me.

I go get a coffee and (about 5 minutes) then click Edit Workbook again then sometimes it works. :(

 

My team is opening a ticket with Microsoft.  I will update this post once I have a solution or work-around.

 

Hey Ted, we now use the Version 1808 (Build 10730.20155 Click-to-run). I hope it helps. I am not fully sure if it helped our whole Organisation. I will follow up it in a few days internally.

 

Cheers Andre

We are seeing the same thing, frustrating this type of an issue is still happening even with the co-authoring update to semi-annual channel. 

 

I dug into the monthly channel for our company pretty deep, and it isn't that it isn't for business - it is about the update frequency.  Monthly channel is what the consumer base of the world that has office click to run is on and is a great test bed (millions of users) before those changes get rolled into semi-annual targeted, then into semi-annual.  The update frequency of monthly updates may be 2 or more updates in a single month.  Where the updates to semi-annual are very predictable and only happen every 6 months.  Personally I am struggling with the need to wait 6 months before the goodness of monthly channel updates come out (focused inbox, co-authoring, some stability items in office apps etc..)  true it is nice to have a 6 month runway for change, but sometimes the benefit of smaller / more frequent updates that give functionality and stability may be worth the end user experience impact of multiple updates a month.  We actually moved to 2x month windows patching due to the frequency of patches and the desire we had to reduce the time it took to patch (2x 10-15 minutes vs 1x a month of 20 plus minutes of downtime) was worth it..  

 

Just some food for thought..  I would really be interested in any updates that any of you get on the locking issue as it carries a significant impact for us as I am sure it is for everyone!

 

Jason

I'm having this issue as well, created a document in Teams and then when I try and delete it I can't.

Thanks Andre. Version 1808 corrected the issue for us as well.

Hey folks,

 

@David Phillips, is your Problem solved also? I read the whole post history today and I am wondering if your Problem is also solved?!?

 

Best regards

Andre

Hi. This is still a problem.

 

I am a consultant working for a client. They are starting to use Teams extensively.

I have upgraded to Office 1808.

I have set the web client setting to not lock files.

I have empties Office upload center cache, and set it to delete the cache after file is closed.

 

Still the following happens:

In teams I open the files tab.

I add a word file.

I edit the file in Teams.

Then I close the file.

Then I select the file and try to delete it.

Then I get the error message:  

"Sorry we ran into a problem. The file filename.docs" is locked"

 

So I use only Microsoft Teams. No local Office and no Office online.

No other people are using the file.

This happens both in Onedrive synced Libraries and not synced libraries.

 

It is terrible! And people are very annoyed.

 

I have to tell people to not use Teams.

We need to sync all Teams Files (from SharePoint) and use local Office to edit and save files. 

That works fine.

 

This is a very serious problem. 

And there is no help.

 

@per ove Did you open a call at Microsoft. I would suggest that while other useres reported that their problem got solved by 1808. Please keep us posted because you are right it is crucial that this things are working!

I will open a ticket, but I admit that doing so is not something I like.

My experience with support is that I need to spend a lot of time to make them understand the problem, and takes me a lot of hours of talking and corresponding before anyone with competence can solve the case. 

 

Office build 1808 does not solve the case. This is probably a Teams related issue.

 

Negative thoughts aside, I will create a support case. :)

 

Me too, I hate spending time to clearify things twice and tell people over and over again what´s happening, but in the end if the issue is such a big one for you and I understand it is, the effort is worth it, I promise. I just like to encourage you to keep on ;). Keep us posted !

Solution:

1. Go to 'Office Upload Center' 
2. Settings -> Delete cached files (I checked the box for "Delete files from the Office Doc.. etc" too, idk if that's a must)
3. Logout of Microsoft Teams then login again 
4. Check if you can delete, move, rename etc some files.

 

If it's not helping, i suggest a temporary workaround:

 

Open the file in SharePoint -> select it from the list -> Show Actions -> More -> Check out -> Checking Out is Done -> Try Delete/Move to/Rename.

where is "office upload center"

Hi:

 

I am also going through the same issue. I could edit a docx in Teams, but could not delete even after 4 hrs since making the change. Just do not know what to do.

 

Thanks

Krishna

We experience the same thing - after editiding a file and closing it in teams  - when someone else tries to open the file to continue working with it they get a message that the file is locked for editing by the last user of the file. This seems sporadic - we have not yet found out when this occurs or why. Just happens occationally, seems random(although it's probably not?)@David Phillips 

@Matthew J. Bailey option 2 seems to be working as a temporary solution for me at the moment, thanks.

@KrishnaRajagopNone of previous workaround worked for me.

Only thing that worked was:

1.- Sign out Teams and restart

2.- Wait 1-2 minutes and try again.

3.- Move, Delete, etc.

This worked for a couple of my clients. Thanks!

 


1. Go to 'Office Upload Center'
2. Settings -> Delete cached files (I checked the box for "Delete files from the Office Doc.. etc" too, idk if that's a must)
3. Logout of Microsoft Teams then login again
4. Check if you can delete, move, rename etc some files.

If it's not helping, i suggest a temporary workaround:

Open the file in SharePoint -> select it from the list -> Show Actions -> More -> Check out -> Checking Out is Done

I believe I solved the problem. I looked at the "Conversations" tab and noticed the file I started/uploaded ended up there. Once I deleted the message, I was able to delete/edit the file on the "Files" tab. @David Phillips 

 

FYI - it's now Oct of 2019 and this is still a problem with Teams at my company.  @David Phillips 

Here is is October 29 and the Teams file-lock issue has been egregious to the point that collaboration is impossible. We have cleared caches, rebooted and so on and have just decided that it is better to have a user save the file with a new name and upload - this is unworkable if you have several reviewers. 

Should several users be able to collaborate if one has the document open in the Desktop App/
What is the secret to clearing file locks? Killing the cache in the browser (Edge) doesn't seem to have any affect. It is taking sometimes more than 24 hours for a file lock to clear on it's own.

 

The secret is using Updated and latest office clients and leveraging "Auto Save". Doing so will prevent locking issues. If you inject old office clients into the picture this starts to happen often since they can't co-author and instead try to grab ahold of documents.

Not saying this is 100% the problem, but utilizing it, will reduce headaches by a lot.

Hi @Chris Webb , thank you so much for the quick reply. I work at Microsoft and are using the very latest and greatest most up to date versions of Office, Teams, Updates, etc. I have had file locking issues pretty much every day, and so have my team mates (also using the latest and greatest.) It seems to occur if someone is editing the file on the Teams site, while someone else is editing the file in the Desktop app. I say seems because we haven't sat down and tested it properly to try and reproduce (deadlines...), but will see if we can do so. 
Yesterday, a user had the file opened in Teams, viewed and closed it and it took till the next day to clear the file lock. He even rebooted his machine, but I am not sure if that cleared his cache. 

Well thank you for listening. I am pretty sure that before the end of next week we will see this problem occur again, so if I can get the steps to produce right, I will post. 

All the best, San

After you read my response, I just want to add that I will look into whether the entire team has auto-save on. Off the top of my head, I can't recall if auto-save is Word or doc attribute, so thanks for that tip.
Good point on the Teams thing. I forgot about that. I usually train users to just open via online or client. I’m hoping with the files tab SharePoint update that files may open differently but time will tell if that update ever gets released anytime soon ;).
It’s a setting you can turn off by default now in the client. It’s usually not saved per file and is on by default.
Related Conversations
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
13 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
22 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
PacketMon Components are not loading in WAC 1909
HotCakeX in Windows Admin Center on
2 Replies