search

ayufan / steam-deck-tools

(Windows) Steam Deck Tools - Fan, Overlay, Power Control and Steam Controller for Windows
https://steam-deck-tools.ayufan.dev
Other
867 stars 63 forks source link

Performance Overlay: Failed to acquire global mutex #176

Open darkelement1987 opened 5 months ago

darkelement1987 commented 5 months ago

image

Upon booting to desktop (Win 11)

I followed all steps in the install notes and left everything except FPS cap to default (limited to 60) and i'm using an external monitor if that matters?

-edit-

After some googling someone said check it bios is not in storage mode. That is not the case

darkelement1987 commented 5 months ago

image

Same for Fan Control

elmolini commented 4 months ago

yep I have the same problem.. have you found any solution?

darkelement1987 commented 4 months ago

No i have not unfortunately

Op zo 3 mrt 2024 13:15 schreef Marc Molina @.***>:

yep I have the same problem.. have you found any solution?

— Reply to this email directly, view it on GitHub https://github.com/ayufan/steam-deck-tools/issues/176#issuecomment-1975140984, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBGH66URKHUS4ZSKYIEIR3YWMH55AVCNFSM6AAAAABDLVCYBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGE2DAOJYGQ . You are receiving this because you authored the thread.Message ID: @.***>

a13xde commented 4 months ago

same Problem here, could this be a problem with a new firmware version ?

anejolov commented 4 months ago

Hello, it happens after one of the recent windows updates. Try to uninstall updates one by one.

Phane7 commented 4 months ago

I tried uninstalling updates one by one but ended up installing everything that I could and had no luck until the last update I uninstalled downgraded me from Windows 11 23H2 back to 22H2, then the issue went away. Reinstalling all the updates that were available still left me on 22H2 but the issue seems to be gone for now. I don't know if anyone is looking into this issue, but a fix would be appreciated so that I can go back to 23H2 when Windows prompts me again without worrying.

ColdThunder11 commented 4 months ago

This problem olny appears when start with windows. Maybe some task run slower after a windows update lead to program can not finish init within origin global mutex timeout? I don't konw actually why. However, just increase GLOBAL_DEFAULT_TIMEOUT as this commmit works for me. I make a release build for this commit in my fork repo. If it works for yours, I'll make a pull request later.

Phane7 commented 4 months ago

This problem olny appears when start with windows. Maybe some task run slower after a windows update lead to program can not finish init within origin global mutex timeout? I don't konw actually why. However, just increase GLOBAL_DEFAULT_TIMEOUT as this commmit works for me. I make a release build for this commit in my fork repo. If it works for yours, I'll make a pull request later.

I updated back to 23H2 but the issue is still gone. If it comes back, I'll test it. Maybe someone else still fighting this can test that fork instead.

ColdThunder11 commented 4 months ago

I updated back to 23H2 but the issue is still gone. If it comes back, I'll test it. Maybe someone else still fighting this can test that fork instead.

Finally find out that inpoutx64's driver may not open success and there is no detection makes the startup of PowerControl cost a lot of time. I add a reload action when detect it, now InpOut can success open in my steamdeck but reload and MapPhysToLin takes more than 10s (about 11s-12s). It's still necessary to increase GLOBAL_DEFAULT_TIMEOUT. 30s' timeout works well on my steamdeck. Build here you can try.