# Version 1.1.17.0 is now live

**URL:** <https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927>\
**Category:** Info and Announcements\
**Created:** [May 24, 2023, 1:14am UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927 "2023-05-24T01:14:29Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![CriticalHit\_NL](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/criticalhit_nl/32/2452_2.png) [@CriticalHit\_NL](https://forum.fxsound.com/u/CriticalHit_NL)\
**Post date:** [May 24, 2023, 11:23pm UTC](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927/9 "2023-05-24T23:23:12Z")

</div>

Happy to see a new version release! This is awesome!  
The upgrade from version 1.1.16.0 went smoothly here on Windows 10 22H2 with Realtek ALC4082 (Logitech Z906, analog) & Logitech G35 7.1

Unfortunately I do notice the bug from below link is not yet fixed in this version:

> [@Memory leak in audiodg.exe with FXSound 1.1.16.0](https://forum.fxsound.com/t/memory-leak-in-audiodg-exe-with-fxsound-1-1-16-0/1445):
>
> I’m here to report an issue that appears to only play when FXSound is running, currently version 1.1.16.0 and this has been happening for months and on two different systems. This issue mostly appears to happen when the system has been running for a prolonged period of time but it is random. Usually with 1+ day uptimes of operating system. The problem is that the system process audiodg.exe starts consuming considerable amounts of memory, sometimes even more than 1GB until FXSound is closed and…

@bvijay @james since it was not in the releasenotes I do not think a fix was yet implemented for this, is this true?  
If so, is there an idea when a fix for this issue could be released?

Thank you in advance and congratulations on the new release!

Keep it up. 😃

---

_[View the full topic](https://forum.fxsound.com/t/version-1-1-17-0-is-now-live/1927)._
