> For the complete documentation index, see [llms.txt](https://support.audacityteam.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.audacityteam.org/au3/troubleshooting/error-codes/error-9996-invalid-device-error.md).

# Error -9996: Invalid Device Error

Learn about causes and fixes for this error.

## Causes

This error indicates that the device that's being attempted to use is not valid, for example:

* The device got unplugged
* The device has a faulty or loose connection
* The device itself is faulty or not a real audio device.

This error can also occur when you are trying to record a number of channels that is not supported in the current configuration.

This error can also occur when using Audacity on Windows with Windows WASAPI as the Host if the selected recording device is being used exclusively by another application. Some applications that could make use of the recording device exclusively are ASIO4ALL, Voicemod (when configured to do so) or Voicemeeter (when configured to do so).

## Fixes

You can attempt to fix this issue with the following methods:

* **Use a different USB port and USB cable.** This will resolve the issue if the fault was in the cable.
* **Use a different audio host**. Sometimes WASAPI works when MME doesn't, sometimes it's the other way round.
* **Use a different number of channels**. For example, some Realtek only work when recording in Mono, while some others only work in Stereo when recording a (loopback) stream.

{% hint style="success" %}
If the troubleshooting steps aren't working for you, feel free to ask in our communities:

* [Forum](https://forum.audacityteam.org/)
* [Discord](https://discord.gg/audacity)
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.audacityteam.org/au3/troubleshooting/error-codes/error-9996-invalid-device-error.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.