Shell execution timed out?

[Randark-JMT]

I'm encountering a problem where the terminal consistently shows a delayed environment activation when using venv.

In the VS Code output window, under the Python Environment tab, I see the following information:

2026-01-09 09:32:00.754 [error] Shell execution timed out: & D:\_Code\test\env-3_14\Scripts\Activate.ps1
2026-01-09 09:32:00.754 [info] Terminal is activated: d:\_Code\test\env-3_14\Scripts\python.exe

However, the script itself is actually fine.

PS D:\_Code\test> Measure-Command { & D: D:\_Code\test\env-3_14\Scripts\Activate.ps1 }   

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 0
Milliseconds      : 5
Ticks             : 50536
TotalDays         : 5.84907407407407E-08
TotalHours        : 1.40377777777778E-06
TotalMinutes      : 8.42266666666667E-05
TotalSeconds      : 0.0050536
TotalMilliseconds : 5.0536

[Randark-JMT]

The good news is that after using this setting

"python-envs.terminal.autoActivationType": "shellStartup"

the delayed activation issue was resolved. However, I'm still curious why command mode encountered a timeout problem.

[anthonykim1]

Which version of Python environment extension are you using?

Also

what does it say next to shell integration when you hover over terminal tab?

[Randark-JMT]

Vision of Python environment extension: 1.16.0

[eleanorjboyd]

@anthonykim1

[Randark-JMT]

The reproduction process is as follows:

[anthonykim1]

Yes, that is as expected, it is so that we can avoid potentially showing you double activate command in terminal. The log is mainly for our internal logging purposes, it seems like activation happened successfully for you.

Use shellStartup if you want terminal activated without waiting and also the cleanliness of not showing activate command in your terminal:

Please set python-envs.terminal.autoActivationType to shellStartup in your settings.
Also add "python.useEnvironmentsExtension": true, to your settings.json.

It will be instant with shellStartup.

If you want to stick to command activation, then try adjusting
https://code.visualstudio.com/updates/v1_106#_consolidated-shell-integration-timeout-setting