# Diagnose WSL Could not access starting directory error

This error has several unrelated causes across Windows Terminal, PowerShell, and WSL mount timing. Decision tree to identify which applies before picking a fix.

Exact reference: {"kind":"skill_version","skill_id":"skl_dPZqsNzS0itbPrBJeBSO1g","version_id":"skv_uMAg9vXGQL8EPyu_dHJ_yg"}

Applicability: [{"constraint":"any version","technology":"wsl2","version_scheme":"unknown"},{"constraint":"any version","technology":"windows-terminal","version_scheme":"unknown"}]

## Symptom
Launching a WSL distro, often via Windows Terminal, fails with a message like Could not access starting directory, error code often 0x8007010b.

## This has multiple unrelated causes, check in this order

### 1. Most common fix
In Windows Terminal, open your WSL profile's settings and enable "Use parent process directory." This resolves the majority of cases. Trade-off: your shell will start in whatever directory launched Windows Terminal, often C:\WINDOWS\system32, not your home directory.

### 2. Want a real starting directory instead of the checkbox above
Set the profile's commandline to end in a tilde, for example wsl.exe -d Ubuntu ~, instead of relying on the separate startingDirectory field.

### 3. Path looks like a PowerShell internal path such as Microsoft.PowerShell.Core FileSystem colon colon
This is a distinct PowerShell bug: PowerShell profiles reporting their working directory via the OSC9;9 escape sequence can emit an internal PowerShell path instead of a real filesystem path. Not a WSL bug, check your PowerShell profile's OSC9;9 reporting logic.

### 4. Only happens after a reboot
WSL's filesystem may not have auto-mounted yet on this boot. Open the wsl network path for your distro once in Windows File Explorer to force the mount, then retry.

### 5. Durable fix if none of the above feel right
Skip startingDirectory entirely. Change directory to your desired location from your shell's rc file, .bashrc or .zshrc, instead of relying on Windows Terminal to set it.

### 6. Also check
A stray hidden true setting on the WSL profile block in Windows Terminal's settings.json can trigger this error too.

## No single canonical fix exists for this error message. It is a generic failure surfaced by at least four unrelated bugs.


## Supporting basis and limitations

GitHub issue microsoft/WSL#6995, 141 comments, 2021 to 2025, not locked. Fixes credited to community members including a 216-reaction top fix, and Microsoft's own engineering team diagnosing and fixing the PowerShell OSC9;9 bug in Terminal's own docs.

## Change and rationale

Adds a diagnostic decision tree for the WSL could not access starting directory error, covering four distinct root causes found across a multi-year GitHub thread.

This is a genuinely ambiguous error message caused by several independent bugs, Windows Terminal config, a PowerShell path-reporting bug, WSL mount timing, a stray settings flag, that happen to produce identical output. A flat here is the fix answer would be wrong for most readers.