starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Unable to install Windows terminal #8550

New Issue
Closed
opened 2026-01-31 01:32:11 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 01:32:11 +00:00
Owner
Copy Link

Originally created by @HounD on GitHub (May 24, 2020).

Hello!
I failed to install Windows terminal both downloading it from github page and installing with winget tool.

For the dowloaded file I got such output:
PS C:\Users\localuser\Downloads> add-appxpackage Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle
add-appxpackage : Deployment failed with HRESULT: 0x80073CF0, Package could not be opened.
error 0x8007007B: Opening the package from location Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle failed.
NOTE: For additional information, look for [ActivityId] 3736654a-298c-0004-6cc8-4f378c29d601 in the Event Log or use the command line Get-AppxLog -ActivityID 3736654a-298c-0004-6cc8-4f378c29d601
At line:1 char:1

  • add-appxpackage Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.ms ...
  •   + CategoryInfo          : OpenError: (C:\Users\localu...bbwe.msixbundle:String) [Add-AppxPackage], FileNotFoundException
  + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

PS C:\Users\localuser\Downloads> Get-AppxLog -ActivityID 3736654a-298c-0004-6cc8-4f378c29d601

Time ID Message

5/24/2020 2:36:42 PM 603 Started deployment Add operation on a package with main parameter: Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle and Options: 0 and 0. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
5/24/2020 2:36:42 PM 164 The app bundle signature was validated for core content of the app bundle published by CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond,
S=Washington, C=US. App packages won't be validated until they are read.
5/24/2020 2:36:42 PM 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com/appx/2018/bundle is inapplicable, it will be ignored during manifest
processing.
5/24/2020 2:36:42 PM 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com/appx/2019/bundle is inapplicable, it will be ignored during manifest
processing.
5/24/2020 2:36:42 PM 465 error 0x8007007B: Opening the package from location Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle failed.
5/24/2020 2:36:42 PM 403 error 0x8007007B: Failure to get staging session for: file:///C:/Users/localuser/Downloads/Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle.
5/24/2020 2:36:42 PM 404 AppX Deployment operation failed for package with error 0x80073CF0. The specific error text for this failure is: error 0x8007007B: Opening the package from
location Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle failed.

For winget tool:
PS C:\Users\localuser\Downloads> winget install "Windows Terminal"
Found Windows Terminal [Microsoft.WindowsTerminal]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/microsoft/terminal/releases/download/v1.0.1401.0/Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle
██████████████████████████████ 18.1 MB / 18.1 MB
Successfully verified installer hash
Starting package install...
Install failed: error 0x8007007B: Opening the package from location Microsoft.WindowsTerminal.1.0.1401.0 failed.
0x8007007b : The filename, directory name, or volume label syntax is incorrect.

In the both cases I was unable to install

Originally created by @HounD on GitHub (May 24, 2020). Hello! I failed to install Windows terminal both downloading it from github page and installing with winget tool. For the dowloaded file I got such output: PS C:\Users\localuser\Downloads> add-appxpackage Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle add-appxpackage : Deployment failed with HRESULT: 0x80073CF0, Package could not be opened. error 0x8007007B: Opening the package from location Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle failed. NOTE: For additional information, look for [ActivityId] 3736654a-298c-0004-6cc8-4f378c29d601 in the Event Log or use the command line Get-AppxLog -ActivityID 3736654a-298c-0004-6cc8-4f378c29d601 At line:1 char:1 + add-appxpackage Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.ms ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (C:\Users\localu...bbwe.msixbundle:String) [Add-AppxPackage], FileNotFoundException + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand PS C:\Users\localuser\Downloads> Get-AppxLog -ActivityID 3736654a-298c-0004-6cc8-4f378c29d601 Time ID Message ---- -- ------- 5/24/2020 2:36:42 PM 603 Started deployment Add operation on a package with main parameter: Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle and Options: 0 and 0. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. 5/24/2020 2:36:42 PM 164 The app bundle signature was validated for core content of the app bundle published by CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US. App packages won't be validated until they are read. 5/24/2020 2:36:42 PM 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com/appx/2018/bundle is inapplicable, it will be ignored during manifest processing. 5/24/2020 2:36:42 PM 216 App manifest validation warning: Declared namespace http://schemas.microsoft.com/appx/2019/bundle is inapplicable, it will be ignored during manifest processing. 5/24/2020 2:36:42 PM 465 error 0x8007007B: Opening the package from location Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle failed. 5/24/2020 2:36:42 PM 403 error 0x8007007B: Failure to get staging session for: file:///C:/Users/localuser/Downloads/Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle. 5/24/2020 2:36:42 PM 404 AppX Deployment operation failed for package with error 0x80073CF0. The specific error text for this failure is: error 0x8007007B: Opening the package from location Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle failed. For winget tool: PS C:\Users\localuser\Downloads> winget install "Windows Terminal" Found Windows Terminal [Microsoft.WindowsTerminal] This application is licensed to you by its owner. Microsoft is not responsible for, nor does it grant any licenses to, third-party packages. Downloading https://github.com/microsoft/terminal/releases/download/v1.0.1401.0/Microsoft.WindowsTerminal_1.0.1401.0_8wekyb3d8bbwe.msixbundle ██████████████████████████████ 18.1 MB / 18.1 MB Successfully verified installer hash Starting package install... Install failed: error 0x8007007B: Opening the package from location Microsoft.WindowsTerminal.1.0.1401.0 failed. 0x8007007b : The filename, directory name, or volume label syntax is incorrect. In the both cases I was unable to install
claunia commented 2026-01-31 01:32:13 +00:00
Author
Owner
Copy Link

