# Unable to build banks because the build output directory does not exist

**URL:** <https://qa.fmod.com/t/unable-to-build-banks-because-the-build-output-directory-does-not-exist/22674>\
**Category:** FMOD Studio\
**Created:** [March 8, 2025, 10:10pm UTC](https://qa.fmod.com/t/unable-to-build-banks-because-the-build-output-directory-does-not-exist/22674 "2025-03-08T22:10:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael\_steinkellner](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/michael_steinkellner/32/1222_2.png) [@michael\_steinkellner](https://qa.fmod.com/u/michael_steinkellner)\
**Post date:** [March 8, 2025, 10:10pm UTC](https://qa.fmod.com/t/unable-to-build-banks-because-the-build-output-directory-does-not-exist/22674/1 "2025-03-08T22:10:31Z")

</div>

Hey!

I got a new Macbook with MacOS Sequoia and now I can’t access my usual build folder anymore. I can navigate to the folder with the “Browse” button, but FMOD keeps saying that the folder does not exist.

 ![Screenshot 2025-03-08 at 23.05.31](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/d/dd55f9b506e7d0f91dee10e3e8e5529bc835ee95.png)

 ![Screenshot 2025-03-08 at 23.05.15](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/e/eb38d5409e124faecc22aabca4b646433fde3103.png)

Thanks for your help!  
Michael

---

<div class="post-metadata">

**Author:** ![michael\_steinkellner](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/michael_steinkellner/32/1222_2.png) [@michael\_steinkellner](https://qa.fmod.com/u/michael_steinkellner)\
**Post date:** [March 8, 2025, 10:36pm UTC](https://qa.fmod.com/t/unable-to-build-banks-because-the-build-output-directory-does-not-exist/22674/2 "2025-03-08T22:36:55Z")

</div>

Is this a version problem? It works with FMOD 2.3 but not with 2.2

---

<div class="post-metadata">

**Author:** ![joseph](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/joseph/32/264_2.png) [@joseph](https://qa.fmod.com/u/joseph)\
**Post date:** [March 12, 2025, 6:22am UTC](https://qa.fmod.com/t/unable-to-build-banks-because-the-build-output-directory-does-not-exist/22674/3 "2025-03-12T06:22:23Z")

</div>

I’m afraid I haven’t been able to reproduce this issue; when I attempt it here, the folder is found without problems.

Is the target directory on a network drive, or a removeable drive? In some cases, the limited or intermittent bandwidth associated with such devices can prevent FMOD Studio from being able to find them.

Is the target directory subject to some cloud syncing service such as Dropbox? If so, try disabling that service or selecting a different directory that isn’t subject to cloud synchronization. Cloud syncing services can sometimes block FMOD Studio from correctly reading or writing to files in the locations they synchronize.

---

<div class="post-metadata">

**Author:** ![michael\_steinkellner](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/michael_steinkellner/32/1222_2.png) [@michael\_steinkellner](https://qa.fmod.com/u/michael_steinkellner)\
**Post date:** [March 13, 2025, 11:17am UTC](https://qa.fmod.com/t/unable-to-build-banks-because-the-build-output-directory-does-not-exist/22674/4 "2025-03-13T11:17:20Z")

</div>

Thanks for looking into that and providing some possible solutions. The target directory is on an internal drive. Interestingly it works if I leave the output directory field blank. Then it builds into the project folder (which is in a folder synced with Google Drive).

I only have the error in 2.2.27, but it works in 2.3.6 so I consider updating it.

---

<div class="post-metadata">

**Author:** ![joseph](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/joseph/32/264_2.png) [@joseph](https://qa.fmod.com/u/joseph)\
**Post date:** [March 20, 2025, 4:37am UTC](https://qa.fmod.com/t/unable-to-build-banks-because-the-build-output-directory-does-not-exist/22674/5 "2025-03-20T04:37:46Z")

</div>

That is strange. I can’t find any change or bug fix in our records that would explain the change in behavior between those versions, and I still can’t reproduce the issue when I attempt to do so here.

As such, I can only recommend that if you have found a workaround that works, you should consider using that workaround.
