You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
plugin install fails with Access is denied (os error 5) on Windows for all sources #4151
copilot plugin install fails 100% of the time on Windows 11 with:
Failed to install plugin: Error: Failed to install plugin: Access is denied. (os error 5)
It fails for a marketplace source (azure@azure-skills), a direct GitHub repo, and a local directory source — so it is not specific to one plugin or fetch method.
Install aborts. It creates an empty target folder under ~/.copilot/installed-plugins/ (e.g. azure-skills and _direct) then fails on its first file operation, before any file is written.
Investigation / ruled out
Not permissions/sandbox: fails identically when run directly as the real user with Full Control over the entire ~/.copilot tree.
Not Controlled Folder Access:Get-MpPreference shows EnableControlledFolderAccess = 0.
Not git:git clone --depth 1 https://github.com/microsoft/azure-skills.git succeeds (1552 files).
Not a lock: the leftover target folder can be freely renamed/deleted.
Plain create/write/delete under installed-plugins and %TEMP% all succeed as the same user.
Fails for both remote and local sources, immediately after the target dir is created.
No detail is written to ~/.copilot/logs; the message is stderr-only and double-wrapped, hiding the offending path.
Suspected cause
A native filesystem op in the install/cache pipeline (likely remove_dir_all/rename/copy) returning Windows ERROR_ACCESS_DENIED — a common Rust-on-Windows failure against read-only files (e.g. git pack objects). Surfacing the actual path in the error would greatly help.
Workaround
copilot --plugin-dir <local-plugin-dir> loads the plugin fine, confirming only the install/copy path is broken.
Hi @ChaitanyaBalaji-SNP , if you have VS Code opened, please try after closing VS Code as a workaround.
Reacted by evabowe, connor-m-burke, Usama Ansari, Quinn Kleinfelter, R. Cooper Snyder, rajivatcc, Rob Jack Stewart, Oliver Shearden, amaringolo, R1ckyCZ and 3 more
Thanks for the report! This is the same issue as #4095, so I'm closing this one as a duplicate. Please follow that issue for updates and add any extra details there.
Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.
Activity
bigben446 commentedon Jul 17, 2026
+1
priyanshu92 commentedon Jul 17, 2026
Duplicate of #4095
Hi @ChaitanyaBalaji-SNP , if you have VS Code opened, please try after closing VS Code as a workaround.
5078086729442496Mahmoud commentedon Jul 17, 2026
4151
patniko commentedon Oct 26, 2026
Thanks for the report! This is the same issue as #4095, so I'm closing this one as a duplicate. Please follow that issue for updates and add any extra details there.
Triaged as part of a Copilot SDK backlog review, with help from GitHub Copilot.