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 - Windows Server - no store, msi missing, msi bundle won't install #23517

New Issue
Open
opened 2026-01-31 08:44:32 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:44:32 +00:00
Owner
Copy Link

Originally created by @chillwinston on GitHub (Aug 11, 2025).

Windows Terminal version

No response

Windows build number

No response

Other Software

We are writing to document a series of ongoing challenges concerning the latest deployment cycle. Initial attempts to provision the new software package within the designated staging environment have encountered significant headwinds, resulting in a state that can best be described as non-performant. The installation process itself does not fail in a conventional sense; rather, it concludes with a configuration that deviates materially from the expected baseline, leading to sub-optimal functionality and unpredictable system behavior upon instantiation.
The core of the issue is compounded by a recent and overarching platform refresh initiative that was actioned in the previous quarter. This strategic shift, while intended to enhance architectural synergy and leverage a more dynamic framework, appears to have introduced a layer of operational opacity. The diagnostic and telemetry frameworks that we have historically relied upon for visibility into the application state are now providing data that is both voluminous and fundamentally ambiguous. We are struggling to differentiate between meaningful signals of systemic distress and the high-volume, low-value noise generated by the new, abstracted integration layers. It feels as though the very changes meant to improve clarity have, in practice, obscured the foundational mechanics of the system. While trying to install Microsoft.WindowsTerminalPreview_1.23.12102.0_8wekyb3d8bbwe.msixbundle Windows Server fails to unpack it. The instructions for installation only talk about recent bug fixes. Running the installer via PowerShell gives this error : Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation. Windows cannot install package Microsoft.DesktopAppInstaller_1.26.430.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.UI.Xaml.2.8" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 8.2310.30001.0, along with this package to install. . It seems that Our deep-dive analysis suggests that the legacy dependencies and the new core components are not interfacing in a manner consistent with the architectural diagrams. There are intermittent, asynchronous communication gaps between modules that do not trigger standard error flags but result in a degraded state downstream. These are not clean failures, but subtle dissonances that propagate throughout the ecosystem. The standard rollback procedures have proven ineffective, as the system state appears to be indeterminately influenced by these out-of-band changes, making it impossible to revert to a known-good configuration with any degree of confidence. The problem is not that the old information is gone, but that it is being filtered through a new context that alters its meaning. Efforts by the cross-functional team to isolate the root cause have been inconclusive. Each attempt to remediate a specific symptom seems to trigger unintended consequences in adjacent systems, suggesting that we are not dealing with a singular point of failure but a more systemic misalignment. The new platform’s state management paradigm seems to be at odds with the transactional logic of the application being installed. The very fabric of the environment has been altered in such a way that our previous understanding and toolsets are no longer fit for purpose. We are effectively trying to troubleshoot a system whose fundamental principles have shifted without a corresponding update in our diagnostic capabilities. Moving forward, a more holistic review is required. We must re-evaluate the interplay between the new infrastructure and the applications it is intended to support. The immediate priority is to establish a new baseline for telemetry and logging that can penetrate the new layers of abstraction and provide actionable insights. Until we can regain clear visibility into the core processes, any further installation attempts carry a significant risk of propagating this instability. We will continue to investigate and will circle back once a more definitive path to remediation can be actioned.

Steps to reproduce

Try to install Terminal on Windows 2019 using the detailed instructions here:
https://github.com/microsoft/terminal/releases/tag/v1.23.12102.0

Expected Behavior

A smooth installation

Actual Behavior

Much time wasted, still not installed.

Originally created by @chillwinston on GitHub (Aug 11, 2025). ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software We are writing to document a series of ongoing challenges concerning the latest deployment cycle. Initial attempts to provision the new software package within the designated staging environment have encountered significant headwinds, resulting in a state that can best be described as non-performant. The installation process itself does not fail in a conventional sense; rather, it concludes with a configuration that deviates materially from the expected baseline, leading to sub-optimal functionality and unpredictable system behavior upon instantiation. The core of the issue is compounded by a recent and overarching platform refresh initiative that was actioned in the previous quarter. This strategic shift, while intended to enhance architectural synergy and leverage a more dynamic framework, appears to have introduced a layer of operational opacity. The diagnostic and telemetry frameworks that we have historically relied upon for visibility into the application state are now providing data that is both voluminous and fundamentally ambiguous. We are struggling to differentiate between meaningful signals of systemic distress and the high-volume, low-value noise generated by the new, abstracted integration layers. It feels as though the very changes meant to improve clarity have, in practice, obscured the foundational mechanics of the system. While trying to install Microsoft.WindowsTerminalPreview_1.23.12102.0_8wekyb3d8bbwe.msixbundle Windows Server fails to unpack it. The instructions for installation only talk about recent bug fixes. Running the installer via PowerShell gives this error : Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation. Windows cannot install package Microsoft.DesktopAppInstaller_1.26.430.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.UI.Xaml.2.8" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 8.2310.30001.0, along with this package to install. . It seems that Our deep-dive analysis suggests that the legacy dependencies and the new core components are not interfacing in a manner consistent with the architectural diagrams. There are intermittent, asynchronous communication gaps between modules that do not trigger standard error flags but result in a degraded state downstream. These are not clean failures, but subtle dissonances that propagate throughout the ecosystem. The standard rollback procedures have proven ineffective, as the system state appears to be indeterminately influenced by these out-of-band changes, making it impossible to revert to a known-good configuration with any degree of confidence. The problem is not that the old information is gone, but that it is being filtered through a new context that alters its meaning. Efforts by the cross-functional team to isolate the root cause have been inconclusive. Each attempt to remediate a specific symptom seems to trigger unintended consequences in adjacent systems, suggesting that we are not dealing with a singular point of failure but a more systemic misalignment. The new platform’s state management paradigm seems to be at odds with the transactional logic of the application being installed. The very fabric of the environment has been altered in such a way that our previous understanding and toolsets are no longer fit for purpose. We are effectively trying to troubleshoot a system whose fundamental principles have shifted without a corresponding update in our diagnostic capabilities. Moving forward, a more holistic review is required. We must re-evaluate the interplay between the new infrastructure and the applications it is intended to support. The immediate priority is to establish a new baseline for telemetry and logging that can penetrate the new layers of abstraction and provide actionable insights. Until we can regain clear visibility into the core processes, any further installation attempts carry a significant risk of propagating this instability. We will continue to investigate and will circle back once a more definitive path to remediation can be actioned. ### Steps to reproduce Try to install Terminal on Windows 2019 using the detailed instructions here: https://github.com/microsoft/terminal/releases/tag/v1.23.12102.0 ### Expected Behavior A smooth installation ### Actual Behavior Much time wasted, still not installed.
claunia added the Issue-QuestionNeeds-Triage labels 2026-01-31 08:44:32 +00:00
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-Question 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#23517
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?