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

Failed install without usable error message #20787

New Issue
Closed
opened 2026-01-31 07:24:08 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:24:08 +00:00
Owner
Copy Link

Originally created by @cook-1229 on GitHub (Nov 9, 2023).

Windows Terminal version

1.18.2822.0

Windows build number

10.0.19045.0

Other Software

I currently have Terminal 1.15.2524.0 installed. Versions after this have failed (can't promise that I tried all of them).

Steps to reproduce

  1. Download Microsoft.WindowsTerminal_1.18.2822.0_8wekyb3d8bbwe.msixbundle from GitHub.
  2. Run installer. Click "Update" button.

Expected Behavior

Terminal installs, like previous versions.

OR

Terminal tells me exactly what is wrong.

Actual Behavior

Installer reports, "App Installer failed to install package dependencies. Ask the developer for package. "

What package? Where would I look to find this information? I couldn't find a log in the Event Viewer that told me.

Originally created by @cook-1229 on GitHub (Nov 9, 2023). ### Windows Terminal version 1.18.2822.0 ### Windows build number 10.0.19045.0 ### Other Software I currently have Terminal 1.15.2524.0 installed. Versions after this have failed (can't promise that I tried all of them). ### Steps to reproduce 1. Download Microsoft.WindowsTerminal_1.18.2822.0_8wekyb3d8bbwe.msixbundle from GitHub. 2. Run installer. Click "Update" button. ### Expected Behavior Terminal installs, like previous versions. OR Terminal tells me exactly what is wrong. ### Actual Behavior Installer reports, "App Installer failed to install package dependencies. Ask the developer for package. " What package? Where would I look to find this information? I couldn't find a log in the Event Viewer that told me.
claunia commented 2026-01-31 07:24:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 9, 2023):

I'd suspect (without investigating) that 1.16 was around the time we stopped shipping Microsoft.UI.Xaml directly in our package, and instead started relying more on the OS installing dependencies for us. I believe the store is supposed to be able to automatically pull down framework package dependencies. The PreinstallKit might have those dependencies still bundled inside it.

@zadjii-msft commented on GitHub (Nov 9, 2023): I'd suspect (without investigating) that 1.16 was around the time we stopped shipping Microsoft.UI.Xaml directly in our package, and instead started relying more on the OS installing dependencies for us. I believe the store is supposed to be able to automatically pull down framework package dependencies. The PreinstallKit might have those dependencies still bundled inside it.
claunia commented 2026-01-31 07:24:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 9, 2023):

See also:

@zadjii-msft commented on GitHub (Nov 9, 2023): See also: * https://github.com/microsoft/terminal/issues/13558#issuecomment-1192184868 * https://github.com/microsoft/terminal/issues/15512#issuecomment-1577373361 * #13520, though, that Midi dependency should be long gone
claunia commented 2026-01-31 07:24:10 +00:00
Author
Owner
Copy Link

@cook-1229 commented on GitHub (Nov 9, 2023):

Thanks for the quick reply, @zadjii-msft.
I installed Microsoft.UI.Xaml.2.8.x64.appx, and the Terminal installer worked without complaint. I am working on a machine that cannot access the Microsoft Store, and I didn't even know that was the problem.

I would have been able to figure this out for myself if the error message had indicated that Xaml was the missing packing. Note that there is a double space in "for package." I suspect that there is a bug in the installer that is preventing the name of the package from being displayed.

@cook-1229 commented on GitHub (Nov 9, 2023): Thanks for the quick reply, @zadjii-msft. I installed Microsoft.UI.Xaml.2.8.x64.appx, and the Terminal installer worked without complaint. I am working on a machine that cannot access the Microsoft Store, and I didn't even know that was the problem. I would have been able to figure this out for myself if the error message had indicated that Xaml was the missing packing. Note that there is a double space in "for package." I suspect that there is a bug in the installer that is preventing the name of the package from being displayed.
claunia commented 2026-01-31 07:24:10 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 9, 2023):

Well, glad you got that figured out! I think there were some enhancements to that installer in Windows 11 that made that a bit less of a problem, but alas, those fixes didn't make it downlevel.

@zadjii-msft commented on GitHub (Nov 9, 2023): Well, glad you got that figured out! I think there were some enhancements to that installer in Windows 11 that made that a bit less of a problem, but alas, those fixes didn't make it downlevel.
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 Issue-Question Needs-Triage Resolution-Answered 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#20787
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?