Volume down won't work

[ayushverma966avva-ops]

So I found this bug that when I launch windhawk, volume down button won't work and upon closing the app, button works fine. I tested this with mods loaded and removed and with my mouse which has dedicated vol down button and same issue happens. Any fix for that?

[m417z]

Which mods are you using? Does the issue occur if all mods are disabled?

[ayushverma966avva-ops]

I have checked and I can confirm that even when all the mods are disabled, volume down won't work when Windhawk is running. When I close it and choose the option of not starting in next boot, volume down works fine and when again I open it, same issue starts happening.

…

On Wed, Sep 10, 2025, 1:19 AM Michael Maltsev ***@***.***> wrote: Which mods are you using? Does the issue occur if all mods are disabled? — Reply to this email directly, view it on GitHub <#643 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BXEA2TFLDGT64IQMAU352ZD3R4VN5AVCNFSM6AAAAACGAGU4X2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZVGU2DKMA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[m417z]

I don't know why it could affect that. It works on my computer and it works for other users. I also don't know how to troubleshoot it, the best thing I can think of is to take Windhawk and start removing parts of the code, which is a time consuming process, especially since each time I'll have to package a test Windhawk version and upload it for you to test.

If you have a way to reproduce the problem, let me know. It will be much easier for me to understand the problem if I can make it happen on my computer.

[ayushverma966avva-ops]

Okay so I dig deeper and found that there is a software in asus laptops called fn hotkeys and somehow that was getting messed up, but luckily I use G-Helper instead of Armoury crate so I deleted the hotkey app and set those from G-Helper and everything works fine now. Sorry for disturbing you man! Cheers

…

On Wed, Sep 10, 2025 at 11:13 AM Michael Maltsev ***@***.***> wrote: I don't know why it could affect that. It works on my computer and it works for other users. I also don't know how to troubleshoot it, the best thing I can think of is to take Windhawk and start removing parts of the code, which is a time consuming process, especially since each time I'll have to package a test Windhawk version and upload it for you to test. If you have a way to reproduce the problem, let me know. It will be much easier for me to understand the problem if I can make it happen on my computer. — Reply to this email directly, view it on GitHub <#643 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BXEA2THSSQVXYK3ARARVJS33R63AJAVCNFSM6AAAAACGAGU4X2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZVHA3DIOA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[m417z]

No problem, I'm glad that it works now. I wonder why there was a conflict. I don't have an Asus computer, so I can't check that. If you find a way to reproduce the problem with a non-Asus computer, let me know and I'll take a look.