xaudio2_9.dll Missing: Diagnose and Repair Windows Game Launches

If xaudio2_9.dll is missing, Windows cannot load the XAudio2.9 game-audio runtime required by the affected program. The correct repair depends on whether the file is missing from the game folder, damaged in Windows, quarantined by antivirus, or unavailable because the operating system is too old.

Before changing anything, note:

• Which game or application displays the error.
• Whether it fails immediately or only after an update, mod installation, driver change, or antivirus detection.
• Whether the message says the file is missing, cannot be loaded, is not designed to run on Windows, or reports an audio initialization failure.
• Whether the named path points to the game folder or to C:\Windows\System32.
• Whether the application is 32-bit, 64-bit, or ARM64.
• Whether other games have the same problem.

Start with the affected application’s repair function. On Windows 10 and Windows 11, that is usually the fastest safe fix because many games ship an application-local XAudio2 runtime.

As an Amazon Associate I earn from qualifying purchases.

What xaudio2_9.dll does

xaudio2_9.dll is Microsoft’s XAudio2 version 2.9 runtime. XAudio2 is a low-level native audio API used by Windows games and applications for music, dialogue, sound effects, mixing, and other audio processing. Microsoft documents XAudio2.9 as an inbox component of Windows 10 and later, where the system file is named XAUDIO2_9.DLL. A redistributable version is available for Windows 7 SP1, Windows 8, Windows 8.1, Windows 10, and Windows 11. Microsoft’s XAudio2 version documentation explains the difference between the available XAudio2 releases.

The program may fail before displaying its own interface because Windows resolves required DLLs while starting the executable. If the loader cannot find a required DLL, cannot load it, or finds a binary for the wrong architecture, the application may stop immediately.

The similarly named files are not automatically interchangeable:

• xaudio2_7.dll belongs to the older XAudio2.7 runtime.
• xaudio2_8.dll is a different API release.
• xaudio2_9redist.dll is the app-local redistributable filename used by Microsoft’s developer package.
• xaudio2_9.dll is the normal Windows 10/11 system filename.

A missing xaudio2_9.dll is therefore not automatically a Visual C++ problem, a .NET problem, or a sound-driver problem.

First identify where the file is missing

The location named in the error changes the repair path.

If the error names the game or application folder

A local file may have been deleted, quarantined, damaged, or replaced by a mod. The application folder is searched before the Windows system directories in the standard DLL search order, so an incorrect local copy can override a healthy Windows copy. Microsoft’s DLL search-order documentation describes this behavior.

Repair the application first. Do not copy a random DLL into the folder.

If the error names System32

On 64-bit Windows, the normal 64-bit system path is:

%windir%\System32\XAudio2_9.dll

The 32-bit system copy is normally:

%windir%\SysWOW64\XAudio2_9.dll

The confusing names are part of Windows’ file-system redirection rules: System32 contains 64-bit system files on 64-bit Windows, while SysWOW64 contains 32-bit system files. Microsoft’s File System Redirector documentation explains the architecture behavior.

A missing or damaged system copy calls for Windows Update, DISM, and SFC rather than a downloaded replacement.

If the file exists but the program still fails

The file may be the wrong architecture, corrupted, blocked by security software, shadowed by a bad local copy, or missing one of its own dependencies. A 0xc000007b or “not designed to run on Windows” message usually points toward binary compatibility or a bad image rather than simple absence.

Fix 1: Verify or repair the game

This is the safest first repair when one game is affected, especially after an update or mod installation.

Steam

1. Open 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 operation to finish.
8. Restart Steam and launch the game again.

Steam may reacquire missing or damaged files. If antivirus removed an app-local DLL, verification may restore it, but the file may be quarantined again unless the security detection is reviewed.

Epic Games Launcher

1. Open Epic Games Launcher.
2. Open Library.
3. Select the three dots beside the game.
4. Select Manage.
5. Select Verify.
6. Wait for verification to complete.
7. Launch the game again.

Other launchers

