How to fix AccEvent UIAutomation stopped

If you are encountering the error "AccEvent-UIAutomation stopped," it may be related to issues with the AccEvent tool itself or the environment in which it is running. Here are some steps you can take to troubleshoot the issue:

1. Check for Updates: Ensure that you are using the latest version of the Windows SDK, as AccEvent is included in it. Updating may resolve compatibility issues.
2. Run as Administrator: Although it is typically not necessary to run AccEvent as an administrator, doing so may help if there are permission issues.
3. Reinstall the SDK: If the problem persists, consider reinstalling the Windows SDK to ensure that all components, including AccEvent, are properly installed.
4. Check System Requirements: Make sure that your system meets the requirements for running AccEvent, especially if you are examining UI Automation data.
5. Review Logs: If available, check any logs generated by AccEvent for more specific error messages that could guide you in resolving the issue.

If none of these steps resolve the problem, you may want to look for alternative tools or consult the Microsoft documentation for further assistance.

References:

• Accessibility tools - AccEvent (Accessible Event Watcher)

Hi @claraide ouano ,

Thanks for your report. Many users have encountered similar “AccEvent – UIAutomation Events” pop-ups, and some found the following approach helpful:

Press Ctrl + Alt + Del and open Task Manager.

Find the AccEvent program in the list.

Right‑click it and choose Open file location.

In the folder that opens, right‑click the executable and select Delete.

Go to the Recycle Bin and empty it to remove the file completely.

This method works because many users have reported it helped prevent repeated pop-ups. For more community feedback, see this thread, which has received multiple helpful votes:

“I’m seen this window AccEvent UIAutomation Events”

Note: Make sure no accessibility tools or automation scripts depend on AccEvent before deleting, as this could impact screen readers or automated testing tools.

If the issue persists after trying this, please let me know for further assistance.