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

Installation on Win11 LTSC 2024, not launching #23331

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

Originally created by @nsarzyns on GitHub (Jun 2, 2025).

Installed 1.22.11141 on OS build 10.0.26100.0. Fresh install as well with the only additional software being Notepad++

Both the VClibs and the WT msixbundle were installed using Add-AppxPackage as the system is disconnected. Everything installs without an issue but when trying to run the app by mean of a search, nothing happens. When I try to run it from right clicking on the start menu, I get a popup stating "The file cannot be accessed by the system". If I run wt from a ps window, admin or not, I get a printout about the same error.

Navigating to the AppData folder listed in the error, shows the wt.exe having a size of 0KB. In fact the other exes in that folder also show 0KB. Anyway, heading to it's installed location in ProgramFiles, looks like the whole dir is only granted permission to TrustedInstaller.

I stopped there as something is amiss. Recursively changing permissions can't be the fix...right?

Odd thing is, this issue is somewhat new. I have a systems running Win11 LTSC 2024 with the terminal installed that works fine. It's been updated over time, it's not the latest, I just don't know what version it started at nor do I have access to the system at the moment as it's no longer in the lab.

Originally created by @nsarzyns on GitHub (Jun 2, 2025). Installed 1.22.11141 on OS build 10.0.26100.0. Fresh install as well with the only additional software being Notepad++ Both the VClibs and the WT msixbundle were installed using Add-AppxPackage as the system is disconnected. Everything installs without an issue but when trying to run the app by mean of a search, nothing happens. When I try to run it from right clicking on the start menu, I get a popup stating "The file cannot be accessed by the system". If I run wt from a ps window, admin or not, I get a printout about the same error. Navigating to the AppData folder listed in the error, shows the wt.exe having a size of 0KB. In fact the other exes in that folder also show 0KB. Anyway, heading to it's installed location in ProgramFiles, looks like the whole dir is only granted permission to TrustedInstaller. I stopped there as something is amiss. Recursively changing permissions can't be the fix...right? Odd thing is, this issue is somewhat new. I have a systems running Win11 LTSC 2024 with the terminal installed that works fine. It's been updated over time, it's not the latest, I just don't know what version it started at nor do I have access to the system at the moment as it's no longer in the lab.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 08:39:04 +00:00
claunia commented 2026-01-31 08:39:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 4, 2025):

The file cannot be accessed by the system

You know, this reminds me a lot of the bucket of issues labelled Culprit-Centennial

0kb

Of all the wild things that you're experiencing, this is actually the normal one 😅
App execution aliases store all their relevant information in a reparse point rather, which gets resolved during CreateProcess.

I stopped there as something is amiss. Recursively changing permissions can't be the fix...right?

Good instinct. Those permissions are part of how app launch works 🤨

We'll probably need to get a local repro going on this. Thanks for the clean repro steps!

--

As a quick thought: if you do a Repair in the app-specific settings page, does anything change?

@DHowett commented on GitHub (Jun 4, 2025): > The file cannot be accessed by the system You know, this reminds me a lot of the [bucket of issues labelled `Culprit-Centennial`](https://github.com/microsoft/terminal/issues?q=is%3Aissue%20state%3Aopen%20label%3ACulprit-Centennial) > 0kb Of all the wild things that you're experiencing, this is actually the normal one 😅 App execution aliases store all their relevant information in a reparse point rather, which gets resolved during `CreateProcess`. > I stopped there as something is amiss. Recursively changing permissions can't be the fix...right? Good instinct. Those permissions are part of how app launch works 🤨 We'll probably need to get a local repro going on this. Thanks for the clean repro steps! -- As a quick thought: if you do a `Repair` in the app-specific settings page, does anything change?
claunia commented 2026-01-31 08:39:05 +00:00
Author
Owner
Copy Link

@nsarzyns commented on GitHub (Jun 4, 2025):

I think I fixed it!

For your question about doing the Repair in the app settings; I did try that, no luck.

I tried to recall why the one system I had the terminal working on with the same base OS, works. I was experimenting with FFU deployments at the time and to get the terminal to work on a deployed system and persist after a sysprep I needed to use Add-AppxProvisionedPackage.

So I tried just that. After installing the deps and the main win terminal packages with Add-AppxPackage. I ran:

Add-AppxProvisionedPackage -Online -PackagePath <Path_to_winTerm_msix> -LicensePath <Lic_xml_in_Win10_PreInstall_Kit> -Regions all

And now it launches perfectly fine in all the ways I'd expect to be able to.

I can't understand why though I need to provision the package on an OS install where there is only one usable account. These same steps are also needed for Win11 IoT LTSC. Very well might have to do with the missing Microsoft Store component in LTSC. I don't recall needing to provision the package in Windows Server which also doesn't have the store component. But hey, it works now

@nsarzyns commented on GitHub (Jun 4, 2025): I think I fixed it! For your question about doing the Repair in the app settings; I did try that, no luck. I tried to recall why the one system I had the terminal working on with the same base OS, works. I was experimenting with FFU deployments at the time and to get the terminal to work on a deployed system and persist after a sysprep I needed to use Add-AppxProvisionedPackage. So I tried just that. After installing the deps and the main win terminal packages with Add-AppxPackage. I ran: `Add-AppxProvisionedPackage -Online -PackagePath <Path_to_winTerm_msix> -LicensePath <Lic_xml_in_Win10_PreInstall_Kit> -Regions all` And now it launches perfectly fine in all the ways I'd expect to be able to. I can't understand why though I need to provision the package on an OS install where there is only one usable account. These same steps are also needed for Win11 IoT LTSC. Very well might have to do with the missing Microsoft Store component in LTSC. I don't recall needing to provision the package in Windows Server which also doesn't have the store component. But hey, it works now
claunia commented 2026-01-31 08:39:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 18, 2025):

I think I fixed it!

🎉 thanks for following up!

I can't understand why though I need to provision the package on an OS install where there is only one usable account

That's an excellent question. I have long since given up on trying to figure out why parts of the app platform behave the way they do 😁

@DHowett commented on GitHub (Jun 18, 2025): > I think I fixed it! :tada: thanks for following up! > I can't understand why though I need to provision the package on an OS install where there is only one usable account That's an excellent question. I have long since given up on trying to figure out why parts of the app platform behave the way they do 😁
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-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#23331
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?