Forum Discussion

AdamR's avatar
6 years ago
Solved

Unable to initialise Windows Audio. XAudio2Create(), 0x80040154

First time I've launched the game, I get an error popping up:

Unable to initialise Windows Audio. XAudio2Create(), 0x80040154

Screenshot

I'm going to take a guess that this revolves around a compatibility issue with Bluetooth based headphones. I've not found any recent details for this error code, but will look further and report back.

What I've tried so far:

  • Switching to a 3.5mm audio cable, and disconnecting the Bluetooth.
  • Disabling all other audio input/output devices, leaving only the 3.5mm headphones enabled.
  • Restarting the Windows Audio Endpoint Builder service. (And implicitly Windows Audio service.)
  • Closing down all other applications that produce audio where possible, particularly those likely to use WASAPI in exclusive mode. (Such as Foobar2000.)
  • Thanks to FruitF@ce leading me down the right path at my thread on the Steam game hub discussions I've resolved this.

    Looking further I downloaded the June 2010 DX9 runtime.

    1. Download directx_Jun2010_redist.exe
    2. Run it, then when prompted, choose somewhere to extract this. -- I'd suggest "C:\Users\[you]\Downloads\DX9Redist" or similar. (It has a lot of files and no root folder.)
    3. Once extraction is completed find "DXSETUP.exe in the path you chose and run that.
    4. Proceed with this installation.
    5. You can delete the folder you created for extraction once the installation has completed. -- Its quite big.

    This dependency really should have been enforced for Steam installations. Having a game published on Steam I know this is very much an option.

    @Developers to resolve this for everyone else via Steamworks:

    1. Visit the App Admin section for your game in SteamWorks
    2. Installation tab then Redistributables.
    3. Under the Windows heading then DirectX heading, tick the June 2010 option.
    4. Publish this change via the Publish tab. -- You can do a lite publish for this.

    This issue has likely not been a problem for many others if they've already got a different game installed that also had the June 2010 DirectX redistributable as an installation dependency. -- This was not the case for me.

5 Replies

  • I did also look for updated DirectX runtimes, but the installer for that claimed I already had a newer version installed.
  • Thanks to FruitF@ce leading me down the right path at my thread on the Steam game hub discussions I've resolved this.

    Looking further I downloaded the June 2010 DX9 runtime.

    1. Download directx_Jun2010_redist.exe
    2. Run it, then when prompted, choose somewhere to extract this. -- I'd suggest "C:\Users\[you]\Downloads\DX9Redist" or similar. (It has a lot of files and no root folder.)
    3. Once extraction is completed find "DXSETUP.exe in the path you chose and run that.
    4. Proceed with this installation.
    5. You can delete the folder you created for extraction once the installation has completed. -- Its quite big.

    This dependency really should have been enforced for Steam installations. Having a game published on Steam I know this is very much an option.

    @Developers to resolve this for everyone else via Steamworks:

    1. Visit the App Admin section for your game in SteamWorks
    2. Installation tab then Redistributables.
    3. Under the Windows heading then DirectX heading, tick the June 2010 option.
    4. Publish this change via the Publish tab. -- You can do a lite publish for this.

    This issue has likely not been a problem for many others if they've already got a different game installed that also had the June 2010 DirectX redistributable as an installation dependency. -- This was not the case for me.

  • I did post a working solution to this, but it's been deleted as apparent spam. Oh well, you can just Google the thread title, find the exact same one on this game's Steam hub discussions, and seem my answer there.

    Classic EA.

  • Carbonic's avatar
    Carbonic
    Hero+
    6 years ago

    The spamfilter loved you. I told EA, they got it fixed, so now I can think you are awesome for posting the solution instead @AdamR  🙂

  • AdamR's avatar
    AdamR
    6 years ago

    @CarbonicThanks for resolving that. 🙂 Glad I could help.
    Currently enjoying this game very much indeed!

    The particular sound output device (Bluetooth vs 3.5mm analogue) didn't matter in the end.

About Command & Conquer Franchise Discussion

Chat about your favorite games in the Command and Conquer franchise and get help from the player community.13,551 PostsLatest Activity: 3 days ago