Look for a menu named Verify, Repair, Scan, or Check files. If the launcher has no repair option, uninstall and reinstall the game from its official launcher after checking antivirus quarantine.

How to tell whether this worked

The game should reach its normal startup screen without the missing-DLL message. If verification reports repaired files but the same error returns immediately, check Protection History before reinstalling. A security product may be removing the file again.

If the error names a file in the Windows system directory rather than the game folder, launcher verification alone is unlikely to repair the system component.

Fix 2: Check antivirus quarantine

Antivirus software can remove an application-local DLL after a game update or after a modified executable changes the files that are scanned. Treat this as a possibility, not as proof that the detection is a false positive.

For Microsoft Defender:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Protection history.
4. Expand the detection associated with the game or application.
5. Inspect the original file path.
6. Check the publisher and digital signature when available.
7. Restore or allow the file only if its source is trusted.
8. Verify the game files afterward.

Microsoft warns that a restored file is scanned again. Allowing a file should be reserved for a known-safe file from Windows or a trusted application installation. Microsoft’s Protection History guidance provides the supported Defender path.

Do not broadly disable antivirus protection or create a permanent exclusion for an entire games folder just to suppress the message. If the file came from an unofficial mod or an unknown archive, remove it and reinstall the application from its official source.

Fix 3: Install Windows updates

Windows 10 and Windows 11 include XAudio2.9 as a system component. If the system copy is missing or damaged, pending cumulative updates may replace or service it.

Windows 11

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

Windows 10

1. Open Start.
2. Select Settings.
3. Select Update & Security.
4. Select Windows Update.
5. Select Check for updates.
6. Install available updates.
7. Restart Windows.
8. Test the application again.

Windows 10 support ended on October 14, 2025. If the computer can run Windows 11, upgrading is the more sustainable system repair path. Microsoft’s Windows Update instructions cover the supported update process.

Do not assume that installing every optional driver update will replace xaudio2_9.dll. The goal here is to bring Windows’ protected components to a consistent, supported state.

Fix 4: Repair Windows with DISM and SFC

Use this path when:

• The error names System32 or SysWOW64.
• Multiple programs report missing or damaged system DLLs.
• The issue began after a failed update, crash, or storage problem.
• The file is present but produces a bad-image error.
• Windows Update did not resolve the problem.

Microsoft recommends running DISM before SFC because DISM can repair the component store that SFC uses as a source.

Outbyte PC Repair can reduce the manual work of hunting through system errors and repeating SFC or DISM without knowing what changed; its free scan shows what it finds, while repair is performed by the full version. It is optional, and when the file belongs to a particular game, verifying or reinstalling that game remains the definitive application repair.

Run DISM

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the command to complete.
2. Restart if Windows requests it.

A successful completion indicates that DISM repaired or confirmed the Windows component store. It does not by itself prove that the game’s local copy is correct.

Run SFC

In the same elevated Command Prompt, run:

sfc /scannow

Wait until verification reaches 100 percent. The result will say whether Windows found no integrity violations, repaired corrupted files, or found files it could not repair.

Restart Windows after SFC completes, then launch the affected program.

Run a targeted SFC check

If you know the affected system path, use a targeted scan:

sfc /scanfile=C:\Windows\System32\XAudio2_9.dll

For a 32-bit system copy on 64-bit Windows, use:

sfc /scanfile=C:\Windows\SysWOW64\XAudio2_9.dll

Replace C:\Windows if Windows is installed in a different directory. The path must match the architecture and the location named by the application or diagnostic message. Microsoft’s SFC command documentation describes the targeted /scanfile option.

If SFC says it cannot repair the file

Run DISM again after installing pending updates. If Windows Update cannot provide repair files, Microsoft documents using installation media that matches the installed Windows edition, language, and build:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Replace C:\RepairSource\Windows with the correct repair-source path. Then run:

sfc /scannow

Do not use a random downloaded xaudio2_9.dll as a repair source. A file from another Windows build may have a different servicing state or architecture. Microsoft’s repair guidance for missing or corrupted system files explains the repair-source approach.

