Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New install unable to Launch via Start Menu #9062

Closed
sbingner opened this issue Feb 6, 2021 · 3 comments
Closed

New install unable to Launch via Start Menu #9062

sbingner opened this issue Feb 6, 2021 · 3 comments
Labels
Culprit-Centennial Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely.

Comments

@sbingner
Copy link

sbingner commented Feb 6, 2021 •
edited
Loading

Environment

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Steps to reproduce

I just installed the latest release file Microsoft.WindowsTerminal_1.5.10271.0_8wekyb3d8bbwe.msixbundle and installed it. When I try to launch after install or launch from the start menu it gives me an error

Expected behavior

Windows Terminal Opens

Actual behavior

Windows gives an error saying it can't access the path. I can browse to the path (After taking owndership of C:\Program Files\WindowsApps) and open it with no problems. Screenshot
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 6, 2021
@sbingner
Copy link
Author

sbingner commented Feb 6, 2021

So this just magically started working when I left everything alone for about 30 minutes...

@DHowett
Copy link
Member

DHowett commented Feb 6, 2021

The appx/msix deployment platform works in mysterious ways :| sorry about that

@zadjii-msft zadjii-msft added the Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely. label Feb 8, 2021
This was referenced Feb 16, 2021
Closed
Closed
@DHowett
Copy link
Member

DHowett commented Mar 11, 2021

Collecting all these issues in #9452

@DHowett DHowett closed this as completed Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Culprit-Centennial Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DHowett @sbingner @zadjii-msft