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

fail to launch WSL (both 1 and 2) from terminal after update to win 11 Build 22581.ni_release.220318-1623 #17071

New Issue
Open
opened 2026-01-31 05:31:29 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:31:29 +00:00
Owner
Copy Link

Originally created by @Fan-iX on GitHub (Mar 25, 2022).

Windows Terminal version

1.12.10393.0

Windows build number

Win32NT 10.0.22581.0 Microsoft Windows NT 10.0.22581.0

Other Software

WSL version: 0.56.2.0
kernel version: 5.10.102.1
WSLg version: 1.0.30
MSRDC version: 1.2.2924
Direct3D version: 1.601.0

Steps to reproduce

  1. terminal profile:
            {
                "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
                "name": "Ubuntu-20.04",  // WSL2
                "source": "Windows.Terminal.Wsl",
                "startingDirectory": "./"
            },
            {
                "guid": "{7a4f49f3-6d68-54b0-90c4-fbd31328a0f9}",
                "name": "Ubuntu.20.04",  // WSL1
                "startingDirectory": "./",
                "source": "Windows.Terminal.Wsl"
            }
  1. Start up WSL directly from windows terminal.
  2. Start up WSL from wsl -d Ubuntu-20.04 or wsl -d Ubuntu.20.04 from PowerShell, or from Win+r.

Expected Behavior

WSL starts.

Actual Behavior

  1. Both WSL1 and WSL2 failed to start up if launched from Windows Terminal:
The parameter is incorrect.

[process exited with code 4294967295 (0xffffffff)]
  1. Both WSL1 and WSL2 started up and worked properly when launched by PowerShell wsl -d Ubuntu-20.04, or Win+r wsl -d Ubuntu-20.04
Originally created by @Fan-iX on GitHub (Mar 25, 2022). ### Windows Terminal version 1.12.10393.0 ### Windows build number Win32NT 10.0.22581.0 Microsoft Windows NT 10.0.22581.0 ### Other Software WSL version: 0.56.2.0 kernel version: 5.10.102.1 WSLg version: 1.0.30 MSRDC version: 1.2.2924 Direct3D version: 1.601.0 ### Steps to reproduce 0. terminal profile: ``` { "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}", "name": "Ubuntu-20.04", // WSL2 "source": "Windows.Terminal.Wsl", "startingDirectory": "./" }, { "guid": "{7a4f49f3-6d68-54b0-90c4-fbd31328a0f9}", "name": "Ubuntu.20.04", // WSL1 "startingDirectory": "./", "source": "Windows.Terminal.Wsl" } ``` 1. Start up WSL directly from windows terminal. 2. Start up WSL from `wsl -d Ubuntu-20.04` or `wsl -d Ubuntu.20.04` from PowerShell, or from <kbd>Win</kbd>+<kbd>r</kbd>. ### Expected Behavior WSL starts. ### Actual Behavior 1. Both WSL1 and WSL2 failed to start up if launched from Windows Terminal: ``` The parameter is incorrect. [process exited with code 4294967295 (0xffffffff)] ``` 2. Both WSL1 and WSL2 started up and worked properly when launched by PowerShell `wsl -d Ubuntu-20.04`, or <kbd>Win</kbd>+<kbd>r</kbd> `wsl -d Ubuntu-20.04`
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 05:31:29 +00:00
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 Issue-Bug Needs-Tag-Fix Needs-Triage
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#17071
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?