'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft Word Stopping to Respond Shortly After Opening
Question details
The user needs to resolve an issue where Microsoft Word crashes and becomes unresponsive almost immediately upon opening a file.
- Product
- Microsoft Word
- Device & OS
- Windows
- Scenario
- Opening a document to read or edit in Microsoft Word.
- Observed behavior
- Word stops responding a few seconds after the document opens, displaying a Windows prompt that the program has stopped working. Standard reinstallation of Microsoft 365 fails to resolve the error.
Ensure you have your Microsoft 365 or university account login credentials readily available, as you may need to sign back in after repairing or cleanly reinstalling the software.
Remove Conflicting Office Versions and Repair the Installation
Multiple installations or older trial versions of Office can severely conflict with Microsoft 365, causing it to crash upon startup.
Often, pre-installed trial versions of Microsoft Office are left on a PC when a new subscription is installed. These overlapping files frequently trigger crashes when opening documents.
Press the Windows key, type 'Control Panel', and press Enter. Navigate to 'Programs' and then click on 'Programs and Features'.
Scroll through the list of installed applications and look for any older versions or trial versions of Microsoft Office. Right-click them and select 'Uninstall'.
Right-click your active Microsoft 365 installation in the same list and select 'Change'. Choose 'Online Repair' and follow the prompts to fix the remaining installation.
Launch Word in Safe Mode to Isolate Add-in Conflicts
Starting Word in Safe Mode bypasses all third-party add-ins, which are common culprits for sudden app crashes.
Perform a Clean Uninstall and Test a New User Profile
If standard repairs fail, the issue might be rooted in deeply corrupted configuration files or a corrupted Windows user profile.
Switch to WPS Office for a Stable and Seamless Experience
If Microsoft Word continues to crash or you are tired of running complex repair tools, try WPS Office. It provides a lightweight, highly compatible, and free alternative to Microsoft Office that is designed to perform smoothly without bogging down your system.
Frequently Asked Questions
Why does Microsoft Word stop responding immediately after opening?
This is typically caused by conflicting third-party add-ins, corrupted Office installation files, or interference from older, duplicate installations of Microsoft Office left on your computer.
What should I do if Safe Mode doesn't fix the Word crashing issue?
If Safe Mode doesn't resolve the issue, the problem might be deeper than add-ins. Check your Windows Control Panel for conflicting or trial Office versions to uninstall, or use the Microsoft Support and Recovery Assistant for a completely clean reinstall.
Can a corrupted Windows user profile cause Word to crash?
Yes, corruption within your Windows user profile settings or registry keys can cause Office applications to crash consistently. Creating a new local user profile in Windows Settings and testing Word there can help isolate and bypass this issue.
