Windows Narrator Not Responding — Screen Reader Crashes and Audio Issues
About Windows Narrator Not Responding
Fix Windows Narrator screen reader not responding, crashing on startup, failing to read text, or producing no audio output for accessibility needs. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: Narrator is the built-in Windows screen reader for users who are blind or have low vision. It reads aloud text on screen, describes UI elements, and provides audio feedback for navigation. Narrator uses text-to-speech voices — Microsoft David, Zira, or downloaded natural voices. The Win+Ctrl+Enter shortcut toggles Narrator on and off. Narrator works with most UWP and Win32 applications through UI Automation APIs. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: Audio output device not configured correctly or muted. Narrator service crashed due to a conflicting application or driver. Text-to-speech voice package corrupted or missing after a Windows update. Application not implementing UI Automation APIs properly, causing Narrator to hang. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Check audio output: ensure the correct speaker/headphone is selected and volume is not muted. Restart Narrator: press Win+Ctrl+Enter to turn off, wait 5 seconds, press again to restart. Reset Narrator settings: Settings > Accessibility > Narrator > scroll down and select a different voice. Update text-to-speech voices: Settings > Time & Language > Speech > Manage voices > Add voices. Run System File Checker to repair system files: sfc /scannow from an admin Command Prompt. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our Windows Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
Can I accidentally enable Narrator?
Yes. Pressing Win+Ctrl+Enter toggles Narrator. If you hear unexpected speech, press the same shortcut to turn it off. You can also disable the shortcut in Settings > Accessibility > Narrator.
Overview
Fix Windows Narrator screen reader not responding, crashing on startup, failing to read text, or producing no audio output for accessibility needs.
Key Details
- Narrator is the built-in Windows screen reader for users who are blind or have low vision
- It reads aloud text on screen, describes UI elements, and provides audio feedback for navigation
- Narrator uses text-to-speech voices — Microsoft David, Zira, or downloaded natural voices
- The Win+Ctrl+Enter shortcut toggles Narrator on and off
- Narrator works with most UWP and Win32 applications through UI Automation APIs
Common Causes
- Audio output device not configured correctly or muted
- Narrator service crashed due to a conflicting application or driver
- Text-to-speech voice package corrupted or missing after a Windows update
- Application not implementing UI Automation APIs properly, causing Narrator to hang
Steps
- 1Check audio output: ensure the correct speaker/headphone is selected and volume is not muted
- 2Restart Narrator: press Win+Ctrl+Enter to turn off, wait 5 seconds, press again to restart
- 3Reset Narrator settings: Settings > Accessibility > Narrator > scroll down and select a different voice
- 4Update text-to-speech voices: Settings > Time & Language > Speech > Manage voices > Add voices
- 5Run System File Checker to repair system files: sfc /scannow from an admin Command Prompt