xaudio2_9redist.dll Missing: Safe Windows 11 and 10 Fixes

The program can’t start because xaudio2_9redist.dll is missing from your computer. Try reinstalling the program to fix this problem.

You may also see “The code execution cannot proceed because xaudio2_9redist.dll was not found,” “Error loading xaudio2_9redist.dll,” or “The specified module could not be found.”

As an Amazon Associate I earn from qualifying purchases.

The safest solution is usually to repair or verify the affected game or application. xaudio2_9redist.dll is normally an application-local Microsoft XAudio 2.9 runtime, so copying a random replacement into System32 is usually the wrong repair.

Which fix applies to you

Use the first description that matches what happened:

• The error appeared after a game update, reinstall, disk cleanup or failed launcher update: verify or repair the game first.
• Windows Security or another antivirus recently reported a threat: check quarantine and Protection history.
• The DLL is present beside one executable but the game still fails: check the exact executable, runtime folder and application architecture.
• The error says “bad image,” “not designed to run on Windows,” or “contains an error”: replace the application’s copy through official repair or reinstall.
• The error names xaudio2_9.dll rather than xaudio2_9redist.dll: investigate the Windows XAudio component separately.
• The program starts but has audio-device errors afterward: update the audio driver only after confirming that the DLL loads.
• You are developing software or supporting an older Windows application: restore the matching build from Microsoft’s Microsoft.XAudio2.Redist package.

Do not begin with a DLL download site, regsvr32, registry cleaning or repeated copies to Windows system folders.

What xaudio2_9redist.dll actually is

xaudio2_9redist.dll is a legitimate Microsoft redistributable runtime for the XAudio 2.9 audio API. Desktop games and Windows applications use XAudio for sound playback, mixing and related audio operations.

Microsoft distributes this runtime through the Microsoft.XAudio2.Redist package. The package contains x86 and x64 builds, and current Microsoft documentation also identifies an ARM64 build. Microsoft’s deployment guidance is to place the redistributable beside the application executable or in an application-controlled runtime directory. See Microsoft’s XAudio 2.9 redistributable documentation.

This is different from the similarly named Windows component:

• xaudio2_9redist.dll is normally shipped with the game or application.
• xaudio2_9.dll is a Windows XAudio component included with Windows 10 and later.
• xaudio2_8.dll is associated with Windows 8.
• xaudio2_7.dll belongs to the older XAudio 2.7 generation supplied by legacy DirectX components.

Microsoft explains the distinction between the operating-system XAudio files and the redistributable in its XAudio2 versions documentation.

The file name alone does not prove that a particular copy is safe. A genuine copy should come from the application’s official installer or Microsoft’s official redistributable package, and the file should have a valid Microsoft digital signature when applicable.

Fix 1: Verify or repair the affected game or application

This is the most likely fix when the problem began after an update, incomplete installation, failed verification, antivirus action or launcher crash.

Steam games

1. Restart Steam.
2. Open Library.
3. Right-click the affected game.
4. Select Properties.
5. Select Installed Files.
6. Select Verify integrity of game files.
7. Wait for the process to finish.
8. Start the game again from Steam.

Steam should download or restore files that are missing or damaged. If the verification completes but the error remains, restart Windows and verify the files a second time. A launcher or anti-cheat update may have changed the executable being started.

Epic, GOG and other launchers

Open the game’s management menu and look for an action named Verify, Repair, Scan and repair or Check files. Let the launcher complete the process before starting the game again.

If the launcher reports that files were repaired but the DLL error continues:

1. Exit the launcher completely.
2. Restart Windows.
3. Run the repair or verification action again.
4. Check Windows Security quarantine.
5. Reinstall the game from its official launcher if the file is still absent.

Do not copy a DLL from another game. Two games may use the same file name but require different application layouts, architectures or supporting files.

Ordinary Windows applications

For a Microsoft Store or supported Windows application:

1. Open Start → Settings.
2. Select Apps.
3. Select Installed apps.
4. Find the affected application.
5. Select its three-dot menu.
6. Select Advanced options.
7. Select Repair.
8. Start the application again.

If Repair does not help, return to the same screen and use Reset if you can recreate the application’s settings. For traditional desktop software, open Control Panel → Programs → Programs and Features, select the program and choose Repair or Change when the installer provides that option.

If neither repair path restores the file, uninstall the program, restart Windows and install it again from its official source. When the file belongs to one application, reinstalling that application is the definitive repair.

Fix 2: Check antivirus quarantine

Security software can remove or block an application-local DLL. This is especially possible after a game update or when an anti-cheat component changes, although a quarantine event does not prove that the file was harmless.

In Windows Security:

