Share via

How to fix Windows Voice Access error 9001

Marta Wielgosz 20 Reputation points
2025-07-09T12:40:28.8833333+00:00

I have purchased a new laptop and I am constantly running into issues with Voice Access not listening, especially after it is muted. I have tested two microphones, both of which show activity in the settings audio tab. Voice Access has speech permissions. Restarting Voice Access sometimes solves the issue, but it is not a reliable solution as it requires another person to assist me. I am disabled and I cannot operate a mouse or keyboard - I only rely on Voice Access, so this issue is especially vital for me. On my previous laptop, I did not run into such problems so often. I have also tried a clean boot to solve issues with conflicting microphone access. It seems to have helped slightly (previously Voice Access did not listen at all), but finally it still crashes. What steps can I take to fix this problem?

Windows for home | Windows 11 | Accessibility
0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2025-07-10T02:48:31.2766667+00:00

    Hello, Marta Wielgosz

    Welcome to the Microsoft Q&A

     

    Thank you for your feedback. I read your description of the problem and I understand the trouble it has caused you.

     

    I read your request for help and empathize with your current dilemma. For you, the voice access function is not an ordinary tool, but a key bridge for you to communicate with the digital world and achieve independent operation. When this bridge becomes unreliable and errors occur repeatedly, I fully understand how much inconvenience and frustration it will bring to you.

     

    The error code 9001 you mentioned, as well as the specific phenomena of "unable to listen normally", "more serious problems after muting" and "temporarily solved after restarting", provide us with very important clues. This usually points to a core problem: a conflict between the voice access service and other audio drivers, applications or system power management functions, resulting in its inability to "lock" and use the microphone continuously and stably.

     

    Based on the above analysis, I suggest that you can try the following methods to troubleshoot the error, which may help your current problem.

     

    Method 1: Optimize the microphone device settings and disable "exclusive mode": This feature allows an application to monopolize the microphone, which may be the root cause of the conflict.

     

    • Right-click on the sound icon in the taskbar and select "Sound Settings".
    • Scroll down and click "More Sound Settings", which will open an old version of the "Sound" control panel window.
    • Switch to the "Recording" tab. Find the microphone you are using and double-click it to open the properties.
    • Switch to the "Advanced" tab.
    • In the "Exclusive Mode" section, uncheck the following two options: "Allow applications to take exclusive control of this device" "Give exclusive mode applications priority" Click "Apply" and "OK".

     

    Turn off all audio enhancements:

    • In the same microphone properties window, look for a tab called "Enhancements" or "Signal Enhancement".
    • Check "Disable all sound effects" or "Disable all enhancements".
    • Click "Apply" and "OK".
    • After completing these two steps, restart your computer and test the voice access function.

    This is the most effective way to solve this type of problem.

     

    Method 2: Adjust power management settings. The laptop's power saving policy sometimes mistakenly puts the USB port you are using (the port connected to the microphone) or audio service into a low-power state, causing the connection to be interrupted.

     

    USB port power management:

    • Right-click on the Start menu button and select "Device Manager".
    • Expand "Universal Serial Bus Controllers". Right-click each "USB Root Hub" and "USB 3.0 eXtensible Host Controller" one by one and select "Properties".
    • Switch to the "Power Management" tab.
    • Uncheck "Allow the computer to turn off this device to save power". Repeat this for all relevant USB controllers.

     

    Create a high-performance power plan:

    • Open "Control Panel" and go to "Hardware and Sound" > "Power Options".
    • Select "Create a power plan".
    • Select "High Performance", name it, and follow the prompts to complete the creation.
    • Set your computer to use this new "High Performance" power plan.
    • This will prevent the system from reducing the performance of critical hardware in order to save power.

    Method 3: Reinstall the audio and USB drivers. Driver instability is another prime suspect, especially on new computers.

     

    • Visit the official website of your laptop manufacturer (e.g. Dell, HP, Lenovo, etc.).
    • Download the latest audio and chipset drivers for your specific model.
    • The chipset drivers include important updates for the USB controller.
    • Install the chipset drivers first, then the audio drivers.
    • Complete the installation and restart the computer.

     

    Method 4: Consider using a dedicated USB sound card, which is a "hardware bypass". If the problem is due to an unresolvable conflict between the laptop's built-in audio driver and voice access, you can use an external USB sound card to completely bypass it.

     

    • This device is very cheap. It is a small, USB-like adapter with a USB-A or USB-C port on one end and microphone and headphone jacks on the other end.
    • Plug your microphone into this USB sound card and then connect it to the computer.
    • Windows will recognize it as a new, independent audio device.
    • In Sound Settings, set this new USB audio device as the default recording device.
    • This often resolves driver conflicts with built-in hardware.

     

    Best regards

    Ami - Microsoft Q&A Support Specialist

    Was this answer helpful?

    2 people found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.