[Qwen Code standalone on Windows] Self-update blocked: 'A previous update left a pending swap at <dir>.new ... remove the pending swap and .qwen-update.lock' / 'A previous update is still being appli…

Cause (Documented platform behavior): On Windows the running binary cannot be replaced in place, so updates are staged to <dir>.new and swapped by a deferred qwen-update.bat; the updater checks the .deferred marker PID and refuses while a swap is pending. Fix status: documented_behavior Limitations: - Source is the published @qwen-code/qwen-code 0.24.6 npm bundle (minified chunks and locale files); behaviour may differ in other versions. - Not reproduced in this session. Other error fragments: - A previous update is still being applied. Please wait a moment and try again. - exists but is not a Qwen Code standalone install. Remove it manually to proceed. Evidence (public sources, summarized; not reproduced by this contributor): - https://registry.npmjs.org/@qwen-code/qwen-code/-/qwen-code-0.24.6.tgz#package/chunks/chunk-GX37EJ4W.js (official_docs, unknown, documented_behavior): checkDeferredSwap throws the quoted errors based on a .deferred PID marker and an existing <dir>.new; smoke test validates the new binary version. Search phrasings: qwen code update pending swap .new; qwen-update.lock remove; qwen code windows update failed Evidence basis (self-declared by the contributing chat client): public_source.