Windows crashes (BSOD) when opening a Word 365 attachment
Since yesterday, following a Windows/Office update, my laptop crashes with BSOD when I double click on a Word attachment to open it. I see the splash screen of Word opening for one second, and then the BSOD.
Opening Word alone does NOT crash the PC. Double-clicking a Word file in the File Explorer does NOT crash the PC. (In both cases I notice that the splash screen lasts at least 2-3 seconds, much more than the time before the BSOD.) Launching Thunderbird in safe mode and then double-clicking a Word file DOES crash the PC.
I made all the system updates and checked that Thunderbird and Word are updated.
So it may be Word, or it may be they way that Thunderbird uses to launch Word ??
Windows 10, version 1903. Thunderbird version 60.7.1, in French, compile id 20190611205646. Word as part of Microsoft Office Professional 2016 version 1905 (Build 11629.20246 Microsoft Store) All self-installed during the weekend, so cannot make the difference on the culprit!
Many thanks for your help.
Усі відповіді (2)
You do not mention what options you have got selected in Thunderbird. You used to be able to select MS Word to open MSWord .doc documents, but in more recent times, Microsoft changed a whole bunch of things; some changes were due to opening docs in a sandbox for security purposes.
Try this one first: Menu icon > Options > Attachments > 'Incoming' tab
If Microsoft Word document is listed in the 'Content Type' column:
- click on the 'Action' to see a drop down list.
- select : 'Use Other'
a 'Select Helper Application' window opens.
- Look for and select TWINUI.
This refers to the windows 10 shell and chooses the system default application for the file type.
- click on OK
- Click on OK to close and save Options
Змінено
Thanks a lot! In fact my config is already on "TWINUI".
In the mean time, I discovered that even opening a Word (or other Office) file from the File Explorer will crash the PC - it just occurs rarely, this is why I did not notice at the beginning. So I would say that the fault is on Office (or Windows) and not on Thunderbird... (even if opening via Thunderbird ALWAYS causes the BSOD).