We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I enabled steam auto kill and auto restart but I get errors in the logs:
Killing Steam (Error): + Start-Process "${env:PROGRAMFILES(X86)}\Steam\steam.exe" "-shutdown" CategoryInfo : InvalidOperation : (:) [Start-Process], InvalidOperationException FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
The problem is that my steam is not in the usual location, so you should use the path specified in the steam rom manager options
Install steam in a non-usual directory. D:/Steam for example
Activate steam auto kill and auto restart, go to "Add games" and "save to steam"
Go to the logs and see that the kill and start do not work.
you should use the path specified in the steam rom manager options
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I enabled steam auto kill and auto restart but I get errors in the logs:
Killing Steam (Error): + Start-Process "${env:PROGRAMFILES(X86)}\Steam\steam.exe" "-shutdown"
CategoryInfo : InvalidOperation : (:) [Start-Process], InvalidOperationException
FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
The problem is that my steam is not in the usual location, so you should use the path specified in the steam rom manager options
Install steam in a non-usual directory. D:/Steam for example
Activate steam auto kill and auto restart, go to "Add games" and "save to steam"
Go to the logs and see that the kill and start do not work.
you should use the path specified in the steam rom manager options
The text was updated successfully, but these errors were encountered: