Sorry for the weird torn state here for a couple releases folks. I'm definitely gonna close this as 'fixed in preview'. #9223, which goes all the way back to Preview v.0. This is cause the check that should enable this came in #12315, but that only ever went to Preview, not stable. 2 does NOT, and gives the same 0xffffffff error.Ĭonsidering that 1.14 is about to come out and 1.13 is gonna get promoted to the Stable version, I'm inclined to close this out as 'fixed in preview'Īh.3 works perfectly fine with ~ as the starting directory.I need to dig out a win10 machine to be able to validate though. I coulda swore that #12437 should have fixed this, which is in Windows Terminal v3.0 / Windows Terminal Preview v5.0. Reports that this doesn't work on:įor people affected by this, changing to %USERPROFILE% works as a workaround. Seems like the whole 'default to ~ for WSL's on <= 19041' doesn't work for folks. Okay there's a lot of reports here, I'm gonna try and distill this down Again, everything just works if starting from the Start menu tile in the standard conhost. So it would appear that there's nothing special about %USERPROFILE%, per se, but that setting a starting directory that exists inside the WSL distribution is what is currently not working in recent versions of WT.

I did the same and it did work inside of Windows Terminal, On a whim, I then set the starting directory to /home/my-wsl-username as opposed to the default ~. The very same distribution works just fine if I start it from the Start menu tile inside the standard CMD console host window instead of using WT.Īccording to the bug report on the WSL project, one user set the starting directory to %USERPROFILE% and then it worked.I have had no Windows Updates in over a year (a Windows Update in late 2019, and twice more in early 2020 DELETED ALL of my personal user data on my work laptop-so yeah, I no longer allow my laptop to update at this time) and the last time I used my distribution, only a few weeks ago, it was working just fine inside of Windows Terminal.I can confirm this is a problem with Windows Terminal because: I reported over on the WSL GitHub project.

Ubuntu windows terminal