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

wt app execution alias slow to be created in fresh Windows install/profile creation? #15987

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

Originally created by @jeremyd2019 on GitHub (Nov 29, 2021).

Windows Terminal version

1.11.2921.0

Windows build number

10.0.22000.318

Other Software

No response

Steps to reproduce

Use an Unattend.xml to set up a fresh Windows install. As part of that, have a synchronousCommand in the oobeSystem stage that sets up a .cmd script that uses wt (among other things), set that up to auto-run, and reboot the system.

Expected Behavior

Windows Terminal would open from the cmd script run after reboot.

Actual Behavior

It opens on a machine that takes a long time to run the oobeSystem synchronousCommands, but on a faster system it does not. I suspect that there's some background process that populates the app execution aliases of preinstalled/provisioned apps. I tried to hurry this along by using the "Preinstall" zip and dism /Online /Add-ProvisionedAppxPackage, which works to install the newer version of Windows Terminal than what shipped in Windows 11, but doesn't seem to help with wt being unavailable on a fast machine.

Is there a command I can run (from CMD) that would "kick" things and make sure the wt alias will be available "now" (or at least immediately post-reboot)?

Originally created by @jeremyd2019 on GitHub (Nov 29, 2021). ### Windows Terminal version 1.11.2921.0 ### Windows build number 10.0.22000.318 ### Other Software _No response_ ### Steps to reproduce Use an Unattend.xml to set up a fresh Windows install. As part of that, have a synchronousCommand in the oobeSystem stage that sets up a .cmd script that uses wt (among other things), set that up to auto-run, and reboot the system. ### Expected Behavior Windows Terminal would open from the cmd script run after reboot. ### Actual Behavior It opens on a machine that takes a long time to run the oobeSystem synchronousCommands, but on a faster system it does not. I suspect that there's some background process that populates the app execution aliases of preinstalled/provisioned apps. I tried to hurry this along by using the "Preinstall" zip and `dism /Online /Add-ProvisionedAppxPackage`, which works to install the newer version of Windows Terminal than what shipped in Windows 11, but doesn't seem to help with wt being unavailable on a fast machine. Is there a command I can run (from CMD) that would "kick" things and make sure the `wt` alias will be available "now" (or at least immediately post-reboot)?
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 Culprit-Centennial Issue-Question Needs-Tag-Fix Needs-Triage Resolution-External
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#15987
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?