# 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:** 11

<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:48pm UTC](https://qa.fmod.com/t/err-output-init-on-windows-2-02-05/18232/11 "2022-02-17T21:48:09Z")

</div>

> [@aguerin](#):
>
> In which version exactly was this change introduced?

The change in behavior was introduced in 2.01.13 and 2.02.04.

> [@aguerin](#):
>
> Can you add this information to the known issue section please?

Added: [Known issues 2.01.13 and 2.02.04](https://qa.fmod.com/t/known-issues-2-01-13-and-2-02-04/18374)

> [@aguerin](#):
>
> Was the fix integrated in 2.02.05 Patch 1 (06/02/22)?

No, the patch1 release was an emergency fix for a single critical issue.  
The issue discussed in this thread is fixed in the upcoming 2.01.15 and 2.02.06 releases.

---

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