How to identify the exact chip and driver you need

Driver development and reverse-engineering notes (for integrators and tinkerers)

Security and reliability considerations

Example troubleshooting scenario (concise, actionable)

Where to look for more information

Practical recommendations

If you provide:

The AB13X USB Audio driver typically appears when using Apple USB-C EarPods or Apple USB-C to 3.5mm Headphone Jack Adapters Go to product viewer dialog for this item.

on Windows or Linux PCs. While these products are designed by Apple, the internal hardware is often identified by the system as an "AB13X" device, which refers to the specific integrated circuit (IC) or digital-to-analog converter (DAC) chip used in the adapter. Key Technical Details

Device Identification: When plugged into a PC, it may show up in the Device Manager or sound settings as "AB13X USB Audio" or "Avocent AB13X USB Audio".

Driver Type: It generally uses the standard USB Audio Class (UAC) drivers built into modern operating systems (Windows 10/11, macOS, and Linux). Users typically do not need to download a separate driver manually.

Functions: The driver manages both audio output (streaming sound to your headphones) and audio input (microphone support) via the USB interface. Common Issues and Solutions

If you encounter problems with an AB13X device, such as audio pausing randomly or no sound, consider these troubleshooting steps frequently discussed in community forums:

Automatic Pausing: Users on Reddit have reported that some adapters cause media to pause/play repeatedly.

Driver Reinstallation: If the device isn't recognized, you can fix sound problems by uninstalling the "AB13X USB Audio" entry in Device Manager and restarting your PC; Windows will automatically reinstall the driver. Firmware/Chip Detection

: Some users use the "AB13X" label to verify if they have a genuine Apple product or a third-party clone, though genuine Apple USB-C EarPods are known to show this identifier. Compatibility Windows: Fully compatible with plug-and-play functionality. Linux: Recognized as a standard snd-usb-audio device.

Nintendo Switch: Reported to work for both audio and microphone input when using USB-C accessories.

Are you experiencing a specific error message or connectivity issue with your AB13X audio device? AI responses may include mistakes. Learn more

The AB13X USB Audio driver is a generic driver for inexpensive Chinese USB-C to 3.5mm Digital-to-Analog Converter (DAC) dongles, often appearing in budget, generic, or clone adapters, including some misidentified "clone" Apple or Samsung Earpods. Key Characteristics and Technical Specs

Identification: Often recognized in Windows as "AB13X USB Audio" or "Generic AB13X USB Audio".

Audio Quality: Limited to 16-bit/48kHz, making it unsuitable for high-resolution audio.

Common Use: Primarily used in low-cost, third-party USB-C headphone adapters.

Performance: Reports indicate these adapters can produce lower volume in one ear or poor recording quality compared to genuine branded DACs. Functionality: They often have built-in microphones.

Troubleshooting and Driver IssuesIf the AB13X device is not working correctly, try these steps:

Reinstall/Update Driver: Go to the Device Manager, find the device under "Audio inputs and outputs," right-click it, and select "Uninstall device." Restart the computer to let Windows automatically reinstall it.

Switch Ports: Try using a different USB port on your device.

Disable Enhancements: In Sound Settings, open the device properties and ensure all audio enhancements are turned off, as these can cause issues.

Disable HID Control: In Device Manager, under View -> "Devices by connection," locate the USB Input device (often listed under the headset), and disable the HID-compliant consumer control device if it causes audio pausing.

Use Proper Audio Software: In applications like Poweramp, ensure the output is properly configured, though the hardware limitation to 16-bit/48k remains.

LimitationsMany users have reported that the AB13X DAC is of lower quality, and if it was bought as a "genuine" branded product, it is likely a clone. If you're still having issues, please tell me: Are you using Windows or Android? Is the issue no sound, or low-quality audio? I can give you more specific steps to fix it.

The AB13X USB Audio driver typically refers to a generic audio controller found in various affordable USB-C to 3.5mm adapters, DACs, and even some Apple Earpods (USB-C) when connected to a Windows or Mac computer.

While these devices are often sold as original accessories (like Samsung or Apple), they may appear in your system as "AB13X USB Audio" due to the internal Chinese DAC chipset they use. Common Technical Characteristics

Plug-and-Play: It uses standard USB audio class drivers, meaning no manual installation is usually required for Windows, macOS, or Linux.

