microsoft
vs_BuildTools.exe
Type: Bug
I installed some items using vs_BuildTools and when I restarted my computer my venv stopped recognizing their libs and their pip. What do I do?
VS Code version: Code 1.80.0 (660393deaaa6d1996740ff4880f1bad43768c814, 2023-07-04T15:06:02.407Z) OS version: Windows_NT x64 10.0.18362 Modes:
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 7 5700X 8-Core Processor (16 x 3394) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off 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 video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.89GB (24.30GB free) |
| Process Argv | --crash-reporter-id ea101295-932e-43a7-8daf-607bf9c3c26e |
| Screen Reader | no |
| VM | 0% |
Extensions (24)
| Extension | Author (truncated) | Version |
|---|---|---|
| gitlens | eam | 14.0.1 |
| code-runner | for | 0.12.0 |
| gc-excelviewer | Gra | 4.2.57 |
| terraform | has | 2.27.0 |
| vscode-language-pack-pt-BR | MS- | 1.80.2023070509 |
| isort | ms- | 2023.11.11881009 |
| python | ms- | 2023.13.11881007 |
| vscode-pylance | ms- | 2023.7.10 |
| jupyter | ms- | 2023.6.1001861915 |
| jupyter-keymap | ms- | 1.1.2 |
| jupyter-renderers | ms- | 1.0.17 |
| vscode-jupyter-cell-tags | ms- | 0.1.8 |
| vscode-jupyter-slideshow | ms- | 0.1.5 |
| cmake-tools | ms- | 1.14.34 |
| cpptools | ms- | 1.16.3 |
| cpptools-extension-pack | ms- | 1.3.0 |
| powershell | ms- | 2023.6.0 |
| vsliveshare | ms- | 1.0.5873 |
| color-highlight | nau | 2.5.0 |
| origamid-next | ori | 2.0.5 |
| chatgpt | tim | 1.1.2 |
| tom | 1.2.2 | |
| cmake | twx | 0.0.17 |
| vscode-icons | vsc | 12.4.0 |
(1 theme extensions excluded)
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
2e4cg342:30602488
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
2i9eh265:30646982
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
showindicator:30785052
pythongtdpath:30769146
bgfeh915:30780428
pythonnosm12tcf:30779713
pythonidxpt:30784022
pythonnoceb:30776495
@lucena564 sorry for the delay here. vs_BuildTools.exe isn't owned by the VS Code team, it's owned by the Visual Studio team so you'll need to help me out here. A few follow up questions:
- Are you still seeing this?
- Does your venv recognize the libs in a different application like Windows Terminal outside of VS Code?
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
