Word error causing unexpected quit when writing

A Update Causes Errors in Word and Other Office Applications. The crash occurs randomly and can result in loss of information when writing a document. Microsoft is aware of and has notified its users of the problem and a possible solution.

According to the support document, applications such as Word, Outlook, and OneNote are experiencing crashes when typing. Some users who updated to version 2407 (17830.20138) or higher may experience an application crash. when typing or running a spell checkIf you are one of the victims, do not despair, because there is a solution.

According to Microsoft, the problem occurs when language pack version is not updated to current version. If this file does not match the current Word build number, the application will definitely close at some point. Although users have the option of autosaving to the cloud, “crashes” This can cause headaches if you don’t take steps to prevent it..

The solution proposed by Microsoft is relatively simple for the average Windows user and requires three steps. First, we will need to identify the error in the operating system’s event viewer to see if it is a language pack. Then, we will repair the application and reinstall the language to match the current version of Word, Outlook, or Office.

How to Fix Unexpected Quits in Word, Outlook, and OneNote

If Word suddenly closes when you are typing or when you activate spell checking, you may be a victim of this error. Unexpected Crash Problem affects version 2407.17830.20138 or later of Word, Outlook, and OneNote.To solve this problem, you just need to follow the steps below.

easy way

1. Right-click the Windows Start menu and select Installed apps.
2. Select Word and click Change to launch the Office installer. Then select Online Repair and wait a few minutes.
3. Once the process is complete, open Word (or any Office application) and go to File > Options > Language to display the list of languages.
4. Select the language pack and click the Remove button to remove it. Then click the Add button at the bottom to add it again to match the current version of the app.

the hard way

The hard way requires entering the operating system event viewer and look for the error. This option is recommended for experienced Windows users.

1. Open the Windows Event Viewer by typing “View…” in the search icon or by right-clicking the Start menu.
2. In the side menu, select the Windows Logs option to display the options, and select Application to display events and errors raised by the application.
3. Right-click on “Application” and select “Filter Current Log” to filter out errors. Otherwise, you will have a huge list.
4. After filtering, look at the list of errors for the hour and see the details. The one we are interested in says: “The name of the application with errors is: OUTLOOK.EXE, version: 16.0.17830.20138timestamp: 0x66aaad8c Faulting module name: mscss7it.dll, version: 16.0.12527.20122Timestamp: 0x5e439ea1 Exception Code: 0xc0000005 Failed offset: 0x000000000003e518 Faulting process ID: 0x0x51B0 Faulting application start time: 0x0x1DAE97DD89190C3.

The name of the module with errors varies depending on the language, but compare its version number with the one in the application. If it is an old number, update it by following the steps described in the “Easy way”.