Sample Rate Limitations: Many users report that these drivers/chips are limited to 16-bit / 48kHz output, even if the adapter was marketed as high-resolution.

Hardware Variants: This chipset is frequently found in "generic" or third-party adapters often sold on platforms like Amazon as budget alternatives to branded versions. Troubleshooting Common Issues

Volume Control Problems: On some systems (like Sailfish OS or specific Linux distros), volume controls may not work, playing at maximum volume regardless of settings. Changing the audio profile in settings often fixes this.

Low Volume/Imbalance: If audio sounds quiet or unbalanced (e.g., louder in one ear), it could indicate a hardware defect or compatibility issue with the specific USB-C port.

Input Recognition: For recording (like digitizing vinyl), ensure your software (e.g., Audacity) has "AB13X USB AUDIO" selected as the input device in sound settings.

Driver Reset: If the device isn't recognized, you can uninstall the driver from the Windows Device Manager; it will automatically reinstall the next time you plug it in.

Are you trying to fix a specific error with this driver, or are you looking to download a newer version? Problem with USB DAC playback - General - Sailfish OS Forum

If you are seeing "AB13X USB Audio" in your device manager, it typically refers to a generic driver for inexpensive USB-C to 3.5mm headphone adapters (DACs) or USB sound cards based on the Airoha AB13X chip. 

Because these are standard "Plug and Play" (UAC) devices, they usually do not require a specific manufacturer's driver file; however, they can sometimes encounter compatibility issues or incorrectly display as a generic device.  Troubleshooting Steps 

If your adapter is not producing sound or is acting up, try the following: 

Check Windows Updates: Often, Windows will find the specific UAC (USB Audio Class) driver automatically. Go to Settings > Windows Update > Advanced Options > Optional Updates to see if a driver is listed. Reinstall via Device Manager: Right-click the Start button and select Device Manager. Expand Sound, video and game controllers. Right-click AB13X USB Audio and select Uninstall device.

Unplug the adapter and plug it back in; Windows should automatically reinstall the generic driver.

Sample Rate Adjustment: Some AB13X chips struggle with high-bitrate settings. Go to Settings > System > Sound > More sound settings.

Right-click the device, go to Properties, then the Advanced tab.

Try lowering the "Default Format" to 16-bit, 44100 Hz (CD Quality) to see if stability improves.  Identifying the Chip 

The "AB13X" designation is often found in third-party Apple EarPods clones or budget DAC adapters found on sites like AliExpress. If the device continues to fail, it may be a hardware incompatibility with your specific operating system version. 

Are you experiencing a specific error code or complete lack of sound with this device?  SMSL PO100 2024 USB Audio Driver Review - AliExpress

Here are a few options for the text, depending on what you specifically need the text for (e.g., a product description, a technical support page, or a download prompt).

Sometimes a clean slate is necessary. Removing all traces of a faulty driver ensures a fresh start.

pnputil /enum-drivers | findstr /i "ab13x"
pnputil /delete-driver <inf name>.inf /uninstall

Using Native Windows Drivers (Plug & Play) If you just plug the device in, Windows 10/11 will automatically install a generic "USB Audio Device" driver. This is perfectly fine for basic stereo listening. It provides low-latency audio without needing extra software.

Using the Dedicated AB13X Driver To access the special features advertised on the box (e.g., "Virtual 7.1," "Echo Cancellation," "Environmental Effects"), you must install the manufacturer's software suite. This software communicates directly with the AB13X chip to process the audio before it sends it to your ears.

AB13X USB Audio Driver: Everything You Need to Know If you have recently plugged in a new USB-C to 3.5mm headphone adapter or a budget USB headset and seen "AB13X USB Audio" appear in your device settings, you are likely looking for information on what it is and how to get it working properly.

The AB13X is a common, cost-effective digital-to-analog converter (DAC) chip manufactured by Shenzhen Bluetrum Technology Co., Ltd.. It is found in a vast array of generic "dongles," adapters, and budget audio accessories sold across platforms like Amazon, AliExpress, and Temu. What is the AB13X USB Audio Driver?

In most modern operating systems like Windows 10/11, macOS, and Android, the AB13X device does not require a specialized, manual driver installation. It is designed to be Plug-and-Play, utilizing the standard USB Audio Class 1.0 driver already built into your system.

