# Known issues 2.01.13 and 2.02.04

**URL:** https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374
**Category:** Known Issues
**Created:** [February 17, 2022, 9:58pm UTC](https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374 "2022-02-17T21:58:40Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)
#### Post date: [February 17, 2022, 9:58pm UTC](https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374/1 "2022-02-17T21:58:40Z")

</div>

**Issue**  
Initialization error on Windows (FMOD\_ERR\_OUTPUT\_INIT) when initializing either the FMOD Core System or FMOD Studio System. Caused by enumerating a buggy audio driver’s details.

**Solution**  
This issue has been fixed in 2.01.15 and 2.02.06 which at the time of posting is not yet released.

**Workaround**  
The user can update the drivers for the problematic device, however it’s hard to know which audio device is causing the issues (it’s not necessarily the default device). A simpler solution is to disable all audio devices except the one you intend to use for playback. If the issue persists, then update the drivers for the remaining device.

---

<div class="post-metadata">

### Author: ![doomedbunnies](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/doomedbunnies/32/3115_2.png) [@doomedbunnies](https://qa.fmod.com/u/doomedbunnies)
#### Post date: [February 18, 2022, 12:07am UTC](https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374/2 "2022-02-18T00:07:55Z")

</div>

We have a couple players who are affected by this bug. I’ll pass the workaround along to them, but do you have an estimate about when we’re likely to see the 2.02.06 update available for download? (is it likely days, weeks, or months away? If it’s close, I’ll likely recommend they just wait for us to upgrade to the new FMOD release rather than try to figure out driver updates)

---

<div class="post-metadata">

### Author: ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)
#### Post date: [February 18, 2022, 12:54am UTC](https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374/3 "2022-02-18T00:54:10Z")

</div>

The release should be available in a week or two depending on how the remaining blockers go.

---

<div class="post-metadata">

### Author: ![Batsphinx](https://avatars.discourse-cdn.com/v4/letter/b/e36b37/32.png) [@Batsphinx](https://qa.fmod.com/u/Batsphinx)
#### Post date: [March 15, 2022, 11:17pm UTC](https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374/4 "2022-03-15T23:17:42Z")

</div>

Any news on when the 2.02.06 release will be Mathew?

I believe our guys are also having an issue with the error described here.

---

<div class="post-metadata">

### Author: ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)
#### Post date: [March 16, 2022, 1:23am UTC](https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374/5 "2022-03-16T01:23:24Z")

</div>

The release has been approved and is being readied on the website right now, so it should go live today.

---

<div class="post-metadata">

### Author: ![Batsphinx](https://avatars.discourse-cdn.com/v4/letter/b/e36b37/32.png) [@Batsphinx](https://qa.fmod.com/u/Batsphinx)
#### Post date: [March 16, 2022, 9:57am UTC](https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374/6 "2022-03-16T09:57:12Z")

</div>

Perfect timing. Many thanks - we will pop it out in a hotfix. Our support team are happy to hear this 🙂