Fix 5: Remove an incorrect local DLL

If the game folder contains a manually copied DLL, an old mod, or a file named similarly to the required runtime, it can take precedence over the Windows copy.

1. Close the game and its launcher.
2. Open the game’s installation folder.
3. Look for manually added files such as xaudio2_9.dll, xaudio2_9redist.dll, or files installed by a sound or compatibility mod.
4. Move suspicious files to a temporary folder rather than deleting them immediately.
5. Remove or disable unofficial mods according to the game’s normal mod-management process.
6. Run the launcher’s file verification.
7. Start the game again.

Do not rename xaudio2_9redist.dll to xaudio2_9.dll as a general repair. The Microsoft redistributable is designed for application-local deployment and has its own filename and loading behavior. A rename is an application-specific workaround only when the developer explicitly documents it.

Fix 6: Match the application architecture

The DLL must match the application that loads it.

• A 32-bit program requires an x86 runtime.
• A 64-bit program requires an x64 runtime.
• An ARM64 program requires an ARM64 runtime where supported.

A 64-bit Windows installation can run both 32-bit and 64-bit applications, but those applications do not load the same system-directory copy. Installing or copying an x86 DLL beside a 64-bit executable commonly causes a bad-image error or 0xc000007b.

Check the application’s official system requirements or package documentation. If the error appeared after manually replacing a DLL, remove the replacement and verify or reinstall the application. If only one edition of a game fails while another works, compare the executable architecture and the files supplied by that edition.

The Microsoft XAudio2 redistributable documentation covers x86 and x64 libraries and also lists ARM64 support for Windows 11 on ARM. Microsoft’s XAudio2 redistributable guide also explains that developers should deploy the redistributable beside the application executable and link against the appropriate import library.

Fix 7: Use the supported XAudio2 redistributable on older Windows

XAudio2.9 is included in Windows 10 and Windows 11. It is not an inbox component on Windows 7 SP1, Windows 8, or Windows 8.1.

Windows version	XAudio2.9 status	Appropriate path
Windows 11	Included as XAUDIO2_9.DLL	Update and repair Windows if damaged
Windows 10	Included as XAUDIO2_9.DLL	Update and repair Windows if damaged
Windows 8.1	Not inbox	Upgrade or use the application’s supported redistributable
Windows 8	Not inbox	Upgrade or use the application’s supported redistributable
Windows 7 SP1	Not inbox	Upgrade or use the application’s supported redistributable
Windows XP or Vista	Not supported by the documented XAudio2.9 redistributable	Use a supported operating system or application version

For developers and application distributors, Microsoft provides the Microsoft.XAudio2.Redist NuGet package. Its redistributable DLL is named xaudio2_9redist.dll, not necessarily xaudio2_9.dll. It is primarily a developer package rather than a normal consumer installer.

For an ordinary player, the correct approach on Windows 7, 8, or 8.1 is usually to upgrade Windows or obtain the runtime through the game developer’s supported installer. Do not extract a DLL from a NuGet package and place it in System32 unless the application developer specifically instructs you to deploy that exact package and architecture beside the executable.

Windows 7 SP1 may also require Microsoft’s SHA-2 support update before the signed redistributable can be installed correctly. Do not treat an unsigned DLL from an unknown source as an equivalent substitute.

Do not confuse XAudio2.9 with the DirectX June 2010 runtime

The phrase “DirectX problem” is too broad to identify the correct package.

The DirectX End-User Runtimes June 2010 package installs legacy components, including XAudio2.7. It does not install the Windows 10/11 system xaudio2_9.dll. Microsoft’s DirectX End-User Runtimes June 2010 page identifies that legacy package.

Installing the June 2010 runtime can still be appropriate when the same game separately reports a missing xaudio2_7.dll, d3dx9_*.dll, or another legacy DirectX component. It is not the decisive fix for a genuine XAudio2.9 dependency.

Likewise:

