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

Terminal installation location keeps changing #23712

New Issue
Closed
opened 2026-01-31 08:50:09 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:50:09 +00:00
Owner
Copy Link

Originally created by @vborovikov on GitHub (Oct 16, 2025).

Is there any way to control where the Terminal executables are being installed? Currently on my machine it's C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.23.12811.0_x64__8wekyb3d8bbwe\ but this path slightly changes with each upgrade.

I need a constant location where the app and its upgrades reside. My auto keyboard layout switcher stops working with the Terminal after each upgrade and I have to look up where the Terminal executable is.

Originally created by @vborovikov on GitHub (Oct 16, 2025). Is there any way to control where the Terminal executables are being installed? Currently on my machine it's `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.23.12811.0_x64__8wekyb3d8bbwe\` but this path slightly changes with each upgrade. I need a constant location where the app and its upgrades reside. My auto keyboard layout switcher stops working with the Terminal after each upgrade and I have to look up where the Terminal executable is.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 08:50:10 +00:00
claunia commented 2026-01-31 08:50:11 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 16, 2025):

Unfortunately, there's no way for us to influence this. The platform decides how and where to install packaged apps, not us. It is very easy to programmatically find the location of a packaged application, however, so perhaps you can write a script to do this, or your keyboard layout switcher app could add support for packaged apps.

@lhecker commented on GitHub (Oct 16, 2025): Unfortunately, there's no way for us to influence this. The platform decides how and where to install packaged apps, not us. It is very easy to programmatically find the location of a packaged application, however, so perhaps you can write a script to do this, or your keyboard layout switcher app could add support for packaged apps.
claunia commented 2026-01-31 08:50:11 +00:00
Author
Owner
Copy Link

@vborovikov commented on GitHub (Oct 16, 2025):

Can I replace the packaged version with the unpackaged version? I see in the Releases tab some zip-files with executables in it?

@vborovikov commented on GitHub (Oct 16, 2025): Can I replace the packaged version with the unpackaged version? I see in the Releases tab some zip-files with executables in it?
claunia commented 2026-01-31 08:50:11 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 16, 2025):

Depends on what you mean with "replace". If you mean to ask if you can just use the unpackaged version as your daily driver, then yes. It's the same thing as the packaged version. The only difference is that if you launch cmd from the start menu or something it won't open in your unpackaged version.

@lhecker commented on GitHub (Oct 16, 2025): Depends on what you mean with "replace". If you mean to ask if you can just use the unpackaged version as your daily driver, then yes. It's the same thing as the packaged version. The only difference is that if you launch `cmd` from the start menu or something it won't open in your unpackaged version.
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
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#23712
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?