@cracker
@heapinfrimp
Glad to hear it. 
Thanks for informing us. 
This thread was posted yesterday and seems quite similar:
Since FxSound worked before this malfunction occurred for all users who reported it, and now even seems to work again in the case reported by @heapinfrimp, I added some instructions on how to update (or roll back) the driver of the affected device.