1. Open Start.
2. Type Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent events.
7. Open an event that mentions the affected game, application or DLL.
8. Check the original file path before taking action.

Only restore or allow the file when you can confirm that it came from the legitimate application installer or Microsoft’s official package. Microsoft warns that restoring a quarantined file can cause Defender to detect it again. Its Protection History guidance explains how these events work.

If the event is unclear, leave the file quarantined and reinstall the application instead. Do not disable antivirus protection merely to make the error disappear.

After restoring a trusted file, add an exclusion only if the application vendor specifically instructs you to do so and you understand the security risk. An exclusion can allow future malicious files in the same location to escape scanning.

Fix 3: Confirm the application is using the right copy

A file can exist on the drive and still be unavailable to the executable that needs it. Games commonly include a launcher, an anti-cheat executable, a shipping executable and separate runtime or plugin directories.

Check the executable named by the error:

1. Right-click the game or application shortcut.
2. Select Properties.
3. Open the Shortcut tab.
4. Note the path in Target and Start in.
5. Open the installation folder.
6. Look for xaudio2_9redist.dll beside the executable being launched or in the runtime directory supplied by the application.
7. Start the program using the normal launcher again.

The relevant file may be beside the game executable rather than beside the launcher. A copy in a plugin folder may not be visible to a separate executable.

Windows uses a defined DLL search order, and application-local files can take precedence over system locations. The details are documented in Microsoft’s DLL search order guidance.

Check the architecture

A 32-bit application needs the x86 build. A 64-bit application needs the x64 build. An ARM64 application needs the ARM64 build where supported.

Do not use the names of System32 and SysWOW64 as a shortcut for choosing a file. On 64-bit Windows, System32 generally contains 64-bit system files, while SysWOW64 contains 32-bit system files. Microsoft documents this behavior in its file-system redirector documentation.

The practical rule is simple:

• Restore x86 for a 32-bit application.
• Restore x64 for a 64-bit application.
• Restore ARM64 for an ARM64 application.
• Let the application installer place the file whenever possible.

A 32-bit game will not be fixed reliably with an x64 DLL, even if both files have the same name.

Fix 4: Restore the file from Microsoft’s official package

Developers, system administrators and users supporting an older Windows application can obtain the runtime from Microsoft’s Microsoft.XAudio2.Redist package. Microsoft identifies Windows 7 SP1, Windows 8, Windows 8.1, Windows 10 and Windows 11 as supported environments for the redistributable.

The package contains release binaries under paths equivalent to:

build\native\release\bin\x86\xaudio2_9redist.dll
build\native\release\bin\x64\xaudio2_9redist.dll

Current package documentation also identifies an ARM64 build.

If you have obtained the official package from Microsoft:

1. Make a backup of the application folder if practical.
2. Open the .nupkg package as an archive.
3. Navigate to the matching architecture folder.
4. Copy the DLL into the exact application directory expected by the program.
5. Start the application from its normal launcher.
6. If the error changes, stop copying files and investigate the new message.

Manual extraction is mainly appropriate when the application vendor or developer has identified the required package and deployment folder. Ordinary users should prefer the game’s repair or reinstall process because it restores related files and preserves the application’s intended layout.

The Microsoft runtime is application-local. Do not copy it into System32, SysWOW64 or another Windows directory to make unrelated programs find it.

Why DirectX June 2010 is usually not the answer

The official DirectX End-User Runtime supplies older side-by-side DirectX components, including XAudio 2.7 files. It does not normally install xaudio2_9redist.dll.

That means installing the June 2010 runtime is not the normal fix for an error that explicitly names xaudio2_9redist.dll. It may be appropriate when a game reports a missing legacy file such as an older d3dx, xinput or XAudio component, but it should not replace application repair for this specific runtime.

Visual C++ Redistributable packages and .NET repairs are also separate issues. Install or repair Visual C++ only when another error names files such as VCRUNTIME140.dll or MSVCP140.dll, or the application vendor explicitly requires it.

Fix 5: Install Windows updates

Windows Update will not normally install an application-local xaudio2_9redist.dll, but current updates can matter when the system has missing servicing components, signature-validation problems or an outdated operating-system API.

1. Open Start → Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart Windows.
6. Try the affected application again.

Microsoft’s current process is documented in Install Windows updates.

Windows 7 SP1 deserves special attention because Microsoft states that the redistributable is SHA-2 signed. Windows 7 systems may need the SHA-2 support update identified by Microsoft as KB4474419 before signature validation works correctly. Do not download that update from a third-party driver or DLL site.

Fix 6: Repair Windows components with DISM and SFC