• Visual C++ Redistributables supply files such as VCRUNTIME140.dll and MSVCP140.dll, not xaudio2_9.dll. Microsoft’s supported Visual C++ downloads are appropriate when the error names a C++ runtime.
• .NET repair is relevant only when the application reports a .NET installation or framework problem. Microsoft’s .NET Framework repair guidance covers that separate issue.
• Windows Features does not provide a checkbox that installs XAudio2.9.

To inspect Windows Features:

1. Press Win+R.
2. Enter:

optionalfeatures

1. Press Enter.
2. Review the available components.

Do not toggle random legacy features to repair xaudio2_9.dll. DirectPlay and other compatibility features address different APIs.

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

Fix 8: Update audio or graphics drivers when the symptom is not a missing file

A sound-driver repair is relevant when the message says “Couldn’t create XAudio2,” when there is no sound, or when the game crashes during audio-device initialization without reporting a missing DLL. It does not normally reinstall the protected Windows XAudio2.9 component.

Update or reinstall an audio driver

1. Right-click Start.
2. Select Device Manager.
3. Expand Sound, video and game controllers.
4. Right-click the audio device.
5. Select Update driver.
6. Select Search automatically for drivers.
7. Restart Windows.
8. Test the game.

If the problem began immediately after a driver update:

1. Open Device Manager.
2. Expand Sound, video and game controllers.
3. Right-click the audio device.
4. Select Properties.
5. Open the Driver tab.
6. Select Roll Back Driver if available.
7. Restart Windows.

If Windows cannot restore the driver:

1. Right-click the audio device in Device Manager.
2. Select Uninstall device.
3. Confirm the removal.
4. Restart Windows.
5. Allow Windows to reinstall the device.

Outbyte Driver Updater can remove the guesswork of checking many hardware entries manually: its free scan shows which drivers are outdated, while driver installation is performed by the full version. It is optional, and a missing xaudio2_9.dll still requires application or Windows repair when the DLL itself is the problem.

Update a graphics driver when appropriate

Update the display driver when the game fails during general initialization, reports a graphics or device error alongside the audio message, or began failing after a Windows update. In Device Manager:

1. Expand Display adapters.
2. Right-click the graphics device.
3. Select Update driver.
4. Select Search automatically for drivers.
5. Restart Windows.

A graphics-driver update will not normally restore xaudio2_9.dll. Keep the two problems separate so an unrelated driver installation does not replace the more direct application or system repair.

regsvr32 does not repair XAudio2.9

Do not run this as a supposed fix:

regsvr32 XAudio2_9.dll

regsvr32 is intended for self-registering COM and ActiveX DLLs that expose DllRegisterServer. XAudio2.9 is loaded through the XAudio2 API or ordinary DLL loading. It is not repaired through COM registration, so the command may produce an error stating that DllRegisterServer was not found.

Microsoft documents XAudio2 creation and loading through the XAudio2 API rather than registration. Microsoft’s regsvr32 documentation explains the command’s actual purpose.

Fix 9: Use System Restore after a recent system change

System Restore is appropriate when the problem began immediately after a Windows update, driver installation, system utility, or other software change and ordinary repair did not help.

1. Press Win+R.
2. Enter:

rstrui.exe

1. Press Enter.
2. Select a restore point from before the problem began.
3. Select Scan for affected programs if available.
4. Review the changes.
5. Finish the restore.
6. Restart Windows and test the application.

System Restore rolls back system files, settings, and installed programs but normally does not remove personal files. Microsoft’s System Restore guidance explains the recovery process.

If there is no suitable restore point, continue with a Windows repair installation rather than downloading a replacement system DLL.

Fix 10: Repair Windows when DISM and SFC still fail

If DISM and SFC cannot repair the component, and multiple Windows programs are failing, back up important data before continuing.

The remaining escalation path is:

1. Use System Restore if a suitable point exists.
2. Perform an in-place Windows repair using installation media that matches the installed edition, language, and build.
3. Retest the application.
4. Reinstall Windows only after backing up personal files and confirming that less disruptive repairs have failed.

A full or offline Microsoft Defender scan is also appropriate when multiple system DLLs disappear, files repeatedly reappear or vanish, or Defender reports additional threats. Malware or storage damage is not the usual explanation for one game’s missing file, but it becomes more plausible when failures affect the entire system.

Common error messages and what they suggest

“The program can’t start because XAudio2_9.dll is missing”

Start with application verification or repair. If the error names a Windows system path or affects several applications, continue with Windows Update, DISM, and SFC.

“Couldn’t create XAudio2”

This can indicate an audio-device, driver, permissions, or runtime initialization problem. Check whether the DLL is actually missing before replacing anything. Update or reinstall the audio driver if the problem is accompanied by no sound or device detection failures.

“The file is not designed to run on Windows”

Check architecture and file origin. Remove manually copied DLLs, verify the application, and run DISM and SFC if the named path is in Windows. This wording commonly indicates a bad image or incompatible binary, not merely a missing file.

0xc000007b

Check for a 32-bit and 64-bit mismatch. Remove unofficial local DLLs and verify the application. Do not install several unrelated runtime packages at random.

0xc000012f

This is commonly presented as a bad-image error. Confirm the path named in the message, repair the application if the path is local, and run Windows component repair if it names the system directory.

Why random DLL downloads are unsafe

Downloading xaudio2_9.dll from an unknown DLL website can introduce:

• Malware or a modified binary.
• The wrong Windows build.
• The wrong architecture.
• A file with missing dependencies.
• A replacement that is rejected by Windows servicing.
• A local DLL that masks the real application or system problem.

It can also make diagnosis harder because the application directory takes precedence over the Windows system directory. Use Windows Update, DISM, SFC, the application’s own verification process, or a Microsoft-supported redistributable instead.

There is no single current file size or universal file version that applies to every Windows installation. Windows services system files according to the installed Windows build and cumulative updates. Do not use an old file listing as a specification for every computer.

Frequently asked questions

Is xaudio2_9.dll part of DirectX?

It is part of Microsoft’s XAudio2 game-audio API, which is associated with DirectX technologies. On Windows 10 and Windows 11, XAudio2.9 is included as a Windows system component. The June 2010 DirectX End-User Runtime supplies older components, including XAudio2.7, and should not be treated as the universal XAudio2.9 fix.

Is xaudio2_9.dll part of Visual C++?

No. Visual C++ runtime packages do not supply this DLL. Install Visual C++ only when the error names a Visual C++ runtime file.

Is it a .NET file?

No. XAudio2.9 is a native Windows audio runtime. .NET repair applies to separate .NET installation or framework errors.

Should I put the file in System32?

No. Do not download an arbitrary DLL and copy it into System32. Windows system components should be repaired through Windows Update, DISM, and SFC. An application developer may deliberately deploy Microsoft’s redistributable beside its executable, but that is different from replacing a protected system file.

Should I register it with regsvr32?

No. XAudio2.9 is not a self-registering COM DLL. regsvr32 does not repair it.

Why does the file exist but the game still fail?

The local copy may be corrupt or may shadow the system copy. The architecture may be wrong, antivirus may be blocking it, or another dependency may be missing. Remove unofficial local replacements, verify the application, and check the exact path and error code.

Can I rename xaudio2_9redist.dll?

Not as a universal fix. The redistributable filename and loading method are application-specific. Rename it only if the application developer explicitly documents that deployment.

Does a sound-driver reinstall fix a missing DLL?

Usually not. Driver repair helps when the problem is no sound, an unavailable audio device, or an XAudio initialization failure without a missing-file message. It does not normally reinstall the Windows XAudio2.9 component.

What information should I provide when asking for support?

Include:

• The exact error wording and status code.
• The application or game name.
• The path named in the message.
• Your Windows version.
• Whether the application is 32-bit, 64-bit, or ARM64.
• Whether verification, Windows Update, DISM, and SFC changed the result.
• Whether antivirus quarantined a file.
• Whether the problem affects one application or several.

That information distinguishes an application repair from a Windows component repair and avoids replacing the wrong runtime.

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.