Excel/Word crashing when co authoring

%3CLINGO-SUB%20id%3D%22lingo-sub-338519%22%20slang%3D%22en-US%22%3EExcel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-338519%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20had%20any%20issues%20when%20co%20authoring%20in%20either%20excel%20or%20word%3F%20Both%20programs%20crash%20unexpectedly%2C%20but%20with%20no%20warning%20or%20error%20message.%20Nothing%20shows%20in%20the%20event%20logs%20as%20to%20what%20happened.%20This%20only%20happens%20when%20co%20authoring%2C%20and%20only%20one%20user%20is%20removed%20from%20the%20doc%2C%20when%20they%20are%20removed%2C%20they%20still%20appear%20to%20be%20in%20the%20document%20to%20the%20other%20users%20in%20the%20doc%20at%20that%20time.%20Reopening%20the%20doc%20picks%20up%20where%20they%20left%20off%2C%20but%20its%20massively%20affecting%20production!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20currently%20have%20a%20ticket%20open%20with%20365%20support%20(Ticket%20%23%3A12768014)%20but%20we%20dont%20seem%20to%20be%20getting%20anywhere%20at%20the%20moment.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EThanks%20in%20advance%2C%20Gary.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-338519%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386905%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386905%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20having%20the%20same%20issue%20with%20two%20of%20my%20users.%20They%20are%20using%20co-authoring%20on%20excel%20and%20they%20always%20click%20'open%20in%20excel'%20since%20not%20all%20the%20features%20they%20need%20are%20available%20on%20excel%20online.%20I%20have%20set%20them%20up%20on%20the%20same%20version.%20Both%20are%20on%20the%20semi-annual%201808%20channel%20and%20on%20Ver.%26nbsp%3B10730.20304%20and%20they%20still%20experience%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-359667%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359667%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20glad%20to%20hear%20that%20we%20aren%C2%B4t%20the%20only%20ones%20with%20this%20problem.%20My%20Word%2FPowerpoint%20crashes%2C%20whenever%20I%20am%20co-authoring%20with%20my%26nbsp%3Bcolleagues.%20We%20have%20had%20the%20problem%20for%20about%202%20months.%3C%2FP%3E%3CP%3EThe%20app%20can%20run%20for%201%20hour%2C%20then%20crash%2C%20then%20run%20for%201%20min%20before%20crash.%20No%20pattern%20I%20can%20find.%3C%2FP%3E%3CP%3EI%20am%20getting%20desperate%2C%20thinking%20about%20going%20back%20to%20the%20old%20days%2C%20where%20you%20had%20local%20copies%20that%20was%20put%20together%20in%20the%20end.%3C%2FP%3E%3CP%3EI%20am%20still%26nbsp%3Bexperiencering%20the%20problem%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-359331%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359331%22%20slang%3D%22en-US%22%3EThe%20client%20in%20question%20doesn't%20use%20the%20OneDrive%20client%20at%20all.%20they%20go%20direct%20to%20SharePoint%20using%20a%20drive%20mapping%20tool.%20They%20are%20on%20the%20standard%20release%20track%20on%20monthly%20already.%20I%20confirmed%20with%20one%20of%20the%20clients%20yesterday%20that%20they%20havent%20seen%20the%20issue%20for%20over%20a%20week%20now%2C%20so%20something%20must%20have%20been%20bundled%20into%20one%20of%20the%20updates%20released%20recently.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-359005%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359005%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F283480%22%20target%3D%22_blank%22%3E%40gbrown481%3C%2FA%3E%26nbsp%3BDid%20you%20disable%20OneDrive%20sync%3F%20The%20issue%20seems%20to%20occur%20either%20when%20one%20user%20opens%20a%20file%20from%20OneDrive%20rather%20than%20Sharepoint%20AND%2FOR%20if%20%22Use%20Office%20to%20sync%20files%20I%20open%22%20is%20enabled%20in%20OneDrive.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20one%20of%20my%20colleagues%20was%20told%20by%20Microsoft%20yesterday%20that%20in%20order%20for%20Coauthoring%20to%20be%20fully%20supported%2C%20MS%20Office%20needs%20to%20be%20in%20the%20%22monthly%22%20update%20channel%20rather%20than%20%22semi-annual%20targeted%22%20because%20the%20feature%20set%20pushed%20out%20is%20different.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-358849%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-358849%22%20slang%3D%22en-US%22%3Ei%20dont%20know%20whether%20any%20of%20you%20are%20still%20having%20these%20issues%2C%20but%20my%20client%20hasn't%20had%20the%20issue%20in%20over%20a%20week%20now!!!%20i%20haven't%20been%20able%20to%20speak%20with%20MS%20directly%20as%20they%20keep%20assigning%20engineers%20that%20are%20nowhere%20near%20my%20timezone%20(there%20should%20be%20a%20policy%20for%20this%20in%20the%201st%20place)!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-355349%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-355349%22%20slang%3D%22en-US%22%3E%3CP%3EYes!%20I'm%20not%20the%20only%20one!%20My%20co-worker%20and%20I%20are%20having%20the%20exact%20same%20issue.%20Hopefully%20MS%20gets%20a%20fix%20out%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-355259%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-355259%22%20slang%3D%22en-US%22%3EMS%20didn't%20ring%20when%20we%20had%20pre-arranged%20to%2C%20so%20no%20further%20with%20them%20specifically.%20although%2C%20I%20did%20some%20testing%20on%20the%202%20users%20that%20have%20the%20issue%20the%20most%2C%20and%20for%20the%20life%20of%20me%20I%20couldn't%20get%20it%20to%20crash%2C%20I%20tried%20for%20half%20an%20hour%2C%20it%20usually%20happens%20within%20a%20couple%20of%20minutes.%20They%20are%20now%20both%20using%20Version%201902%20(Build%2011328.20100)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-354795%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354795%22%20slang%3D%22en-US%22%3E%3CP%3EI'd%20like%20to%20hear%20more%20details%20from%20Microsoft%20as%20well!%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-354332%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354332%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20we%20have%20a%20client%20that%20has%20been%20having%20this%20issue.%20Here%20is%20what%20I've%20been%20able%20to%20find%3A%3C%2FP%3E%3CUL%3E%3CLI%3EUser%20A%20and%20User%20B%20open%20the%20file%20from%20SharePoint%20Online%20using%20%22Edit%20in%20Browser%22%20-%20No%20Problems.%3C%2FLI%3E%3CLI%3EUser%20A%20and%20User%20B%20open%20the%20file%20from%20SharePoint%20Online%20using%20%22Edit%20in%20Word%2FExcel%22%26nbsp%3B%20-%20No%20problems%20(%20I%20think)%3C%2FLI%3E%3CLI%3EUser%20A%20opens%20online%20and%20User%20B%20Opens%20in%20local%20app%20-%20May%20have%20an%20issue.%3C%2FLI%3E%3CLI%3EUser%20A%20opens%20from%20OneDrive%20synced%20to%20SharePoint%2C%20User%20B%20opens%20from%20SharePoint%20-%20Will%20randomly%20crash.%3C%2FLI%3E%3CLI%3EUser%20A%20opens%20from%20SharePoint%2C%20either%20in%20browser%20or%20app%2C%20and%20User%20B%20opens%20from%20SharePoint%20in%20File%20Explorer%2C%20then%20opens%20in%20local%20app%20-%20Random%20crashes.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EThe%20underlying%20problem%20appears%20to%20be%20the%20Auto-Save%20feature%20added%20to%20OneDrive%20for%20Business%20in%20the%20fall%20coupled%20with%20having%20OneDrive%20sync%20to%20SharePoint%20enabled%20and%20allowed.%20All%20the%20documentation%20on%20coauthoring%20I%20have%20seen%20indicates%20that%20you%20need%20a%20shared%20source%20for%20the%20files%2C%20and%20on-prem%20SharePoint%2C%20O365%20SharePoint%2C%20One%20Drive%20and%20OneDrive%20for%20Business%20are%20all%20candidates%2C%20but%20nothing%20says%20anything%20about%20if%20you%20have%20SharePoint%20synced%20with%20OneDrive.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EThat%20said%2C%20I%20also%20opened%20a%20ticket%20with%20Microsoft%2C%20and%20was%20verbally%20told%2C%20definitely%20opening%20from%20two%20different%20locations%2C%20(i.e.%20SharePoint%20and%20OneDrive)%20definitely%20WILL%20break%20coauthoring%20and%20cause%20the%20applications%20to%20crash.%20But%20there%20is%20NOTHING%20in%20print%20as%20of%20this%20writing%20that%20officially%20states%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20this%20is%20a%20scenario%20that%20Microsoft%20didn't%20think%20of%2C%20and%20didn't%20test%2C%20and%20the%20Office%20Suite%20has%20no%20error%20handling%20for.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20only%20solution%20at%20the%20moment%20is%20to%20disable%20OneDrive%20sync%20to%20SharePoint%2C%20but%20I%20have%20one%20client%20that%20doesn't%20accept%20that%20answer%2C%20and%20getting%20detailed%20information%20involving%20all%20the%20possible%20parameters%20from%20end%20users%20is%20nigh%20on%20impossible.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353908%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353908%22%20slang%3D%22en-US%22%3E%3CP%3EGreat!%20keep%20us%20posted!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2F%20Adam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353895%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353895%22%20slang%3D%22en-US%22%3EHi%20Saunit%2C%3CBR%20%2F%3E%3CBR%20%2F%3Eno%20fix%2Fupdate%20as%20of%20yet!%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20been%20assigned%20an%20MS%20ambassador%20now%2C%20we%20have%20a%20call%20scheduled%20for%20tomorrow%2C%20so%2C%20will%20see%20what%20comes%20of%20that.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20Gary%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353666%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353666%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20Microsoft%20have%20an%20update%20on%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ESaunit%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-343823%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-343823%22%20slang%3D%22en-US%22%3EHave%20you%20found%20anything%20to%20help%20it%20or%20stop%20it%3F%20Its%20so%20intermittent%20that%20it%20makes%20it%20so%20hard%20to%20predict%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-339884%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-339884%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20my%20coworkers%20and%20I%20have%20been%20having%20this%20issue%20for%20weeks.%20I've%20had%20to%20change%20my%20auto%20save%20setting%20to%20every%20minute%20so%20I%20don't%20lose%20any%20data%20when%20Word%2C%20Excel%20or%20PowerPoint%20crashes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-438772%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-438772%22%20slang%3D%22en-US%22%3ESame%20issue%20still%20with%20Powerpoint%2C%20Excel%20and%20Word...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-440446%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-440446%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F283480%22%20target%3D%22_blank%22%3E%40gbrown481%3C%2FA%3E%26nbsp%3BWe%20face%20the%20same%20issue%20while%20we%20are%20now%20in%20the%20pilot%20stage%20of%20migrating%20to%20Office365.%3CBR%20%2F%3E%3CBR%20%2F%3EDo%20you%20have%20any%20update%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20windows%2010%20%2F%20proplus%20monthly%20channel.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481063%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481063%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20had%20the%20same%20issue%20now%20for%20about%20four%20weeks%2C%20and%20have%20raised%20the%20issue%20with%20Microsoft%20last%20week.%20We%20have%20navigated%20the%20tier%201%20support%20and%20now%20are%20waiting%20to%20hear%20back.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESummary%3A-%3C%2FP%3E%3CUL%3E%3CLI%3EWe%20produce%20large%20documents%20in%20a%20collaborative%20fashion%2C%20by%20finding%20a%20document%20in%20a%20SharePoint%20Online%20document%20library%20using%20the%20'Edit%20in%20Word'%20feature.%3C%2FLI%3E%3CLI%3EWe%20have%20done%20this%20for%20a%20long%20time%20(co-authoring%20documents%20is%20a%20large%20part%20of%20what%20we%20do)%20and%20the%20issue%20has%20only%20started%20occurring%20(and%20with%20multiple%20people)%20within%20the%20last%20four%20weeks%20or%20so.%3C%2FLI%3E%3CLI%3EWe%20all%20use%20Windows%207%2C%20SharePoint%20Online%2C%20and%20Microsoft%20Office%20downloaded%20from%20Office365%3C%2FLI%3E%3CLI%3EWithin%20a%20random%20amount%20of%20time%20(sometimes%20a%20few%20seconds%2C%20sometimes%20an%20hour)%2C%20Word%20just%20closes.%3C%2FLI%3E%3CLI%3EEnd%20users%20do%20not%20have%20OneDrive%20installed%20or%20configured.%3C%2FLI%3E%3CLI%3ETested%20with%20multiple%20users%2C%20multiple%20computers%2C%20multiple%20documents%2C%20multiple%20document%20libraries%20and%20sites.%3C%2FLI%3E%3CLI%3EMicrosoft%20recorded%20a%20screen%20and%20was%20able%20to%20witness%20and%20acknowledge%20the%20behaviour%20twice.%20Hoping%20the%20issue%20gets%20escalated%3B%20we%20have%20a%20lot%20of%20angry%20users%20-%20which%20is%20frustrating%20when%20we%20have%20spent%20considerable%20efforts%20trying%20to%20build%20confidence%20in%20using%20SharePoint%20Online%20as%20a%20suitable%20platform%20for%20document%20collaboration%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481355%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481355%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20curious%20to%20see%20if%20this%20affects%20organizations%20who%20are%20100%25%20in%20the%20cloud%20or%20like%20mine%20that%20are%20in%20a%20transition%20state%20and%20have%20some%20on%20prem%20stuff%20along%20with%20some%20being%20in%20the%20cloud.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481364%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481364%22%20slang%3D%22en-US%22%3Eeither%20my%20client%20has%20stopped%20bothering%20to%20tell%20me%20about%20the%20issue%2C%20or%20the%20issue%20has%20gone%20away%2C%20as%20they%20haven't%20mentioned%20it%20for%20what%20feels%20like%20forever!%20In%20summary%2C%20I%20have%20found%20that%20in%20the%20past%2C%20the%20issue%20only%20happens%20when%20co%20authoring%20(which%20doesn't%20happen%20as%20often%20as%20it%20used%20to%20do%2C%20probably%20because%20of%20the%20issue%20in%20the%201st%20place!)%2C%20but%20could%20be%20minutes%2C%20hours%2C%20or%20even%20just%20the%201st%20click%20that%20causes%20Word%2FExcel%20to%20close%20with%20no%20explanation.%20MS%20had%20been%20connected%20to%20my%20laptop%20at%20least%203%20times%20when%20the%20issue%20occurred%2C%20and%20had%20no%20answer%20to%20what%20it%20could%20be.%20They%20seemed%20to%20just%20drop%20off%20the%20support%20ticket%2C%20but%20as%20the%20client%20hasnt%20reported%20the%20issue%2C%20I%20havent%20chased%20MS%20myself%20for%20a%20fix.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481376%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481376%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F283480%22%20target%3D%22_blank%22%3E%40gbrown481%3C%2FA%3E%26nbsp%3BI'd%20bet%20they%20just%20aren't%20reporting%20it%20anymore.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20clients%20are%20still%20having%20the%20issue%20and%20we%20have%20an%20open%20ticket%20with%20Microsoft.%20They've%20had%20us%20recording%20the%20issue%20with%20a%20tool%20called%20the%20Problem%20Steps%20Recorder.%20Their%20next%20step%20is%20to%20do%20remote%20support%20of%20two%20users%20simultaneously%20while%20they%20are%20co-authoring%20so%20they%20can%20see%20the%20issue%20first%20hand.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBased%20on%20some%20of%20the%20responses%20above%20it%20seems%20like%20even%20when%20OneDrive%20isn't%20in%20play%20coauthoring%20is%20still%20buggy%20and%20unreliable.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20look%20forward%20to%20seeing%20a%20fix%2C%20but%20I'm%20not%20holding%20my%20breath.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481804%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481804%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F289674%22%20target%3D%22_blank%22%3E%40Bill_R%3C%2FA%3EWe%20use%20Exchange%20on-prem%20but%20SharePoint%20Online%20with%20E3%20licensing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-524236%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-524236%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20received%20*anything*%20tangible%20from%20MS%20yet%3F%20More%20users%20are%20complaining%2C%20senior%20mostly...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20reputation%20of%20SharePoint%20has%20taken%20a%20large%20battering%20at%20our%20organisation.%20I%20could%20have%20done%20without%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-528804%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-528804%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F325441%22%20target%3D%22_blank%22%3E%40Glen226%3C%2FA%3E%26nbsp%3BNothing%20that%20I've%20seen%20so%20far.%20More%20than%202%20months%20of%20people%20having%20this%20issue%20and%20no%20acknowledgement.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-540286%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-540286%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate...%20Microsoft%20have%20advised%20that%20they%20have%20released%20a%20new%20build%20of%20Office%20last%20week%20and%20that%20we%20should%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B*%20Install%20the%20new%20build%20of%20Office%3C%2FP%3E%3CP%3E%26nbsp%3B*%20Then%20perform%20an%20online%20repair%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20going%20to%20test%20this%20with%20one%20user%20who%20is%20commonly%20affected%20and%20will%20report%20back%20our%20findings.%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-541454%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-541454%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F325441%22%20target%3D%22_blank%22%3E%40Glen226%3C%2FA%3E%26nbsp%3BI'm%20looking%20forward%20to%20the%20results%20of%20this.%3C%2FP%3E%3CP%3EIs%20it%20Office%202016%20or%202019%3F%20Either%20way%2C%20please%20post%20the%20build%20number%20if%20it%20works.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EJamie%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-541696%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-541696%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F288128%22%20target%3D%22_blank%22%3E%40JamieBird%3C%2FA%3EOffice%20365%2C%20Build%201904%2C%20released%2029th%20April.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-543754%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-543754%22%20slang%3D%22en-US%22%3E%3CP%3EI%20should%20hopefully%20be%20getting%201904%20this%20week.%20I'll%20test%20things%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-557585%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-557585%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F289674%22%20target%3D%22_blank%22%3E%40Bill_R%3C%2FA%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F288128%22%20target%3D%22_blank%22%3E%40JamieBird%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20All%20-%20we%20have%20been%20testing%20this%20version%20new%20build%20of%20Office%20for%20a%20few%20days%20now%2C%20and%20we%20haven't%20been%20able%20to%20replicate%20the%20Word%20closing%20issue%20since.%20The%20user%20we%20were%20testing%20with%20was%20previously%20heavily%20affected%2C%20with%20documents%20almost%20always%20closing%20within%20an%20hour.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20cautiously%20optimistic%20that%20this%20particular%20build%20has%20resolved%20the%20issue%20at%20hand%2C%20and%20will%20now%20begin%20to%20test%20further%20by%20installing%20this%20Office%20build%20for%20another%20two%20affected%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-777112%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-777112%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F283480%22%20target%3D%22_blank%22%3E%40gbrown481%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20having%20the%20same%20issue%20with%20PowerPoint%20when%20our%20users%20tried%20to%20co-authoring.%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CSTRONG%3EEnvironment%20%3A%3C%2FSTRONG%3E%3CBR%20%2F%3E-%20Microsoft%20Office%20365%20ProPlus%20v1902%20build%2011328.20138%20Semi-annual%20targeted%3CBR%20%2F%3E-%20Microsoft%20Teams%20v1.2.00.17057%20(64bit)%20last%20update%20on%2027th%20of%20June%202019%3CBR%20%2F%3E-%20OneDrive%202019%2019.033.0218.0012%3C%2FDIV%3E%3CDIV%3EThe%20user%20opens%20the%20file%20from%20Microsoft%20Teams%20with%20the%20client%20PowerPoint%20and%20after%205-6%20mins%20It%20crashes.%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EWe%20opend%20a%20ticket%20to%20Microsoft%20and%20we're%20still%20wating%20for%20their%20answer.%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EDo%20you%20have%20any%20idea%20to%20fix%20this%20issue%20please%20%3F%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-796288%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-796288%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383613%22%20target%3D%22_blank%22%3E%40Sofianeda1st%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F283480%22%20target%3D%22_blank%22%3E%40gbrown481%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EWe%20had%20the%20same%20issue%20until%20last%20week%2C%20Powerpoint%20and%20Word%20files%20were%20crashing%20regularly%20for%20several%20users.%20We%20did%20log%20a%20case%20with%20Microsoft%20and%20they%20also%20didn't%20find%20anything%20substantial%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELast%20week%2C%20there%20was%20an%20Office%20365%20client%20update%20which%20got%20installed%20on%20the%20users'%20machine%20and%20since%20then%20no%20one%20has%20reported%20any%20issue%20with%20the%20file%20crashing.%20We%20tried%20to%20reproduce%20the%20issue%20with%20a%20couple%20of%20frequent%20users%20but%20still%20not%20finding%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVersion%20we%20are%20using%3A%26nbsp%3B%3CSPAN%3ESemi-Annual%20Channel%20(Targeted)%3A%20Version%201902%20(Build%2011328.20368)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDid%20anyone%20has%20the%20same%20behaviour%2C%20we%20are%20trying%20to%20find%20what%20fixed%20this%20issue%20and%20what%20exactly%20caused%20it%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%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-810354%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-810354%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389549%22%20target%3D%22_blank%22%3E%40DC11604%3C%2FA%3E%26nbsp%3Bfor%20the%20feedback.%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20the%20same%20version%20of%20yours%20but%20we%20still%20have%20the%20same%20issue%20with%20PowerPoint.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20opened%20a%20ticket%20at%20Microsoft%20but%20they%20didn't%20fix%20the%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3EWe'll%20check%20if%20we've%20an%20update%20on%20our%20client%20or%20we%20will%20try%20to%20force%20it%20in%20order%20to%20fix%20the%20bug.%26nbsp%3B%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-818640%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-818640%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2F%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383613%22%20target%3D%22_blank%22%3E%40Sofianeda1st%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20looks%20this%20issue%20has%20fixed%20by%20Microsoft%20in%20their%20recent%20Office%20365%20client%20update%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fofficeupdates%2Fsemi-annual-channel-targeted-2019%23version-1902-august-13%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fofficeupdates%2Fsemi-annual-channel-targeted-2019%23version-1902-august-13%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20MS%20engineer%20on%20the%20case%20informed%20the%20same%20and%20after%20the%20pilot%20deployment%2C%20the%20issue%20has%20fixed%20for%20all%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-819700%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-819700%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389549%22%20target%3D%22_blank%22%3E%40DC11604%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20feedback.%26nbsp%3B%3C%2FP%3E%3CP%3EActually%20this%20new%20365%20Office%20client%20update%20has%20fixed%20the%20co-authoring%20bug%20in%20PowerPoint.%3C%2FP%3E%3CDIV%3E%3CDIV%3E%3CSTRONG%3EBuild%3A%20Semi-Annual%20Channel%20(Targeted)%3A%20Version%201902%20(Build%2011328.20392)%3C%2FSTRONG%3E%3C%2FDIV%3E%3CDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1024460%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1024460%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20same%20here.%20We%20have%208%20people%20to%20work%20together.%20All%20of%20us%20kept%20crashing.%20It%20was%20before%20an%20assignment%20and%20there%20were%20a%20lot%20of%20mistakes%20due%20to%20MS%20conversion%20error.%20At%20last%2C%20the%20document%20was%20unable%20to%20be%20opened%20any%20more.%20All%20of%20our%20work%20has%20lost!!!%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Ffacepalm_40x40.gif%22%20alt%3D%22%3Afacepalm%3A%22%20title%3D%22%3Afacepalm%3A%22%20%2F%3E%20Well%20done%2C%20good%20for%20light%20co-work%20but%20bad%20for%20large%20team%20co-working.%20If%20MS%20still%20not%20solved%20it%2C%20Sharepoint%20is%20only%20for%20very%20small%20groups%20with%20up%20to%203%20people.%20The%20productivity%20at%20this%20point%20is%20pretty%20low.%20Hopefully%2C%20we%20can%20see%20the%20updates%20many%20years%20later.%20Hehe%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F283480%22%20target%3D%22_blank%22%3E%40gbrown481%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20upvote%20the%20PO%20to%20let%20MS%20see%20this%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1026751%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1026751%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389549%22%20target%3D%22_blank%22%3E%40DC11604%3C%2FA%3E%26nbsp%3Bis%20the%20update%20automatically%20pushed%20to%200365%20subscribers%20or%20is%20this%20something%20we%20have%20to%20actively%20install%3F%20we%20were%20still%20dealing%20with%20crashing%20during%20co-authoring%20as%20recent%20as%20mid%20October.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1110099%22%20slang%3D%22fr-FR%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1110099%22%20slang%3D%22fr-FR%22%3E%3CP%3EHello%20all%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389549%22%20target%3D%22_blank%22%3E%40DC11604%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20been%20reading%20this%20topic%20with%20great%20interest%20since%20we%20are%20having%20the%20same%20issue%20as%20described%20here%3A%20as%20soon%20as%20you%20collaborate%20on%20a%20document%2C%20Word%20crashes%20unexpectedly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20seen%20that%20the%201902%20version%20(Build%2011328.20392)%20patch%20should%20resolve%20the%20issue.%3C%2FP%3E%3CP%3EThe%20problem%20is%20that%20we%20are%20one%20patch%20level%20ahead%20(Version%201902%20(build%2011328.20438))%20and%20we%20still%20encounter%20this%20issue...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20something%20else%20I'm%20missing%3F%3C%2FP%3E%3CP%3EAfaik%2C%20we%20are%20not%20using%20one%20drive%20(which%20seems%20to%20be%20a%20reason%20for%20crashing)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20help.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChristophe%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1180091%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1180091%22%20slang%3D%22en-US%22%3EWere%20you%20able%20to%20resolve%3F%20If%20so%2C%20any%20advice%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1181468%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%2FWord%20crashing%20when%20co%20authoring%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1181468%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F562231%22%20target%3D%22_blank%22%3E%40lknight-sjvh%3C%2FA%3E%26nbsp%3BI%20wasn't%20able%20to%20resolve%20it%20yet%2C%20I'm%20lacking%20time%20to%20conduce%20some%20testings.%3C%2FP%3E%3CP%3EBut%20I%20did%20contact%20Microsoft%20support%20who%20told%20me%20to%20upgrade%20to%20latest%20semi%20annual%20update.%3C%2FP%3E%3CP%3EThe%20Version%201902%20(Build%2011328.20392)%20fixed%20the%20issue%20in%20the%20monthly%20channel%20update.%3C%2FP%3E%3CP%3EI'm%20on%26nbsp%3Bthe%20semi%20annual%20update%20channel%20and%20it's%20possible%20that%26nbsp%3Bthis%20channel%26nbsp%3Bdidn't%20get%20the%20patch%20until%20a%20recent%20release%20I've%20yet%20to%20install.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20it%20seems%20that%20the%20monthly%20channel%20fixed%20the%20issue%20in%20Version%201902%20(Build%2011328.20392)%2C%20but%20the%20semi%20annual%20channel%20seems%20to%20still%20contain%20the%20issue%20in%20the%20Version%201902%20(build%2011328.20438))%20I'm%20using%3C%2FP%3E%3CP%3EI%20still%20have%20to%20upgrade%20to%20latest%20semi%20annual%20channel%20release%20to%20see%20if%20it%20fixes%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Has anyone had any issues when co authoring in either excel or word? Both programs crash unexpectedly, but with no warning or error message. Nothing shows in the event logs as to what happened. This only happens when co authoring, and only one user is removed from the doc, when they are removed, they still appear to be in the document to the other users in the doc at that time. Reopening the doc picks up where they left off, but its massively affecting production!

 

I currently have a ticket open with 365 support (Ticket #:12768014) but we dont seem to be getting anywhere at the moment. 

Thanks in advance, Gary.

38 Replies
Highlighted

Yes, my coworkers and I have been having this issue for weeks. I've had to change my auto save setting to every minute so I don't lose any data when Word, Excel or PowerPoint crashes.

Highlighted
Have you found anything to help it or stop it? Its so intermittent that it makes it so hard to predict
Highlighted

Did Microsoft have an update on this issue?

 

Thanks

Saunit

Highlighted
Hi Saunit,

no fix/update as of yet!

I have been assigned an MS ambassador now, we have a call scheduled for tomorrow, so, will see what comes of that.

Thanks Gary
Highlighted

Great! keep us posted!

 

/ Adam

Highlighted

Yes, we have a client that has been having this issue. Here is what I've been able to find:

  • User A and User B open the file from SharePoint Online using "Edit in Browser" - No Problems.
  • User A and User B open the file from SharePoint Online using "Edit in Word/Excel"  - No problems ( I think)
  • User A opens online and User B Opens in local app - May have an issue.
  • User A opens from OneDrive synced to SharePoint, User B opens from SharePoint - Will randomly crash.
  • User A opens from SharePoint, either in browser or app, and User B opens from SharePoint in File Explorer, then opens in local app - Random crashes.

The underlying problem appears to be the Auto-Save feature added to OneDrive for Business in the fall coupled with having OneDrive sync to SharePoint enabled and allowed. All the documentation on coauthoring I have seen indicates that you need a shared source for the files, and on-prem SharePoint, O365 SharePoint, One Drive and OneDrive for Business are all candidates, but nothing says anything about if you have SharePoint synced with OneDrive. 

That said, I also opened a ticket with Microsoft, and was verbally told, definitely opening from two different locations, (i.e. SharePoint and OneDrive) definitely WILL break coauthoring and cause the applications to crash. But there is NOTHING in print as of this writing that officially states that.

 

I think this is a scenario that Microsoft didn't think of, and didn't test, and the Office Suite has no error handling for.

 

Our only solution at the moment is to disable OneDrive sync to SharePoint, but I have one client that doesn't accept that answer, and getting detailed information involving all the possible parameters from end users is nigh on impossible.

Highlighted

I'd like to hear more details from Microsoft as well!  

Highlighted
MS didn't ring when we had pre-arranged to, so no further with them specifically. although, I did some testing on the 2 users that have the issue the most, and for the life of me I couldn't get it to crash, I tried for half an hour, it usually happens within a couple of minutes. They are now both using Version 1902 (Build 11328.20100)
Highlighted

Yes! I'm not the only one! My co-worker and I are having the exact same issue. Hopefully MS gets a fix out soon.

Highlighted
i dont know whether any of you are still having these issues, but my client hasn't had the issue in over a week now!!! i haven't been able to speak with MS directly as they keep assigning engineers that are nowhere near my timezone (there should be a policy for this in the 1st place)!
Highlighted

@gbrown481 Did you disable OneDrive sync? The issue seems to occur either when one user opens a file from OneDrive rather than Sharepoint AND/OR if "Use Office to sync files I open" is enabled in OneDrive.

 

Also, one of my colleagues was told by Microsoft yesterday that in order for Coauthoring to be fully supported, MS Office needs to be in the "monthly" update channel rather than "semi-annual targeted" because the feature set pushed out is different.

Highlighted
The client in question doesn't use the OneDrive client at all. they go direct to SharePoint using a drive mapping tool. They are on the standard release track on monthly already. I confirmed with one of the clients yesterday that they havent seen the issue for over a week now, so something must have been bundled into one of the updates released recently.
Highlighted

Hi

 

So glad to hear that we aren´t the only ones with this problem. My Word/Powerpoint crashes, whenever I am co-authoring with my colleagues. We have had the problem for about 2 months.

The app can run for 1 hour, then crash, then run for 1 min before crash. No pattern I can find.

I am getting desperate, thinking about going back to the old days, where you had local copies that was put together in the end.

I am still experiencering the problem :(

Highlighted

I've been having the same issue with two of my users. They are using co-authoring on excel and they always click 'open in excel' since not all the features they need are available on excel online. I have set them up on the same version. Both are on the semi-annual 1808 channel and on Ver. 10730.20304 and they still experience this issue.

Highlighted
Same issue still with Powerpoint, Excel and Word...
Highlighted

@gbrown481 We face the same issue while we are now in the pilot stage of migrating to Office365.

Do you have any update?

 

We are windows 10 / proplus monthly channel.

 

Thanks!

Highlighted

We have had the same issue now for about four weeks, and have raised the issue with Microsoft last week. We have navigated the tier 1 support and now are waiting to hear back.

 

Summary:-

  • We produce large documents in a collaborative fashion, by finding a document in a SharePoint Online document library using the 'Edit in Word' feature.
  • We have done this for a long time (co-authoring documents is a large part of what we do) and the issue has only started occurring (and with multiple people) within the last four weeks or so.
  • We all use Windows 7, SharePoint Online, and Microsoft Office downloaded from Office365
  • Within a random amount of time (sometimes a few seconds, sometimes an hour), Word just closes.
  • End users do not have OneDrive installed or configured.
  • Tested with multiple users, multiple computers, multiple documents, multiple document libraries and sites.
  • Microsoft recorded a screen and was able to witness and acknowledge the behaviour twice. Hoping the issue gets escalated; we have a lot of angry users - which is frustrating when we have spent considerable efforts trying to build confidence in using SharePoint Online as a suitable platform for document collaboration
Highlighted

I'm curious to see if this affects organizations who are 100% in the cloud or like mine that are in a transition state and have some on prem stuff along with some being in the cloud.

either my client has stopped bothering to tell me about the issue, or the issue has gone away, as they haven't mentioned it for what feels like forever! In summary, I have found that in the past, the issue only happens when co authoring (which doesn't happen as often as it used to do, probably because of the issue in the 1st place!), but could be minutes, hours, or even just the 1st click that causes Word/Excel to close with no explanation. MS had been connected to my laptop at least 3 times when the issue occurred, and had no answer to what it could be. They seemed to just drop off the support ticket, but as the client hasnt reported the issue, I havent chased MS myself for a fix.