You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to request an option to change the shutdown method used by Playnite in fullscreen mode.
Background:
When shutting down via Playnite in fullscreen mode, it uses shutdown.exe, which causes certain services to not start properly after a reboot.
This includes services such as Controller Companion and Virtual Display Driver (VDD), requiring a manual login to get them working again.
In contrast, performing a standard Windows shutdown via the Start menu does not cause this issue. Everything works as expected, allowing Wake-on-LAN (WOL) to function correctly, Playnite to start in the background, without needing the user to log in. .The issue persists even after a fresh installation of Windows.
Other users have encountered similar behavior and confirmed the discrepancy between the shutdown.exe method and the "standard one" as discussed in this StackOverflow post.
Potential Solution:
A potential solution could be to use the (undocumented) EWX_ARSO flag with ExitWindowsEx(), which appears to replicate the standard Windows shutdown behavior. However, given that this method is undocumented, it may be preferable to add an option allowing users to choose between different shutdown methods in case the flag is removed in future Windows updates.
Request:
Implement an option in Playnite settings to choose the shutdown method.
Consider using ExitWindowsEx() with the EWX_ARSO flag as an alternative to shutdown.exe.
Thank you for your time and consideration!
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Feature description
Description:
I would like to request an option to change the shutdown method used by Playnite in fullscreen mode.
Background:
When shutting down via Playnite in fullscreen mode, it uses shutdown.exe, which causes certain services to not start properly after a reboot.
This includes services such as Controller Companion and Virtual Display Driver (VDD), requiring a manual login to get them working again.
In contrast, performing a standard Windows shutdown via the Start menu does not cause this issue. Everything works as expected, allowing Wake-on-LAN (WOL) to function correctly, Playnite to start in the background, without needing the user to log in. .The issue persists even after a fresh installation of Windows.
Other users have encountered similar behavior and confirmed the discrepancy between the shutdown.exe method and the "standard one" as discussed in this StackOverflow post.
Potential Solution:
A potential solution could be to use the (undocumented) EWX_ARSO flag with ExitWindowsEx(), which appears to replicate the standard Windows shutdown behavior. However, given that this method is undocumented, it may be preferable to add an option allowing users to choose between different shutdown methods in case the flag is removed in future Windows updates.
Request:
Implement an option in Playnite settings to choose the shutdown method.
Consider using ExitWindowsEx() with the EWX_ARSO flag as an alternative to shutdown.exe.
Thank you for your time and consideration!
Screenshots
No response
The text was updated successfully, but these errors were encountered: