Skip to content

vscode-python-envs forgets environment and writes faulty ./.vscode/settings.json #1219

Closed
Closed
vscode-python-envs forgets environment and writes faulty ./.vscode/settings.json#1219
Assignees
eleanorjboyd
Labels
info-neededIssue requires more information from poster

Description

@hunterhogan
Hunter Hogan (hunterhogan)
opened on Feb 11, 2026

Type: Bug

I updated to 1.18.1. On the very next restart, vscode-python-envs had forgotten that I had a .venv. After I selected the correct environment, in the directory "./.vscode," it created a "settings.json" file.

Contents

{
    "python-envs.pythonProjects": [
        {
            "path": "",
            "envManager": "ms-python.python:venv",
            "packageManager": "ms-python.python:pip"
        }
    ]
}

I deleted the file, restarted VS Code, and the same thing happened.

This is the exact same issue that was happening the pre-release, reported by bitadmiral in #1115, and elaborated by me in #1115 (comment).

Extension version: 1.18.1
VS Code version: Code - Insiders 1.110.0-insider (ec59ef60160e1e00bf4fec301226427444b42fd2, 2026-02-10T14:43:03.373Z)
OS version: Windows_NT x64 10.0.26200
Modes:

System Info
Item Value
CPUs AMD Ryzen 7 5700U with Radeon Graphics (16 x 1797)
GPU Status 2d_canvas: enabled
GPU0: VENDOR= 0x1002, DEVICE=0x164c [AMD Radeon(TM) Graphics], DRIVER_VENDOR=AMD, DRIVER_VERSION=31.0.21923.11000 ACTIVE
GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.7309
Machine model name:
Machine model version:
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
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 12.90GB (2.70GB free)
Process Argv
Screen Reader no
VM 0%

Activity

  1. hunterhogan commented on Feb 11, 2026

    @hunterhogan
    Hunter Hogan (hunterhogan)
    on Feb 11, 2026
    Author

    Additional troubleshooting and coping with the problem:

    1. Delete settings.json.
    2. Close VS Code Insiders.
    3. Eat dinner.
    4. Open VS Code.
    5. The problem still exists.
    6. Attempt "Download Specific Version VSIX...", select 1.18.0. Nothing happens. No new files on my computer--except a generic "payload.vsix" in IE Cache. I don't try to use it.
    7. Use "Install Specific Version...", select 1.16.0.
    8. Click Restart Extensions--I don't close VS Code.
    9. The problem is completely resolved without me changing any other settings.
  2. Eleanor Boyd (eleanorjboyd)
    added a commit that references this issue on Feb 11, 2026

    Fix empty path handling in pythonProjects for workspace root projects (…

    e1e27b1

  3. eleanorjboyd commented on Feb 11, 2026

    @eleanorjboyd
    Eleanor Boyd (eleanorjboyd)
    on Feb 11, 2026
    Contributor

    Hi! Sorry about this- we have been making changes around it but obviously are still having trouble. We put in a fix for this issue this morning: e1e27b1 and the pre-release is out which should have this change. Could you try switching to the pre-release version and let me know if that fixes it?

  4. Eleanor Boyd (eleanorjboyd)
    self-assigned this
    on Feb 11, 2026
  5. Eleanor Boyd (eleanorjboyd)
    added
    info-neededIssue requires more information from poster
    on Feb 11, 2026

  6. hunterhogan commented on Feb 11, 2026

    @hunterhogan
    Hunter Hogan (hunterhogan)
    on Feb 11, 2026
    Author
    1. In tab for "ms-python.vscode-python-envs", select "Switch to pre-release."
    2. Version 1.19.10421909.
    3. Click Restart Extensions.
    4. No problems.
    5. Close and re-open VS Code Insiders.
    6. No problems.
    7. Possibly useful information: I don't have a "..vscode\settings.json", and this time the file was not created at any point. (Did that make sense? The non-creation of the file is in contrast to the problem version.)

    Version: 1.110.0-insider (user setup)
    Commit: c600be49daf9167f9757b51670f12151d8621855
    Date: 2026-02-11T17:06:04.989Z
    Electron: 39.3.0
    ElectronBuildId: 13168319
    Chromium: 142.0.7444.265
    Node.js: 22.21.1
    V8: 14.2.231.22-electron.0
    OS: Windows_NT x64 10.0.26200

  7. eleanorjboyd commented on Feb 12, 2026

    @eleanorjboyd
    Eleanor Boyd (eleanorjboyd)
    on Feb 12, 2026
    Contributor

    So it sounds fixed then?

  8. hunterhogan commented on Feb 13, 2026

    @hunterhogan
    Hunter Hogan (hunterhogan)
    on Feb 13, 2026
    Author

    So it sounds fixed then?

    Yes, in the pre-release version.

    1. Click Switch to release version.
    2. Version 1.18.1.
    3. Click restart extensions.
    4. vscode-python-envs has forgotten the environment.
    5. Click Switch to pre-release.
    6. 1.19.10431014
    7. Problem solved.

    Version: 1.110.0-insider (user setup)
    Commit: cc318781a13d6869a36573f9de9eabacc9fad49f
    Date: 2026-02-12T19:01:29.089Z
    Electron: 39.3.0
    ElectronBuildId: 13168319
    Chromium: 142.0.7444.265
    Node.js: 22.21.1
    V8: 14.2.231.22-electron.0
    OS: Windows_NT x64 10.0.26200

  9. Eleanor Boyd (eleanorjboyd)
    closed this as completedon Feb 17, 2026
  10. github-actions
    locked as resolved and limited conversation to collaborators on Apr 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

info-neededIssue requires more information from poster

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions