(4) One was a user/repair manual download from the Dell support website (44 pages) (3) One was created by PDF995 from the HRBlock tax program (14 pages) (2) One was created by "Save as PDF" in Libre Office Calc (5 pages) (1) One was created by "Save as PDF" in Libre Office Writer (8 pages) I selected eight PDF documents to reflect a variety of origins, to see if I could isolate a trigger: See the document below for more information.Not doubting your results, but I tested this morning, opening 10 separate PDF documents in Edge Chromium Version 76.0.182.6 (Official build) dev (64-bit), and all printed correctly without creating any issues. Any document that crashed for the client would no longer crash when opened via the Open and Repai r option when opening a document from Word and that seemed to fix the crashing.
Deleting printer drivers (as suggested) did not work. Unregistering and reregistering the dll from the Application Error did not work. I tried running a full Office repair and reinstall and that did not fix the issue. 2127, time stamp: 0x58e3408fįaulting module name: ucrtbase.DLL, version: 6.1412, time stamp: 0x5a64613eįaulting application start time: 0x01d415604cc0ed57įaulting application path: C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXEįaulting module path: C:\WINDOWS\system32\ucrtbase.DLL I had a client that was having the same issue, when using the Save Asįunction on an existing document it would crash Word with the following Application Error:įaulting application name: WINWORD.EXE, version.
I can ensure you that there is no generic problem running 32 bit Office 2016 on 64 bit Windows 10, because that is the setup I am running myself. Also, make sure that there is a printer driver installed and set as the Windows
The Microsoft service also did not help - "do a clean install blabla" - we already tryed all these things, so we stopped waisting our time with first level support.įor us it looks definitely like a software bug inside Office and we hope Office 2018 will fix this :)Ĭan you reproduce the problem if you start Word in Safe mode? If not, the underlying cause is an add-in, a corrupt Normal template, or damaged registry entries for Word. We tryed clean installs and about 10000 other things we found on the forums. Office 2016 32bit on 圆4 Windows 10 Ent., no plugins, nothing special, updates installed. We found no consents between the users with or without the problem. So testing is very time-consumingĪnd cost-intensive. It normally happens with the first document a day. We are searching for a solution since a year now. Same here - we have about 100 Office installations and about 50-60% of the users have this problem. I have restarted my NAS, modem, and router. I have attempted to Change/Repair Office from the Control Panel, but that crashes.
I have completely uninstalled Office 365 from 3 different computers on the network, and reinstalled, with no change. It's an Office/Word/Excel problem, and all 3 instances occurred when saving to networked drives. An attendee at the meeting said that the same thing happened to him at his [totally different company with totally different Note that I can save to my local hardĭrive just fine it's always a networked drive that forces the hard crash in Word or Excel.Īlso, I witnessed the same thing at a meeting that I attended today at a totally different company with a totally different network. It happens with any Office program (Excel, Word, etc) but does not happen with other programs, like Adobe. This problem popped up for me 5 or 6 days ago, and happens every time that I try to save to a networked drive.
Although, we do have other PCs that are working perfectly fine, it's only this machine is having an issue.Īny tips on how to resolve this issue? Please let me know! I'm suspecting Word is crashing because Word is trying to render the Save As destination folder with 50,000+ files inside. Using the "Save" function works but not "Save As". I've tried running the quick and online repair but doesn't resolve the issue. 2033, time stamp: 0x579646a6įaulting module name: mso99Lwin32client.dll, version: 0.0.0.0, time stamp: 0x5793ca8eįaulting application start time: 0x01d1f76509523d8bįaulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\WINWORD.EXEįaulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso99Lwin32client.dll Has anyone encountered an issue with Word (Office 365 version) crashing when using Save As function? This is what I see in the event viewer when Word crashes:įaulting application name: WINWORD.EXE, version.