# ERR\_OUTPUT\_INIT on Windows, 2.02.05

**URL:** <https://qa.fmod.com/t/err-output-init-on-windows-2-02-05/18232>\
**Category:** Unity\
**Created:** [January 18, 2022, 8:51am UTC](https://qa.fmod.com/t/err-output-init-on-windows-2-02-05/18232 "2022-01-18T08:51:32Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![aguerin](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@aguerin](https://qa.fmod.com/u/aguerin)\
**Post date:** [February 17, 2022, 7:05pm UTC](https://qa.fmod.com/t/err-output-init-on-windows-2-02-05/18232/10 "2022-02-17T19:05:36Z")

</div>

Hello, sorry to intrude on your discussion Talecrafter, I have a few questions for Mathew.

> [@mathew](#):
>
> There was a recent patch that changed the behavior of IAudioClient that would explain the difference between 2.01.07 and 2.02.05 you are seeing.

In which version exactly was this change introduced? Can you add this information to the known issue section please?

> [@mathew](#):
>
> I will get this fixed to keep the fail behavior similar to 2.01 in which it’s only fatal if you choose to play on the faulty device.

Was the fix integrated in 2.02.05 Patch 1 (06/02/22)?

---

_[View the full topic](https://qa.fmod.com/t/err-output-init-on-windows-2-02-05/18232)._