Standard Performance: It typically supports a maximum output of 16-bit / 48kHz.

Generic Identification: Because many manufacturers do not customize the chip's internal firmware, it defaults to the generic "AB13X USB Audio" name rather than a brand name like "Samsung" or "Apple". Common Issues and How to Fix Them

While it is intended to be simple, users frequently encounter minor hurdles with these generic chips. 1. Audio Quality and Static

Some users report hearing loud static when music stops or notice lower fidelity compared to brand-name adapters.

The "AB13X USB Audio" driver is a generic identifier often seen when generic or counterfeit USB-C to 3.5mm adapters (DACs) are plugged into a computer. If your device appears as "AB13X" in the Device Manager, it typically indicates that the hardware is using a standard plug-and-play USB audio class driver rather than a proprietary one. Common Issues & Troubleshooting

If you are seeing this name and experiencing audio problems, here is how to address them:

Generic Hardware Identification: Authentic high-quality adapters (like the Apple USB-C to 3.5mm Adapter) should typically display a brand-specific name. If it shows "AB13X," the device is likely a generic third-party clone.

Driver Update: Since it uses standard USB audio protocols, you don't usually need a manual download. You can try updating it through the Windows Device Manager by right-clicking the device and selecting "Update driver" > "Search automatically for drivers".

Reinstallation: If the audio is crackling or not working, right-click "AB13X USB Audio" in Device Manager, select Uninstall device, and then unplug and replug the adapter. Windows will automatically reinstall the generic USB audio driver.

Compatibility: Some USB-C ports on laptops are "data only" and do not support audio output. Ensure your port supports DisplayPort or Power Delivery, which are common indicators of audio support.

Are you experiencing a specific error like "Device not recognized" or is the audio quality the main issue? Update Audio drivers in Windows - Microsoft Support

The "AB13X USB Audio" driver is a generic driver often associated with USB-C to 3.5mm adapters (DACs) and certain USB-C headphones, including newer Apple EarPods (USB-C) when used on Windows PCs.

Below are three post templates tailored for different platforms and user needs: Option 1: Help Request (For Reddit/Forums)

Help: USB-C Headphones / Adapter showing as "AB13X USB Audio" and not working Post Body:

Hi everyone, I’m having trouble with my [Your Device Name, e.g., USB-C to 3.5mm adapter]. When I plug it into my laptop, Windows recognizes it as "AB13X USB Audio" , but I’m getting [no sound / static / volume issues]. What I've tried: Restarting the PC. Uninstalling the driver from Device Manager. Testing the adapter on my phone (where it works fine).

Has anyone found a specific driver update or a way to get this chipset working properly on [Windows 10/11]? Any advice on rolling back or forcing a generic "USB Audio Class" driver would be great. Thanks! Option 2: Technical Fix/PSA (For Tech Blogs/Social Media) How to Fix "AB13X USB Audio" Driver Issues on Windows Post Body: If you’ve recently bought a budget USB-C audio adapter or Apple EarPods , you might see them show up as AB13X USB Audio

in your sound settings. If the audio is glitchy or missing, here’s a quick checklist to get it working: Check Privacy Settings:

Ensure "Allow apps to access your microphone" is ON in Windows Settings, as this can sometimes block the entire interface. Force Generic Driver:

Go to Device Manager > Sound, video and game controllers > Right-click AB13X > Update Driver > Browse my computer > Let me pick. Select "USB Audio Device" instead of the specific AB13X listing. Avoid "Driver Boosters": Tools like Driver Booster

have been known to accidentally remove this driver, causing USB-C ports to stop recognizing audio devices entirely. #TechTips #USBC #AudioDrivers #Windows11 #AB13X

Option 3: Product Review/Note (For AliExpress/Amazon/Shopping) Solid adapter, recognized as AB13X on PC Review Text:

Used this for my [Phone Model] and it works perfectly. On my Windows 11 PC, it was plug-and-play and appeared as "AB13X USB Audio" immediately. Cheap, supports [48kHz/96kHz] sample rates, compact. Sometimes requires a replug if the PC goes to sleep.

If you don't see it, check your "Sound Output" settings and make sure it’s selected as the default device. Great value for those needing a quick 3.5mm fix! Are you looking to troubleshoot a specific device showing this driver name, or are you writing a guide for a product you sell?