DISM and System File Checker repair Windows itself. They do not generally reinstall a game’s application-local xaudio2_9redist.dll, so use them when Windows components appear damaged or when the error actually concerns xaudio2_9.dll.

Run DISM before SFC:

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes at the User Account Control prompt.
6. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish.
2. Then run:

sfc /scannow

1. Wait until the scan reaches 100 percent.
2. Restart Windows and test the application.

A successful DISM operation should complete without an unrepaired error. SFC may report that it found no integrity violations, repaired damaged files or found files it could not repair. If SFC cannot repair Windows, repeat the application verification steps rather than assuming the game DLL has been fixed.

Microsoft’s System File Checker guidance covers the supported command order and results.

Running DISM and SFC by hand can make it difficult to see what changed when several Windows issues are present. Outbyte PC Repair can scan for the underlying Windows issues; its free scan shows what it found, while repair is done by the full version, and reinstalling the affected game or application remains the definitive fix when its own DLL is missing.

Fix 7: Update audio and graphics drivers only when the DLL is present

A driver problem is not the usual cause of a missing xaudio2_9redist.dll message. Handle drivers after repairing the application, especially if the program now starts but reports no audio, cannot initialize an audio endpoint or has graphics-related crashes.

Update the audio driver

1. Press Win + X.
2. Select Device Manager.
3. Expand Sound, video and game controllers.
4. Right-click the active audio device.
5. Select Update driver.
6. Select Search automatically for drivers.
7. Install the offered driver.
8. Restart Windows.

If Windows finds no driver, use the computer or motherboard manufacturer’s official support page. Avoid driver packages that do not identify the hardware or publisher.

Update the graphics driver

Graphics drivers are not a replacement for the XAudio runtime, but an outdated display driver can cause a separate failure once the game gets past DLL loading.

1. Open Device Manager.
2. Expand Display adapters.
3. Right-click the graphics adapter.
4. Select Update driver.
5. Select Search automatically for drivers.
6. Restart Windows when prompted.

You can also use Start → Settings → Windows Update → Advanced options → Optional updates → Driver updates when Windows lists a suitable driver.

Hunting through hardware models and deciding which of several driver packages is current can be tedious. Outbyte Driver Updater can scan for outdated drivers; its free scan shows what it identifies, while driver installation is done by the full version, and it is not a substitute for reinstalling the affected game when that program owns the missing DLL.

Windows Features will not install this DLL

You can check Windows’ optional feature list, but there is no normal Windows Features checkbox for xaudio2_9redist.dll.

To inspect it:

1. Press Win + R.
2. Type:

optionalfeatures

1. Press Enter.
2. Review the available features.
3. Close the window without enabling unrelated components.

Do not turn on random legacy features hoping that one contains the file. This runtime is normally deployed by the application, not by selecting an optional Windows feature.

What to do with “bad image” and “specified module could not be found”

Different messages point to different failure modes.

“The specified module could not be found”

This can mean the named DLL is missing, but it can also mean that Windows found the DLL and could not load one of its dependencies. It may also indicate an incorrect application path, blocked file or wrong architecture.

Use this order:

1. Verify or repair the application.
2. Check antivirus quarantine.
3. Confirm the executable and runtime directory.
4. Confirm x86, x64 or ARM64 compatibility.
5. Reinstall the application from its official source.
6. If the file is present and the error remains, provide the full error text and executable path to the application vendor.

Do not repeatedly replace the visible DLL without checking dependencies and loader paths.

“Not designed to run on Windows,” “bad image” or “contains an error”

This usually indicates corruption, an incomplete replacement, wrong architecture or a blocked or invalid binary. A generic Windows loader message does not identify one unique cause.

Use Properties → Digital Signatures on the application’s DLL and confirm that the file came from a trusted installer or Microsoft package. If the signature is missing, invalid or the file was copied from an unknown source, remove it through the application’s repair or reinstall process.

Microsoft states that the redistributable binary is Microsoft-signed with SHA-2. A Windows 7 system that cannot validate that signature may need the appropriate servicing update, but a signature problem is not fixed by renaming the DLL.

“There was a problem starting xaudio2_9redist.dll”

This may be a loader, dependency or architecture problem rather than a simple missing-file problem. Confirm that the application is loading the file from its own directory and that the file matches the application’s architecture.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Why regsvr32 does not repair this error

Do not run:

regsvr32 xaudio2_9redist.dll

regsvr32 is intended for DLLs that expose registration entry points, commonly COM or ActiveX components. XAudio 2.9 is a runtime library loaded by the application through normal linking or DLL loading. It is not repaired by registering it in the Windows registry.

