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

Windows Terminal unavailable immediately after logging into a sysprep Windows 11 image #18159

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

Originally created by @CodeCyclone on GitHub (Aug 11, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

Create an Azure VM with Windows 11 Enterprise image that had sysprep performed.
Login to machine and try to launch Windows Terminal via Start Menu or wt.exe.

Expected Behavior

Windows Terminal is immediately available after first login on a fresh Windows 11 machine that had sysprep performed previously.

Actual Behavior

The wt.exe doesn't respond or shows as not found after login. In Start Menu, if you click Windows Terminal it doesn't launch.

After some time the issue corrects itself and you can launch Windows Terminal but it can be 10+ minutes in some cases.
It is an intermittent issue, doesn't always reproduce.

Have tried to wait for it to become available but 10 minutes is too long to wait. Tried to install Appx packages directly on Windows 11 but it takes Windows Terminal a long time to become available even in this scenario too.

An example of this is the output below, each wait is 5 seconds (2.5 min) which is after installing AppX:

WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax.
Package Microsoft.VCLibs.140.00 is already installed and up-to-date.
WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax.
Package Microsoft.VCLibs.140.00.UWPDesktop is already installed and up-to-date.
WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax.
Package Microsoft.DesktopAppInstaller is already installed and up-to-date.
        Waiting for Windows Terminal...attempt #1 out of 30
        Waiting for Windows Terminal...attempt #2 out of 30
        Waiting for Windows Terminal...attempt #3 out of 30
        Waiting for Windows Terminal...attempt #4 out of 30
        Waiting for Windows Terminal...attempt #5 out of 30
        Waiting for Windows Terminal...attempt #6 out of 30
        Waiting for Windows Terminal...attempt #7 out of 30
        Waiting for Windows Terminal...attempt #8 out of 30
        Waiting for Windows Terminal...attempt #9 out of 30
        Waiting for Windows Terminal...attempt #10 out of 30
        Waiting for Windows Terminal...attempt #11 out of 30
        Waiting for Windows Terminal...attempt #12 out of 30
        Waiting for Windows Terminal...attempt #13 out of 30
        Waiting for Windows Terminal...attempt #14 out of 30
        Waiting for Windows Terminal...attempt #15 out of 30
        Waiting for Windows Terminal...attempt #16 out of 30
        Waiting for Windows Terminal...attempt #17 out of 30
        Waiting for Windows Terminal...attempt #18 out of 30
        Waiting for Windows Terminal...attempt #19 out of 30
        Waiting for Windows Terminal...attempt #20 out of 30
        Waiting for Windows Terminal...attempt #21 out of 30
        Waiting for Windows Terminal...attempt #22 out of 30
        Waiting for Windows Terminal...attempt #23 out of 30
        Waiting for Windows Terminal...attempt #24 out of 30
        Waiting for Windows Terminal...attempt #25 out of 30
        Waiting for Windows Terminal...attempt #26 out of 30
        Waiting for Windows Terminal...attempt #27 out of 30
        Waiting for Windows Terminal...attempt #28 out of 30
        Waiting for Windows Terminal...attempt #29 out of 30
        Waiting for Windows Terminal...attempt #30 out of 30
WARNING: Windows Terminal wasn't detected
Originally created by @CodeCyclone on GitHub (Aug 11, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce Create an Azure VM with Windows 11 Enterprise image that had sysprep performed. Login to machine and try to launch Windows Terminal via Start Menu or wt.exe. ### Expected Behavior Windows Terminal is immediately available after first login on a fresh Windows 11 machine that had sysprep performed previously. ### Actual Behavior The wt.exe doesn't respond or shows as not found after login. In Start Menu, if you click Windows Terminal it doesn't launch. After some time the issue corrects itself and you can launch Windows Terminal but it can be 10+ minutes in some cases. It is an intermittent issue, doesn't always reproduce. Have tried to wait for it to become available but 10 minutes is too long to wait. Tried to install Appx packages directly on Windows 11 but it takes Windows Terminal a long time to become available even in this scenario too. An example of this is the output below, each wait is 5 seconds (2.5 min) which is after installing AppX: ``` WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax. Package Microsoft.VCLibs.140.00 is already installed and up-to-date. WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax. Package Microsoft.VCLibs.140.00.UWPDesktop is already installed and up-to-date. WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax. Package Microsoft.DesktopAppInstaller is already installed and up-to-date. Waiting for Windows Terminal...attempt #1 out of 30 Waiting for Windows Terminal...attempt #2 out of 30 Waiting for Windows Terminal...attempt #3 out of 30 Waiting for Windows Terminal...attempt #4 out of 30 Waiting for Windows Terminal...attempt #5 out of 30 Waiting for Windows Terminal...attempt #6 out of 30 Waiting for Windows Terminal...attempt #7 out of 30 Waiting for Windows Terminal...attempt #8 out of 30 Waiting for Windows Terminal...attempt #9 out of 30 Waiting for Windows Terminal...attempt #10 out of 30 Waiting for Windows Terminal...attempt #11 out of 30 Waiting for Windows Terminal...attempt #12 out of 30 Waiting for Windows Terminal...attempt #13 out of 30 Waiting for Windows Terminal...attempt #14 out of 30 Waiting for Windows Terminal...attempt #15 out of 30 Waiting for Windows Terminal...attempt #16 out of 30 Waiting for Windows Terminal...attempt #17 out of 30 Waiting for Windows Terminal...attempt #18 out of 30 Waiting for Windows Terminal...attempt #19 out of 30 Waiting for Windows Terminal...attempt #20 out of 30 Waiting for Windows Terminal...attempt #21 out of 30 Waiting for Windows Terminal...attempt #22 out of 30 Waiting for Windows Terminal...attempt #23 out of 30 Waiting for Windows Terminal...attempt #24 out of 30 Waiting for Windows Terminal...attempt #25 out of 30 Waiting for Windows Terminal...attempt #26 out of 30 Waiting for Windows Terminal...attempt #27 out of 30 Waiting for Windows Terminal...attempt #28 out of 30 Waiting for Windows Terminal...attempt #29 out of 30 Waiting for Windows Terminal...attempt #30 out of 30 WARNING: Windows Terminal wasn't detected ```
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#18159
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?