How does an AB13x-based device compare to other common audio solutions?

| Feature | AB13x USB Audio | Realtek ALC897 (Onboard) | Generic USB Audio (UAC 2.0) | | :--- | :--- | :--- | :--- | | Driver Reliability | Moderate (depends on vendor) | High (mature drivers) | Very High (built into OS) | | ASIO Support | Via custom driver | No (ASIO4ALL only) | Rare | | Typical SNR | ~90-100dB | ~110dB | ~85-95dB | | Sample Rates | Up to 24-bit/96kHz | Up to 32-bit/192kHz | Up to 24-bit/96kHz | | Use Case | External USB mics/adapters | Laptop/Desktop onboard | Basic USB headsets |

Conclusion: The ab13x driver excels in providing a cheap, flexible external audio solution. It is not professional grade (like RME or Focusrite), but for $10-$50 USB devices, it is the industry workhorse.

BCD Editor EXAMPLES:

If you ask for help on the "/export" switch, you'll see:

C:\>bcdedit /export /?

bcdedit /export <filename>

This command exports the contents of the system store into a file.  This file
can be used later to restore the state of the system store.  This command is
only valid for the system store.

<filename>          The filename to be used as the destination for the export.
                    If the filename contains spaces, it must be enclosed in
                    quotation marks ("").

Example:

The following command exports the system store to the specified file:

    bcdedit /export "C:\Data\BCD Backup"

So we tried the following and saw it was successful:

C:\>bcdedit /export "C:\Users\<your user name>\Documents\bcdtemp.bin"
The operation completed successfully.

After examining this backup file in our Documents folder (using HxD), our first reaction was: "Man, this thing appears to be full of all kinds of needless 'gunk'!" It even saves the path and filename to this backup file, inside the file itself!

Then we compared it to the original BCD file by making a copy of that file while the OS was offline (connected as a slave drive to a different OS), and found there were MANY differences! So, the 'backup copy' is not really a true copy. And the differences go well beyond simply changing the path name of its location.

So why is this file so 'cluttered' compared to the Windows XP boot.ini file? Its first 4 bytes are a big clue: "regf". Reason: The BCD file has the same format as a Windows Registry hive! (For example, the NTUSER.DAT file begins with the same 4 bytes.) And in fact, once a Windows Vista/7/8 OS has actually started booting-up, it loads the BCD file into the Windows Registry at: HKEY_LOCAL_MACHINE\BCD00000000.

BOOTMGR Experiments:

What happens if we change the NT Disk Signature on a Windows 7 disk drive?

To test this, we used a disk editor to alter the bytes at offsets 0x1B8 through 0x1BB in the MBR (first sector of the disk drive) by simply adding 1 to each byte. If you attempt to boot a PC after doing that, you'll see the following BLACK error screen:

In previous Windows versions, the OS would still boot up this way; even though there was the possibility some program that used the Disk Signature could then have problems. Note: The same error message, with Status: code of 0xc000000e, will also be displayed if we change those NT Sig. bytes to all zeros! Only if you edit these bytes back to their original values will the PC boot-up again.

It's also possible to see such an error if your PC is somehow directed to start booting from a drive other than the normal boot drive, and the BCD Store on that drive points to the first drive, which will obviously contain a different Disk Sig. than what is stored in that drive's BCD. Most PC BIOS have a 'Boot Menu' (often accessible using the F12 key at boot-up) which temporarily makes whatever drive you select, be the first drive on the PC, so a Windows 7, 8.1 or 10 OS on that drive will not have this error! (Note: Unless you plan on always keeping an original Windows OS drive and a new Windows OS drive both connected to your PC, you should never do a new OS install with any other drives connected to the PC!) Why? Because new Windows OS installs often make changes to a primary disk drive, even when installed to a secondary drive! Disconnect all but the disk drive you intend to install a new Win OS on, and in the future you will be able to boot-up the new drive all by itself (or using a Boot Menu key) without it depending upon some primary disk drive you decided to remove, or that has failed.

NOTE: The error shown above is a function of the bootmgr program! We know this, because the same error message will be displayed after altering the NT Disk Signature on a drive that has had its entire C: Volume (where the actual Windows OS resides) removed! So, the Boot Manager must check the NT Disk Signature before it even looks for the presence of the C: Volume.

