Repository navigation
Error - pip not available after 1.105 upgrade #25523
Copy link
Copy link
Closed as not planned
Labels
info-neededIssue requires more information from posterIssue requires more information from postertriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
Description
Type: Bug
Behaviour
When you open a .ipynb file and select a kernel , an error message is given about pip not being available
Steps to reproduce:
- XXX
Diagnostic data
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX
Extension version: 2025.16.0
VS Code version: Code 1.105.0 (03c265b1adee71ac88f833e065f7bb956b60550a, 2025-10-08T14:09:35.891Z)
OS version: Windows_NT x64 10.0.26100
Modes:
- Python version (& distribution if applicable, e.g. Anaconda): 3.13.7
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
- Value of the
python.languageServersetting: Default
User Settings
languageServer: "Pylance"
Installed Extensions
| Extension Name | Extension Id | Version |
|---|---|---|
| copilot | Git | 1.372.0 |
| copilot-chat | Git | 0.32.0 |
| debugpy | ms- | 2025.14.0 |
| js-debug | ms- | 1.105.0 |
| js-debug-companion | ms- | 1.1.3 |
| jupyter | ms- | 2025.9.0 |
| jupyter-keymap | ms- | 1.1.2 |
| jupyter-renderers | ms- | 1.3.0 |
| python | ms- | 2025.16.0 |
| rainbow-csv | mec | 3.23.0 |
| vscode-js-profile-table | ms- | 1.0.10 |
| vscode-jupyter-cell-tags | ms- | 0.1.9 |
| vscode-jupyter-slideshow | ms- | 0.1.6 |
| vscode-pylance | ms- | 2025.8.3 |
| vscode-python-envs | ms- | 1.10.0 |
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) Ultra 5 235U (14 x 3187) |
| GPU Status | 2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 31.46GB (13.24GB free) |
| Process Argv | --crash-reporter-id bae412fe-a861-410d-86c7-7c96a3208b82 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
usemplatestapi:31297334
aj953862:31281341
agentisdefault:31399626
nes-set-on:31351930
63221493:31336333
envsdeactivate2:31353495
ovs_ter_t:31398874
0cj2b977:31352657
gendocstringf:31395206
0574c672:31362109
cloudbuttont:31379625
todos-1:31390405
v66_all_req:31398803
treatment_gpt5applypatchexclusively:31398171
3efgi100_wstrepl:31382709
trigger-command-fix:31379601
auto_model_enabled:31385282
use-responses-api:31390855
gemagent1cf:31398531
applesignin:31399435
dcggh915:31400023
ddidt:31399633
nes-subseq-delay-200:31400950
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
info-neededIssue requires more information from posterIssue requires more information from postertriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
Activity
eleanorjboyd commentedon Oct 13, 2025
Hi! Can you try disabling the python environments extension and see if this changes the behavior? Thanks
mtm-tud commentedon Oct 13, 2025
Hi, thanks for fast response, i had to rollback to 1.104.1 which I've found to be stable (I am lecturing a class of 130 2nd year students, and they have a big assessment over the next 2 weeks so I had to get them set up for success today, most were impacted with the 1.105 release and now all are rolling back tonight). I will attempt to do that on another machine once I get this sorted. Thanks!
eleanorjboyd commentedon Oct 14, 2025
totally understand- glad rolling back worked and I will look at this on my end as well
mtm-tud commentedon Oct 14, 2025
eleanorjboyd commentedon Dec 9, 2025
Let me know if you are able to try again and if you are still seeing this issue- thanks!
github-actions commentedon Jan 9, 2026
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!