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

Error 0xffffffff starting WSL from WT #19613

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

Originally created by @angelog0 on GitHub (Mar 30, 2023).

Windows Terminal version

1.16.230126001

Windows build number

Microsoft Windows [Versione 10.0.19045.2788]

Other Software

No response

Steps to reproduce

I reported this also to WSL people #9875

I used WSL since it was added to W10 and followed its evolution migrating from WSL1 to WSL2 when it was added. I enabled systemd a few months ago and all worked just fine until today.

Now when I start WSL fro Windows Terminal (WT) it prints

[processo terminato con codice 4294967295 (0xffffffff)]

and in WT prints the message It is possible to configure termination... bla bla

I upgraded WT 1.16.230126001 on January from the msixbundle package and worked just fine

Now I get the above error: it occurs only when I start WSL from WT!!! If I start it using MinTTY, with a link (lnk) whose target is

C:\msys64\usr\bin\mintty.exe -c C:\msys64\home\user\.minttyrc -t "WSL Terminal" --position 20,450 /usr/bin/wslbridge2.exe -d Ubuntu -W "~"

WSL starts without error. As workaround, to start it from WT, I have to reboot but I can only start it once: if I close the Ubuntu tab and restart it the error reappears...

I did not change anything in the configuration: both in Windows and in WSL or WT. May be a Windows upgrade? there was one few days ago.. but until yesterday all worked.. I did also a windows cleaning (System - Archive - temp files etc..) but I worked with WSL up to March 29 21:47 (a timestamp of a file produced by TeXLive) so it is a mistery why now it does not work from WT but only with MinTTY...

Expected Behavior

WSL should start

Actual Behavior

WSL gives the above error

Originally created by @angelog0 on GitHub (Mar 30, 2023). ### Windows Terminal version 1.16.230126001 ### Windows build number Microsoft Windows [Versione 10.0.19045.2788] ### Other Software _No response_ ### Steps to reproduce I reported this also to WSL people [#9875](https://github.com/microsoft/WSL/issues/9875#issue-1648081978) I used WSL since it was added to W10 and followed its evolution migrating from WSL1 to WSL2 when it was added. I enabled [systemd](https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/#set-the-systemd-flag-set-in-your-wsl-distro-settings) a few months ago and **all worked just fine until today**. Now when I start WSL fro Windows Terminal (WT) it prints ``` [processo terminato con codice 4294967295 (0xffffffff)] ``` and in WT prints the message `It is possible to configure termination... bla bla` I upgraded `WT 1.16.230126001` on January from the msixbundle package and worked just fine Now I get the above error: **it occurs only when I start WSL from WT!!!** If I start it using MinTTY, with a link (lnk) whose target is ``` C:\msys64\usr\bin\mintty.exe -c C:\msys64\home\user\.minttyrc -t "WSL Terminal" --position 20,450 /usr/bin/wslbridge2.exe -d Ubuntu -W "~" ``` **WSL starts without error.** As workaround, to start it from WT, I have to reboot but I can only start it once: if I close the Ubuntu tab and restart it the error reappears... I did not change anything in the configuration: both in Windows and in WSL or WT. May be a Windows upgrade? there was one few days ago.. but until yesterday all worked.. I did also a windows cleaning (System - Archive - temp files etc..) but I worked with WSL up to March 29 21:47 (a timestamp of a file produced by TeXLive) so it is a mistery why now it does not work from WT but only with MinTTY... ### Expected Behavior WSL should start ### Actual Behavior WSL gives the above error
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 06:48:44 +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-Attention 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#19613
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?