starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

error 0x8007010b when launching `wsl -d Ubuntu-18.04 #15231

New Issue
Closed
opened 2026-01-31 04:32:06 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 04:32:06 +00:00
Owner
Copy Link

Originally created by @Trid-collab on GitHub (Sep 16, 2021).

Windows Terminal version (or Windows build number)

Windows Terminal Version: 1.10.2383.0

Other Software

windows terminal + WSL +Ubuntu

Steps to reproduce

I have wsl - Ubuntu as my default profile in WIndows Terminal.

I have noticed whenever I am trying to launch the terminal by default to the Ubuntu home directory using the "wsl -d Ubuntu-18.04" in my Terminal Config file I am getting the following error and I am not able to open wsl.

[error 0x8007010b when launching `wsl -d Ubuntu-18.04']
Could not access starting directory "//wsl$/Ubuntu-18.04/home/tridib"

However if open the command prompt and type wsl I am able to launch Ubuntu which opens it by default on my windows user folder and then I need to cd into the Ubuntu home directory.

Is there something I am missing in my config.

Expected Behavior

No response

Actual Behavior

image

Originally created by @Trid-collab on GitHub (Sep 16, 2021). ### Windows Terminal version (or Windows build number) Windows Terminal Version: 1.10.2383.0 ### Other Software windows terminal + WSL +Ubuntu ### Steps to reproduce I have wsl - Ubuntu as my default profile in WIndows Terminal. I have noticed whenever I am trying to launch the terminal by default to the Ubuntu home directory using the "wsl -d Ubuntu-18.04" in my Terminal Config file I am getting the following error and I am not able to open wsl. [error 0x8007010b when launching `wsl -d Ubuntu-18.04'] Could not access starting directory "//wsl$/Ubuntu-18.04/home/tridib" However if open the command prompt and type wsl I am able to launch Ubuntu which opens it by default on my windows user folder and then I need to cd into the Ubuntu home directory. Is there something I am missing in my config. ### Expected Behavior _No response_ ### Actual Behavior ![image](https://user-images.githubusercontent.com/61322708/133550244-13374a6d-71ff-4237-a6a1-26aa910e11c5.png)
claunia commented 2026-01-31 04:32:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 16, 2021):

Curious. Does this work right if you first open a conhost window running wsl (i.e. just run wsl.exe) then open the Terminal? I'm wondering if we're trying to access the wsl$ mount before it actually exists, because the WSL service hasn't started yet.

@zadjii-msft commented on GitHub (Sep 16, 2021): Curious. Does this work right if you first open a conhost window running wsl (i.e. just run `wsl.exe`) _then_ open the Terminal? I'm wondering if we're trying to access the `wsl$` mount before it actually exists, because the WSL service hasn't started yet.
claunia commented 2026-01-31 04:32:07 +00:00
Author
Owner
Copy Link

@Trid-collab commented on GitHub (Sep 16, 2021):

If I run win+r and type wsl it opens the Ubuntu terminal. Then as long that is open I can use the Windows Terminal to open Ubuntu Terminal normally without any issues

@Trid-collab commented on GitHub (Sep 16, 2021): If I run win+r and type wsl it opens the Ubuntu terminal. Then as long that is open I can use the Windows Terminal to open Ubuntu Terminal normally without any issues
claunia commented 2026-01-31 04:32:07 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Sep 16, 2021):

@Trid-collab this is how I start Ubuntu in my home directory:

            {
                "commandline": "wsl.exe ~ -d Ubuntu-20.04",
                "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
                "hidden": false,
                "name": "Ubuntu-20.04",
                "source": "Windows.Terminal.Wsl"
            },
            {
                "commandline": "wsl ~ -d Ubuntu-18.04",
                "guid": "{c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40}",
                "hidden": false,
                "name": "Ubuntu-18.04",
                "source": "Windows.Terminal.Wsl"
            },

Something to get you running until "startingDirectory" is being fixed :)

@elsaco commented on GitHub (Sep 16, 2021): @Trid-collab this is how I start Ubuntu in my home directory: ``` { "commandline": "wsl.exe ~ -d Ubuntu-20.04", "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}", "hidden": false, "name": "Ubuntu-20.04", "source": "Windows.Terminal.Wsl" }, { "commandline": "wsl ~ -d Ubuntu-18.04", "guid": "{c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40}", "hidden": false, "name": "Ubuntu-18.04", "source": "Windows.Terminal.Wsl" }, ``` Something to get you running until "startingDirectory" is being fixed :)
claunia commented 2026-01-31 04:32:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 16, 2021):

@DHowett Shouldn't #9223 have fixed this?

🤦 doh, that's only in 1.11 preview. @Trid-collab Could you try installing "Windows Terminal (Preview)", and reboot the machine (to make sure the WSL service stops), then try this with the Preview version of the Terminal? I'm pretty sure this is fixed in 1.11.

@zadjii-msft commented on GitHub (Sep 16, 2021): @DHowett Shouldn't #9223 have fixed this? 🤦 doh, that's only in 1.11 preview. @Trid-collab Could you try installing "Windows Terminal (Preview)", and reboot the machine (to make sure the WSL service stops), then try this with the Preview version of the Terminal? I'm pretty sure this is fixed in 1.11.
claunia commented 2026-01-31 04:32:08 +00:00
Author
Owner
Copy Link

@Trid-collab commented on GitHub (Sep 18, 2021):

Thank you. let me check. I do not have access to the preview ver right now.

But with the stable release I noticed that sometimes the stable version worked properly with out any errors and sometime it came up with the issues like the one mentioned . So I am confused

@Trid-collab commented on GitHub (Sep 18, 2021): Thank you. let me check. I do not have access to the preview ver right now. But with the stable release I noticed that sometimes the stable version worked properly with out any errors and sometime it came up with the issues like the one mentioned . So I am confused
claunia commented 2026-01-31 04:32:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 18, 2021):

But with the stable release I noticed that sometimes the stable version worked properly with out any errors and sometime it came up with the issues like the one mentioned . So I am confused

Yea, that's because the //wsl$ path isn't accessible until the WSL service (lxss) is already running. So until that service starts, the Terminal thinks that any paths under that root aren't valid paths.

I'm going to tentatively call this fixed by #9223, and when 1.11 moves to stable, if that hasn't fixed this issue for you, we can reopen then. Sound good?

@zadjii-msft commented on GitHub (Sep 18, 2021): > But with the stable release I noticed that sometimes the stable version worked properly with out any errors and sometime it came up with the issues like the one mentioned . So I am confused Yea, that's because the `//wsl$` path isn't accessible until the WSL service (lxss) is already running. So until that service starts, the Terminal thinks that any paths under that root aren't valid paths. I'm going to tentatively call this fixed by #9223, and when 1.11 moves to stable, if that hasn't fixed this issue for you, we can reopen then. Sound good?
claunia commented 2026-01-31 04:32:08 +00:00
Author
Owner
Copy Link

@Trid-collab commented on GitHub (Sep 19, 2021):

Thank you. WIll check it up with 1.11 when I have an access to it

@Trid-collab commented on GitHub (Sep 19, 2021): Thank you. WIll check it up with 1.11 when I have an access to it
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Fix-Available
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15231
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?