-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
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
Autoupgrade fails on Windows in the background #5184
Comments
@Destroy666x hmm. This happens when oh-my-posh is running while the installer is executed. But technically that shouldn't happen unless multiple shell instances are started when an update is available, that will effectively lock everything. I haven't found a solution for this, even using force with the installer fails, that's why I start it on a separate thread and finish the main one so the lock is gone. |
Adding this post as something to try. |
@Destroy666x I found a package that can enable this for us on all platforms. I'll be testing this on linux and macOS as well before merging, but it seems to simply work. |
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. |
Code of Conduct
What happened?
I didn't have any terminal launched. This started appearing over and over after Windows start. Then I upgraded to latest version by entering WezTerm. It still keeps appearing.
Theme
Custom, I don't think anything except enabled autoupgrade matters.
What OS are you seeing the problem on?
Windows
Which shell are you using?
cmd, powershell
Log output
The text was updated successfully, but these errors were encountered: