Terminal failed to start with "Access is denied" error
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 153
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Short summary
Terminal initialization fails with access denied error when attempting to spawn PowerShell process.
### Affected version or release
v1.1.8
### Installation context
GitHub Copilot installed on Windows, attempting to spawn terminal with shell integration
### What happened?
When opening a terminal session, the application fails to spawn the PowerShell process with the following error:
```
Failed to spawn PTY command: CreateProcessW `"C:\\Users\\hnaganur\\AppData\\Local\\Microsoft\\WindowsApps\\pwsh.exe -NoLogo -ExecutionPolicy Bypass -NoExit -Command \". '\\\\?\\C:\\Users\\hnaganur\\AppData\\Local\\Programs\\GitHub Copilot\\terminal-integration\\shellIntegration.ps1'\"\0"` in cwd `Some("C:\\Users\\hnaganur\\.copilot\\chats\\fd4d9613-e8fd-4251-b269-5486833858ba\0")` failed: Access is denied. (os error 5)
```
### Steps to reproduce
- Launch GitHub Copilot app
- Open or navigate to a chat session
- Attempt to open a terminal
### Expected behavior
Terminal should initialize successfully and display a ready PowerShell prompt.
### Additional context
- **Error Code:** OS error 5 (Access is denied)
- **Shell:** PowerShell (pwsh.exe)
- **Environment:** Windows
- **Attempted Integration:** Shell integration script at `terminal-integration\shellIntegration.ps1`
- **Working Directory:** `.copilot\chats\fd4d9613-e8fd-4251-b269-5486833858ba`
Guía de contribución
Línea de trabajo
Reproduce the failure on Windows from the GitHub Copilot app using pwsh.exe and the reported .copilot\chats working directory. Start with the terminal launch path and terminal-integration\shellIntegration.ps1, then verify that opening a terminal completes without OS error 5 and shows a ready PowerShell prompt.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- powershell
- Área
- cli, desktop, operating-systems
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100