@darkRaspberry commented on GitHub (May 24, 2020):

try installing from microsoft store

@darkRaspberry commented on GitHub (May 24, 2020): try installing from microsoft store
claunia commented 2026-01-31 01:32:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2020):

That's certainly curious. 0x8007007B is

ERROR_INVALID_NAME The filename, directory name, or volume label syntax is incorrect.

Which doesn't totally make sense for this, but I don't know too much about how appx deployment works.

@HounD Which version of windows are you running?

@zadjii-msft commented on GitHub (May 28, 2020): That's certainly curious. `0x8007007B` is ERROR_INVALID_NAME | The filename, directory name, or volume label syntax is incorrect. -- | -- Which doesn't totally make sense for this, but I don't know too much about how appx deployment works. @HounD Which version of windows are you running?
claunia commented 2026-01-31 01:32:14 +00:00
Author
Owner
Copy Link

@HounD commented on GitHub (May 28, 2020):

That's certainly curious. 0x8007007B is

ERROR_INVALID_NAME The filename, directory name, or volume label syntax is incorrect.
Which doesn't totally make sense for this, but I don't know too much about how appx deployment works.

@HounD Which version of windows are you running?

C:\Users\localuser>systeminfo | findstr Build
OS Version: 10.0.17134 N/A Build 17134
OS Build Type: Multiprocessor Free

@HounD commented on GitHub (May 28, 2020): > That's certainly curious. `0x8007007B` is > > ERROR_INVALID_NAME The filename, directory name, or volume label syntax is incorrect. > Which doesn't totally make sense for this, but I don't know too much about how appx deployment works. > > @HounD Which version of windows are you running? C:\Users\localuser>systeminfo | findstr Build OS Version: 10.0.17134 N/A Build 17134 OS Build Type: Multiprocessor Free
claunia commented 2026-01-31 01:32:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2020):

Welp there you go. From the README:

👉 Note: Windows Terminal requires Windows 10 1903 (build 18362) or later

@zadjii-msft commented on GitHub (May 28, 2020): Welp there you go. From the [README](https://github.com/microsoft/terminal#installing-and-running-windows-terminal): > 👉 Note: Windows Terminal requires Windows 10 1903 (build 18362) or later
claunia commented 2026-01-31 01:32:15 +00:00
Author
Owner
Copy Link

@numpythuckles commented on GitHub (Jun 4, 2020):

This is still a problem. Running into it on 1909.

@numpythuckles commented on GitHub (Jun 4, 2020): This is still a problem. Running into it on 1909.
claunia commented 2026-01-31 01:32:15 +00:00
Author
Owner
Copy Link

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

I have reported a similar issue here. Two reasons come to mind:

  • I am using an old version of Windows that doesn't support MSIX
  • I don't have admin rights

Both issues could be solved if Microsoft would publish a portable .exe of the Windows Terminal as I have suggested in this Tweet.

@Foadsf commented on GitHub (Nov 12, 2020): I have reported a similar issue [here](https://superuser.com/q/1601487/588662). Two reasons come to mind: - I am using an old version of Windows that doesn't support MSIX - I don't have admin rights Both issues could be solved if Microsoft would publish a portable `.exe` of the Windows Terminal as I have suggested in [this Tweet](https://twitter.com/fsfarimani/status/1326862105828581376?s=20).
claunia commented 2026-01-31 01:32:15 +00:00
Author
Owner
Copy Link

@browolf commented on GitHub (Nov 15, 2022):

I get this error on a 2016 server. I guess that's too old.

@browolf commented on GitHub (Nov 15, 2022): I get this error on a 2016 server. I guess that's too old.
claunia commented 2026-01-31 01:32:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 16, 2022):

@browolf yep. See the FAQs.

@zadjii-msft commented on GitHub (Nov 16, 2022): @browolf yep. [See the FAQs](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#can-i-use-the-terminal-on-windows-7-windows-server-2019-any-other-down-level-windows-version).
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-Attention Needs-Tag-Fix Needs-Triage Product-Terminal Resolution-Answered
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#8550
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?