You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have a WSL distro with working networking (e.g., ping 1.1.1.1 works as you'd expect)
Change the TEMP and TMP environment variables (in Windows) to something other than the default, preferably also on another drive like D:\Temp when WINDIR is C:\WINDOWS - it seems that the per-user ones are the ones that matter but change all 4 of them just in case
Reboot
Start the very same WSL distro and try step 1 again
Note that the non-default Temp folder existed and was NOT NTFS-compressed in this scenario, which is another bug that will break WSL networking.
Expected Behavior
Networking to keep working regardless of what TEMP/TMP are on the Windows side if they still point to a sensible path
Actual Behavior
Network is unreachable or Temporary failure in name resolution depending on you pinging an IP address or a domain name
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered:
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.
Windows Build Number
Microsoft Windows [Version 10.0.19042.867]
WSL Version
Kernel Version
5.4.72-microsoft-standard-WSL2
Distro Version
Gentoo
Other Software
No response
Repro Steps
ping 1.1.1.1
works as you'd expect)Note that the non-default Temp folder existed and was NOT NTFS-compressed in this scenario, which is another bug that will break WSL networking.
Expected Behavior
Networking to keep working regardless of what TEMP/TMP are on the Windows side if they still point to a sensible path
Actual Behavior
Network is unreachable
orTemporary failure in name resolution
depending on you pinging an IP address or a domain nameDiagnostic Logs
No response
The text was updated successfully, but these errors were encountered: