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

Cannot preinstall WT package 1.4.3141.0 Windows10_PreinstallKit.zip on Windows Server 10.0.20251.1000 #11370

New Issue
Closed
opened 2026-01-31 02:45:51 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 02:45:51 +00:00
Owner
Copy Link

Originally created by @PGomersall on GitHub (Nov 12, 2020).

Originally assigned to: @DHowett on GitHub.

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Server 10.0.20251.1000
Windows Terminal version (if applicable): N\A

Any other software?

Steps to reproduce

  1. Open elevated Powersell
    Downloaded provided package zip, unblocked and expanded to C:\WT
    Run Add-AppxProvisionedPackage -Online -FolderPath C:\WT
    Add-AppxProvisionedPackage : No applicable main package was found for this platform.
    The directory must contain an applicable package with a .main file extension. For more information, see the help.
    Same result when specifying the msixbunde file with -PackagePath and the license file with -License.
    Using -FolderPath also doesn't work on W10 20H2, but specifying the files specifically does

Expected behavior

Actual behavior

Installs WT for all users should work on Windows Server vNext?

Originally created by @PGomersall on GitHub (Nov 12, 2020). Originally assigned to: @DHowett on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Server 10.0.20251.1000 Windows Terminal version (if applicable): N\A Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1) Open elevated Powersell Downloaded provided package zip, unblocked and expanded to C:\WT Run Add-AppxProvisionedPackage -Online -FolderPath C:\WT Add-AppxProvisionedPackage : No applicable main package was found for this platform. The directory must contain an applicable package with a .main file extension. For more information, see the help. Same result when specifying the msixbunde file with -PackagePath and the license file with -License. Using -FolderPath also doesn't work on W10 20H2, but specifying the files specifically does # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? --> Installs WT for all users should work on Windows Server vNext?
claunia commented 2026-01-31 02:45:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 12, 2020):

Wait what? where are you getting this PreinstallKit.zip file? That doesn't look like something that we ship. IIRC we're only shipping an msixbundle for the packaged release

@zadjii-msft commented on GitHub (Nov 12, 2020): Wait _what_? where are you getting this `PreinstallKit.zip` file? That doesn't look like something that _we_ ship. IIRC we're only shipping an `msixbundle` for the packaged [release](https://github.com/microsoft/terminal/releases)
claunia commented 2026-01-31 02:45:53 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Nov 12, 2020):

https://github.com/microsoft/terminal/releases/download/v1.4.3141.0/Microsoft.WindowsTerminal_1.4.3141.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip

@WSLUser commented on GitHub (Nov 12, 2020): https://github.com/microsoft/terminal/releases/download/v1.4.3141.0/Microsoft.WindowsTerminal_1.4.3141.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip
claunia commented 2026-01-31 02:45:53 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Nov 12, 2020):

@DHowett started issuing them the last release or two ago.

@WSLUser commented on GitHub (Nov 12, 2020): @DHowett started issuing them the last release or two ago.
claunia commented 2026-01-31 02:45:53 +00:00
Author
Owner
Copy Link

@PGomersall commented on GitHub (Nov 12, 2020):

Yes as @WSLUser notes: https://github.com/microsoft/terminal/releases/download/v1.4.3141.0/Microsoft.WindowsTerminal_1.4.3141.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip

@PGomersall commented on GitHub (Nov 12, 2020): Yes as @WSLUser notes: https://github.com/microsoft/terminal/releases/download/v1.4.3141.0/Microsoft.WindowsTerminal_1.4.3141.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip
claunia commented 2026-01-31 02:45:53 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 12, 2020):

Alright well, I'll defer to Dustin then because I have no idea what that is 😄

@zadjii-msft commented on GitHub (Nov 12, 2020): Alright well, I'll defer to Dustin then because I have no idea what that is 😄
claunia commented 2026-01-31 02:45:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 12, 2020):

So you did this successfully on Windows Client? Interesting! Can you grab a copy of C:\Windows\Logs\DISM.log after a failed apply?

We’ve only validated that the PreinstallKit works on Client, so I’m not surprised that there might be an issue here.

@DHowett commented on GitHub (Nov 12, 2020): So you did this successfully on Windows Client? Interesting! Can you grab a copy of `C:\Windows\Logs\DISM.log` after a failed apply? We’ve only validated that the PreinstallKit works on Client, so I’m not surprised that there might be an issue here.
claunia commented 2026-01-31 02:45:54 +00:00
Author
Owner
Copy Link

@PGomersall commented on GitHub (Nov 12, 2020):

@DHowett Yes works on most recent W10 client: 10.0.19042.630
Here you go with the log file:
dism.log
Tried a few different options on\after: 2020-11-12 07:50:34

Note that using the -FolderPath with Add-AppxProvisionedPackage approach also failed on the client. The client only worked specifying the msixbundle file and license file explicitly.

Just installing the msixbundle for each user works though on Server.

@PGomersall commented on GitHub (Nov 12, 2020): @DHowett Yes works on most recent W10 client: 10.0.19042.630 Here you go with the log file: [dism.log](https://github.com/microsoft/terminal/files/5531960/dism.log) Tried a few different options on\after: 2020-11-12 07:50:34 Note that using the -FolderPath with Add-AppxProvisionedPackage approach also failed on the client. The client only worked specifying the msixbundle file and license file explicitly. Just installing the msixbundle for each user works though on Server.
claunia commented 2026-01-31 02:45:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 13, 2020):

This is really strange! Every failure says:

    Msg:[Failed while adding license file '.\6520b63bb369427b9cfbf867f6ab2cb4.msixbundle']

It's as though it's attempting to parse the bundle itself as a license. That seems deeply incorrect.

I'll reach out to the DISM team and see if I can reproduce this on Server myself. 😄

@DHowett commented on GitHub (Nov 13, 2020): This is really strange! Every failure says: ``` Msg:[Failed while adding license file '.\6520b63bb369427b9cfbf867f6ab2cb4.msixbundle'] ``` It's as though it's attempting to parse the bundle itself as a license. That seems deeply incorrect. I'll reach out to the DISM team and see if I can reproduce this on Server myself. :smile:
claunia commented 2026-01-31 02:45:54 +00:00
Author
Owner
Copy Link

@PGomersall commented on GitHub (Oct 11, 2021):

In the GA release of Server 2022 it seems to be fixed.
Install WT using -PackagePath and _LicenseFile works

@PGomersall commented on GitHub (Oct 11, 2021): In the GA release of Server 2022 it seems to be fixed. Install WT using -PackagePath and _LicenseFile works
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 Area-Build Issue-Bug Needs-Tag-Fix Priority-3 Product-Terminal Tracking-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#11370
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?