terminal: error when launching..Could not access starting directory
Windows Terminal version (or Windows build number)
1.8.1444.0
Other Software
- PowerToys v0.37.2 (newly installed ~2 weeks)
- Windows 10 Pro 20H2 Build 19042.985 (newly installed < 1mo.) No other issues.
- Kate 21.04.0 (newly installed ~1 week)
- Windows Terminal Settings?
- Added paste setting
- added color schemes
- “Gruvbox Dark”,
- “Gruvbox Dark Blu”,
- Anaconda and WSL2 settings
{
"colorScheme": "Gruvbox Dark",
"commandline": "cmd.exe /K %USERPROFILE%\\Miniconda3_32\\Scripts\\activate.bat",
"guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6102}",
"hidden": false,
"icon": "%USERPROFILE%\\Miniconda3_32\\Menu\\Iconleak-Atrous-Console.ico",
"name": "Anaconda Prompt (Miniconda3_32)",
"startingDirectory": "C:\\Users\\myname",
"tabTitle": "Anaconda (qb)"
},
{
"bellStyle": "none",
"colorScheme": "Gruvbox Dark Blu",
"guid": "{58ad8b0c-3ef8-5f4d-bc6f-13e4c00f2530}",
"hidden": false,
"name": "Debian",
"source": "Windows.Terminal.Wsl",
"startingDirectory": "C:\\Users\\myname",
"tabTitle": "WSL (Debian)"
},
Steps to reproduce
This happened after latest update. I tried toggling WSL in “manage app execution aliases” as recommended in another recent post but this did not improve the broken Windows Terminal. Windows Terminal error 0x80070003 when launching `fedoraremix.exe’ #10167
Repair is not sufficient. Only Reset brings back the WSL functionality. If I reset Windows app and return to base settings then Debian works, but of course Conda is missing.
I have nearly the exact same setup on my remote work computer-- same Windows Terminal version, Windows Terminal settings (except for different path/machine name), recent installs of PowerToys and Kate. Windows 10 version on work computer is also the same. I remote into using RDP. No issues there.
I use Windows Terminal nearly every day to use Debian to SSH into remote server. Have experience no issues until yesterday.
Expected Behavior
Launch of Anaconda or WSL2 Debian
Actual Behavior
[error 0x8007010b when launching `wsl.exe -d Debian']
Could not access starting directory "C:\Users\myname"
[error 0x8007010b when launching `cmd.exe /K %USERPROFILE%\Miniconda3_32\Scripts\activate.bat']
Could not access starting directory "C:\Users\myname"
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 10
- Comments: 19 (6 by maintainers)
Getting a similar or the same problem. I have my start directory set to
//wsl$/Ubuntu/home/aaron
, this has been working fine for me for a long time, until today where after installing Windows 10 Cumulative Update for June 2021, I now get an error on starting WSL inside Windows Terminal. I have to start WSL outside of Windows Terminal first, using the default starting directory, then opening WSL inside Windows Terminal works, which is now rather annoying.IMO this should be re-opened
The latest update seems to have broken my starting directory as well. Manually editing the starting directory fixed the issue, but I had made no changes to it from the default installation and this update broke it.
Huh. Out of curiosity, what happens when you remove
startingDirectory
from your settings?We stopped validating those before on launch in #10045. Before that, we’d just silently fall back to
%userprofile%
when we couldn’t validate the directory.I’m seeing the same issue in Version 10.0.22000 Build 22000, it does seem like this issue should be reopened
This is a somewhat annoying issue where WSL cannot handle
\\wsl$
paths until it’s been launched once, which we’re hoping to ameliorate with #9223We’ve got some documentation specifying this, but we could probably make it clearer and surface it in the UI somewhere.
This has never been possible, but due to aggressive path “validation” it was ignored, and reset to C:\Users\yourname. For some people, this looked like it was working. In every case, however, it was not. Folks just had invalid
startingDirectory
settings that were being ignored instead of reported.I’m seeing this happen as well, my starting directory was set to
/home/tom/
, which does exist within WSL, but Terminal was trying to set the starting directory toC:/home/tom
, if I create a home directory within Windows it will then run WSL, but I start in/mnt/c/home/tom
.