Unable to Install FMOD Studio 2.03 on Windows 10

I am unable to install FMOD on my Windows 10 machine (22H2).

I have tried the 64-bit Windows installer for 2.03, 2.02 and 2.01.11. I have even tried a 32-bit installer. None of them work for me and all fail with the same error:

I have tried the following:

  • Running as administrator
  • Adding an exception for the program in Windows Defender
  • Running in compatibility mode
  • Disabling UAC
  • Installing on C and D drive (both drives have plenty of space left)

None of these things have worked and all have resulted in the same error which is very frustrating, The application itself does seem to be installed and it seems to be an example project that is failing to be installed (I’m not sure why it would be trying to install it in my documents folder anyway rather than alongside the application?). Unfortunately the application won’t run with the installation aborted part way so I’m assuming something else it needs doesn’t get installed when aborted.

Could someone provider me information on what I need to do to get this working? I don’t usually have issues like this installing software but assume there is something specific about my setup that is causing this? I have seen the following links:

that seem to be describing the same issue but unfortunately no resolutions were posted. It looks like it could be related to firewall settings but as far as I’m aware I have added an exemption for this installer to the firewall.

If anyone could provide some help that would be much appreciated.

Thanks,
Tom

Ok so I figured this out and it was a firewall issue, but it was a setting in a different place. I was in focus mode and did not see that the following notification had shown up in Action Centre:

Clicking on this took me to a section in the Windows Security settings asking me to approve this specific access for this app. Selecting Allow on Device and then rerunning the installer solved the issue for me.

I still think it would be nice if the examples installed alongside the application rather than in the Documents folder - ideally I would not want to give access to a 3rd party installer for my Documents folder.

1 Like

Hi,

Thank you for providing the solution. I will make a task to investigate a better way to include the solution project. Thank you for your suggestions.

1 Like

We stopped shipping the examples in the application directory due to Windows not usually having write access to that location. It seems now there are additional issues with the documents directory. We’ve encountered similar issues on Mac where the application bundle cannot be written to due to code signing integrity.

Our plan is to move to shipping the examples as a package (.fspackage) within the application directory/bundle that you can unpack to a chosen location. This means you will always have a pristine copy of the examples available to unpack and you can choose where it goes at runtime.