microsoft / microsoft/terminal
Process has no package identity
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
### Windows Terminal version
1.17.10234.0
### Windows build number
10.0.19044.2486
### Other Software
_No response_
### Steps to reproduce
I am working on a locked down corporate laptop with Windows 10. I had Terminal installed via one of the binaries from Github, but then after an OS update, it stopped working. By "stopped working", I mean that I couldn't launch Terminal at all, and there were no error messages when I tried to launch Terminal. Just nothing would happen at all when I tried to launch it.
When I tried to install the new 1.17 binary, I get the error shown below. I get the same thing when I try to reinstall 1.16.
Steps to reproduce:
- Download the msixbundle file for 1.17.
- Attempt to install Terminal via msixbundle.
- Hit the "Run" button in Microsoft Store after installation.
### Expected Behavior
Terminal launches.
### Actual Behavior

Contributor guide
Research direction
Start by reproducing the MSIXBundle installation and launch steps on the reported Windows 10 build, then inspect the package identity error shown in the attached image. Done means identifying why the installed Terminal package cannot launch after installation and confirming that Terminal launches successfully through the reported steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100