Installation on Win11 LTSC 2024, not launching

[nsarzyns]

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.

[DHowett]

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?

[nsarzyns]

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

[DHowett]

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 😁