Windows 10: WSL2 fails to inherit Windows Environment PATH variable Code

I had a perfect Debian environment working in WSL2 on my Surface Laptop 2 until yesterday, when an attempt to play around with an unstable build resulted in me needing to reinstall the distro. However, upon reinstall, I was unable to access the previously usable Code variable in WSL. I have checked the environment variables - I added "C:\Users\USER\AppData\Local\Programs\Microsoft VS Code\bin" to the local user. Thinking it was an access issue, I went ahead and added it to the system variables as well. I have also attempted a complete reinstall of Windows 10 from Cloud, and reproduced the previous steps.


I'm thinking there may be some error in variable sharing between Windows and WSL. "https://devblogs.microsoft.com/commandline/share-environment-vars-between-wsl-and-windows/" seemed to point in the right direction but I'm fairly certain I never had to mess around with WSLENV previously - my working build inherited directly properly.


There are also decent guides peppered around for editing bashrc directly in Linux or Mac but I'm worried that this will override some important functionality in WSL.


Is there a command on the Windows side that can help grant its PATH to the WSL?


OS Name Microsoft Windows 10 Home
Version 10.0.19041 Build 19041
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-U5ENFJ0
System Manufacturer Microsoft Corporation
System Model Surface Laptop 2
System Type x64-based PC
System SKU Surface_Laptop_2_1769_Consumer
Processor IntelR CoreTM i5-8250U CPU @ 1.60GHz, 1800 Mhz, 4 Cores, 8 Logical Processors
BIOS Version/Date Microsoft Corporation 138.3261.768, Not Available
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Microsoft Corporation
BaseBoard Product Surface Laptop 2
BaseBoard Version Not Available
Platform Role Mobile
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom

:)

 

WSL2 and Environment Variables

I am trying to install Selenium and build a python application that includes automating web page completion (login info). I would like to built the program using VSCode and WSL2. I've installed selenium in WSL2. Selenium requires a webdriver api to
be installed and included on the system PATH in the environment variables. If I install the msedgedriver.exe for Windows, in Windows, and add it to PATH, will it work with Selenium installed on WSL2 in VSCode using Python?

 

System environment variable won't stick

Running Win10 Home on an Acer Spin 3, 64bit, i7cpu. I try to add a path to the system environment variables by:

1. Control Panel > System > Advanced system settings > Advanced tab > Environment variables

2. The "Environment Variables" window opens.
3. In the "System Variables" pane I select "Path" and click the EDIT button.
4. A list of the current system paths is displayed.
5. I click the NEW button, browse to the path I want to add which is "C:\Python36-32" and click OK. The path "C:\Python36-32" is added to the list of current system paths.
6. I click OK and am returned to the "Environment Variables" window.
7. I click the "X" at the top right to close the "Environment Variables" window.

Now if I click the "Environment Variables" button again (end of step-1) and repeat steps 2-4, the new path I added in step-5 is gone. IOW, adding a new path won't stick.

What am I doing wrong?

 

Accidentally deleted the path of environment variables

I accidentally deleted the path of system environment variables, instead of editing it and adding a new one, in my Windows 10 Dell Laptop. I lost all the default variables that were there. How do I restore the previous variables? Please help