But how does bootmgr know what those hex bytes should be?

Answer: After examining both our copy and the original BCD file, we found the NT Disk Signature there, in the same order as found in the MBR Sector, no less than 9 times. For our small test install of a new Windows 7 OS, this shows where those bytes occurred (highlighted with a pink background color); along with all the other data contained in a BCD Store file. Note: The \Boot folder of your System Reserved partition will also contain a few LOG files: BCD.LOG, BCD.LOG1 and BCD.LOG2, but the numbered files are often empty. This LOG file is a copy of the BCD file, having the same location written inside it and all the general indications of a BCD Registry file, but about half its bytes may be different.

Have fun examining your own backup BCD copy.

Why is it so difficult to move the C: Volume under Windows 7 or later?

To clarify: Under most previous Windows installs, such as Windows 98, people who performed multi-booting or simply had many different partitions on their PCs often used a program called Partition Magic to shrink or even completely rearrange the layout of partitions on their disk drives. But attempting to change where the C: Volume begins under Windows 7 results in a similar BLACK screen error as above; including the same exact message: "Info: The boot selection failed because a required device is inaccessible." But with a different code: "Status: 0xc0000225."

[Note: This is true whether the correct location is specified in the Partition Table or not; same Status code will be shown in either case. In fact, we doubt that bootmgr even looks at the Partition Table, provided it can find the C: volume where it is supposed to be!]

This problem is similar to the one above (concerning the NT Disk Signature), but involves the exact sector location of the C: drive's partition.

So where in the BCD file, is the sector location of the Windows Boot Sector stored?

The reason for the question being: Although we can find our drive's NT Disk Signature in the BCD Store, we can not find a sector location for the C: drive! Before searching, we had thought only the BCD file would need to be updated if we moved the C: Volume. We knew how partitions are referenced in a Windows REGISTRY (see NTFS Disk Signature), but could not find any similar bytes; other than the 4 bytes of the NT Disk Sig., in our BCD file! So how does bootmgr know where the sector offset location of a C: drive should be, and prevent booting from an OS volume we simply moved and did not resize; even though the data in both the Partition Table and its Boot Sector (Hidden Sectors which give us sector offset to Boot Sector) have already been updated?

Could it be as simple as the OS already having accessed the REGISTRY; with much of the system already running in Memory, it then finds the offset stored there does not match the values in the Partition Table and/or Boot Sector, so it gives us essentially a false message, stating: "The boot selection failed because a required device is inaccessible."? Yet, the bootmgr program could only know that if it did find and access the Registry.

Other Experiments:

2. We next carried out the following steps on a copy of our Windows 7 OS install in order to verify our theory about why Windows 7 does this:

    A) Copy the hidden file bootmgr and various folders (including "Boot\enUS" and "Boot\Fonts") from the "System Reserved" partition to the root directory of the C:\ drive. Note: Five or six files must be 'skipped' when doing this, because the BCD Store (and associated files) will remain in use by the OS (preventing them from being copied)!
    B) Create a copy of the BCD file in C:\Boot by using this command (as Administrator): bcdedit /export C:\Boot\BCD
    C) Change the MBR Sector, so the main OS partition is the 'Active' partition.

After that we were able to boot-up the OS from only the C: drive. In order to prove this is true, we used HxD to zero-out the entry in the Partition Table for the System Reserved partition. (Note: The reason we did not use Windows to 'delete' the partition, is because that could have ruined being able to access it again in the future. By saving those hex bytes elsewhere and zero-filling the entry, we can simply enter those bytes in the table again, in order to restore and access the partition!) Upon rebooting and opening the Disk Management utility, one can graphically see this is true:

    D) We shrank the size of this Volume (C:) to only 8 GB in order to run the next test below.


What about BOOTSTAT.DAT and BOOTSECT.BAK files?


    E) shift the beginning of the C: drive to where the System Reserved partition had been, by correcting the data in both the Boot Sector (VBR) and the Partition Table; not to mention, actually moving the Boot Sector and its following Volume Boot Record sectors as well

You can write to us using this: online reply form. (It opens in a new window.)

Free MBR/VBR TOOLS Page

Back to MBR and Volume Boot Records Index

The Starman's Realm Index Page