microsoft / microsoft/amplifier

[Bug] Bundle preparation fails on Windows: uv pip install -e cannot overwrite running amplifier.exe (OS error 32)

Open
#218 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3.1k
Forks
261
Avg merge
3h 28m
Merged PRs (30d)
13

Description

Description

amplifier run fails on Windows because bundle preparation calls uv pip install -e on every invocation, which attempts to remove/overwrite the currently running amplifier.exe. Windows file locking prevents this.

Environment

  • OS: Windows 11 (10.0.26200) ARM64
  • Python: 3.13.12
  • amplifier: 2026.02.14-a94f815
  • uv: installed via pipx
  • Install method: editable (pip install -e .)

Reproduction

amplifier run --mode single "What is 7 * 8?"

Error

Preparing bundle 'foundation'...
Failed to install module from C:\Users\<user>\.amplifier\cache\amplifier-d1dda27a16518560.
stderr: error: failed to remove file `...\Scripts\amplifier.exe`:
  The process cannot access the file because it is being used by another process. (os error 32)

Notes

  • Same command works on WSL/Linux — Unix allows deleting a running binary, Windows does not.
  • The error originates in amplifier-foundation/modules/activator.py_install_dependencies().

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in amplifier-foundation/modules/activator.py at _install_dependencies(), then reproduce amplifier run --mode single "What is 7 * 8?" on Windows. Done means bundle preparation no longer tries to overwrite the running amplifier.exe and the command succeeds, while the existing Linux behavior remains working.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.