Unable to Use Copilot after 1.0.40

[bmkaiser]

Describe the bug

After version 1.0.40, I can no longer install new versions of Copilot CLI on Windows 11 with WinGet. When running copilot.exe I get the following error:

Package extraction took 25977ms
Failed to extract bundled package: Error: EPERM: operation not permitted, rename 'C:\Users\bmkaiser\AppData\Local\copilot\pkg\win32-x64\.extracting-1.0.42-44072-1778094065373' -> 'C:\Users\bmkaiser\AppData\Local\copilot\pkg\win32-x64\1.0.42'
    at async Object.rename (node:internal/fs/promises:785:10)
    at async Cr (sea-loader.js:8:54620)
    at async Vh (sea-loader.js:8:55884)
    at async Xh (sea-loader.js:9:52) {
  errno: -4048,
  code: 'EPERM',
  syscall: 'rename',
  path: 'C:\\Users\\bmkaiser\\AppData\\Local\\copilot\\pkg\\win32-x64\\.extracting-1.0.42-44072-1778094065373',
  dest: 'C:\\Users\\bmkaiser\\AppData\\Local\\copilot\\pkg\\win32-x64\\1.0.42'
}

[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

I see the following from the 1.0.42 release notes:

CLI updates on Windows no longer fail with ENOENT when a transient EPERM occurs during package extraction

However, I'm still experiencing the issue. I have tried uninstalling and reinstalling with WinGet, but the only working solution I have so far is downgrading back to 1.0.40.

Affected version

1.0.42

Steps to reproduce the behavior

1. Install with WinGet: winget install --id GitHub.Copilot --silent --accept-package-agreements --accept-source-agreements --force
2. Run copilot.exe

Expected behavior

I expect GitHub Copilot CLI to launch.

Additional context

• Operating System: Windows 11 (25H2)
• Terminal Emulator: Windows Terminal
• CPU Architecture: x64
• Shell: PowerShell 7.6.1