Microsoft documents the command’s purpose in regsvr32 documentation, while its XAudio deployment guidance explains the application-local loading model.

A failed regsvr32 attempt may produce an entry-point error and adds no useful repair. Restore the file through the application installer instead.

Is manually copying the DLL safe

Manual copying is safe only in a narrow situation:

• the source is the official application installation or Microsoft package;
• the destination is the exact application directory;
• the architecture matches;
• the application actually requests xaudio2_9redist.dll;
• the file has a trustworthy signature and provenance.

It is unsafe to download a replacement from a random DLL website. Those files may contain malware, may be the wrong architecture, may be old, or may fail because the real problem is a missing dependency, a launcher path or an antivirus quarantine event.

Do not:

• copy the file into System32;
• copy an x64 file into a 32-bit game;
• rename it casually to xaudio2_9.dll;
• overwrite the Windows xaudio2_9.dll component;
• copy it from another game;
• disable security software to force the application to start.

Some older applications or compatibility layers may explicitly request xaudio2_9.dll rather than xaudio2_9redist.dll. Renaming a redistributable file is not a general solution and should only be done when the application’s documented deployment specifically requires that name.

Fix 8: Use System Restore after a recent system change

System Restore is worth considering when the application worked immediately before a driver installation, system change or software update and normal application repair has failed.

1. Press Win + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select a restore point from before the problem began.
3. Review the affected programs.
4. Start the restore.
5. Restart Windows.
6. Test the application.

System Restore rolls back system files, settings and installed programs but normally does not remove personal files. Microsoft describes the process in its System Restore guidance.

Use this after verifying the application and checking quarantine, not as the first response to a single missing game DLL.

Prevention after the repair

Once the program launches again:

• Keep the game or application in its official launcher.
• Do not delete runtime folders during disk cleanup.
• Let updates complete before closing the launcher.
• Check quarantine after major game or anti-cheat updates.
• Keep Windows updated.
• Do not replace application DLLs with files from another installation.
• Keep a note of whether the application is 32-bit, 64-bit or ARM64.
• If you use modified files or unofficial installations, return to the vendor’s original files before troubleshooting.

The file may be used by PC games and middleware-based applications, including installations associated with games such as Halo: The Master Chief Collection. That demonstrates real use, not that one particular launcher or game is responsible for every occurrence.

Information to collect before asking for support

If the normal repair path fails, provide:

• the complete error text;
• any error code, such as a bad-image status;
• the Windows version and system architecture;
• the game or application name;
• the launcher being used;
• the exact executable path;
• the path where xaudio2_9redist.dll was found;
• whether the file has a valid digital signature;
• whether Windows Security or another antivirus quarantined it;
• whether the application is x86, x64 or ARM64;
• whether the failure occurs in the launcher, direct executable or anti-cheat executable;
• whether the error names xaudio2_9redist.dll or xaudio2_9.dll.

This information distinguishes a missing application file from a missing dependency, wrong architecture, blocked signature or incorrect launcher path.

FAQ

Is xaudio2_9redist.dll a virus

The legitimate file is a Microsoft XAudio 2.9 redistributable runtime. A file with that name can still be unsafe if it came from an untrusted download, so verify its source, path and digital signature.

Does Windows 10 or Windows 11 install xaudio2_9redist.dll

Usually no. Windows 10 and later include the operating-system xaudio2_9.dll component, while xaudio2_9redist.dll is normally shipped with the application that needs it.

Why is the file in System32 but the game still says it is missing

The game may need its application-local redistributable, may be loading a different executable, may require another architecture or may be unable to load a dependency. A file somewhere on the drive does not prove that the failing executable can use it.

Should I install DirectX June 2010

Not for this file alone. The June 2010 runtime supplies older DirectX components, including XAudio 2.7 files. Verify or reinstall the application that requests xaudio2_9redist.dll.

Should I install Visual C++ Redistributable

Only when another message identifies a Visual C++ runtime file or the application vendor specifically requires it. Visual C++ installation does not normally restore this XAudio DLL.

Should I run SFC and DISM

Run them when Windows components appear damaged or when the error involves the system xaudio2_9.dll. They do not generally restore a game’s application-local xaudio2_9redist.dll.

Should I use regsvr32

No. This XAudio runtime is not repaired by COM-style DLL registration.

Can I copy xaudio2_9redist.dll into System32

No. Microsoft’s deployment model is application-local. Restore the matching file beside the executable or in the application’s runtime directory through official repair or reinstall.

What is the safest fix

Verify or repair the game or application, check antivirus quarantine, and reinstall it from its official source if the file remains missing. Developers and administrators can use the matching architecture from Microsoft’s Microsoft.XAudio2.Redist package.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.