Resolving the Microsoft 365 Word Auto-Launch Bug

Issue Description

A known bug is affecting some Microsoft 365 users, causing Microsoft Word to randomly open after being closed. This issue is particularly prevalent among users with Copilot 365 licenses, but it's not limited to them. The problem manifests as Word unexpectedly launching on its own or reopening after being closed.

Root Cause

The root cause of this issue has been identified as a conflict between Windows Error Reporting (WER) and a background process called DWWIN.exe, which is triggering Word to open. Additionally, a process called ai.exe, associated with Copilot features, may be involved in this behavior.

Troubleshooting Steps

To resolve or mitigate this issue, follow these steps:

1. Check for Copilot 365 License

If your organization recently rolled out Copilot 365 licenses, this could be the trigger. Users without the license typically don't experience this issue.

2. Disable Windows Error Reporting Service

Open Services (services.msc)
Locate Windows Error Reporting Service
Right-click → Properties
Set Startup type to Disabled
Click Stop if it's running, then Apply

Note: This may suppress the behavior but doesn't fix the underlying bug.

3. Use Process Explorer to Confirm

Download Process Explorer from Microsoft SysInternals. When Word opens unexpectedly, check if DWWIN.exe is the parent process of WINWORD.EXE.

4. Perform an Online Repair

Quick Repair may not be sufficient. Try:

Go to Control Panel → Programs → Microsoft 365 → Change
Select Online Repair

5. Group Policy Workaround

If you are managing devices via Group Policy, you might try suppressing Word auto-launch behavior by disabling certain telemetry or startup behaviors, though this is not officially documented as a fix.

Additional Information

Microsoft is aware of this issue, and it's being reported by users in community discussions. The problem is specifically linked to Microsoft 365 and may be more common among Copilot 365 license holders. If the issue persists after trying these troubleshooting steps, it's recommended to contact Microsoft support for further assistance.