-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Updating Warp on Windows fails every first time #8339
Copy link
Copy link
Open
Labels
bugSomething isn't working.Something isn't working.os:windowsWindows-specific behavior, regressions, or requests.Windows-specific behavior, regressions, or requests.pf:waiting-warperWaiting for Warp team responseWaiting for Warp team responseready-to-implementThe issue is ready for implementation work.The issue is ready for implementation work.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.
Description
Metadata
Metadata
Assignees
Labels
bugSomething isn't working.Something isn't working.os:windowsWindows-specific behavior, regressions, or requests.Windows-specific behavior, regressions, or requests.pf:waiting-warperWaiting for Warp team responseWaiting for Warp team responseready-to-implementThe issue is ready for implementation work.The issue is ready for implementation work.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.
Pre-submit Checks
Describe the bug
Everytime Warp detects that an update is available and you let it install the update, it closes, then shows en error dialog.
You have to then restart warp again, goto help, install update, then it works.
Not a nig problem, but still annoying since you update frequently.
To reproduce
Get an update available notification.
Install the update.
Warp closes, then an error dialog is shown.
This has been like this for as long as I am using warp.
Start Warp again
Goto Help, install update
Warp closes and update runs through fine.
Expected behavior
Update should run without error the first time.
Screenshots, videos, and logs
No response
Operating system (OS)
Windows
Operating system and version
10.0.26220
Shell Version
No response
Current Warp version
v0.2025.12.17.17.17.stable_02
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None