-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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.
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
Cannot start after updating to 1.16 - likely due to elevate:true
#14729
Comments
I have yet to debug what is going on, but on my machine something similar started happening as soon as I got the update to 1.16, except that after 10 minutes or more the window suddenly appears. I can see the process is running the whole time in Task Manager. Hitting "Save" in the settings also triggers a 10+ minute hang. |
quick sanity check: are you using
This seems like a different issue. Actually, @Robo210 your whole post sounds like a different issue - mind filing a new thread? I just want to make sure we track all these regressions to their individual root causes, and not conflate them. |
I'm also encountering this problem - as soon as I installed 1.16.10232.0 (Windows 11) attempts to launch Terminal failed in the way described.
I am using 'elevate:true' here - and editing my settings.json to remove that results in me being able to launch Terminal again. But unfortunately without Administrator privilege, which isn't great. As soon as I re-enable "Run this process as Administrator" again, save, and re-launch - well.. it doesn't launch again. Dean |
I think the above reply is correct. It starts when I change "elevate": true to "elevate": false. When I go back to "elevate": true, it doesn't start. At present, you can only manually find settings.json file to modify it. |
Okay well that's some sane confirmation, even if it's mysterious and confusing. For the record, if you really need I still don't understand how this regressed in 1.16 in the first place... The list of https://github.com/microsoft/terminal/commits/release-1.16 I guess the original issue repro'd in I TAKE THAT BACK, #14520 is in 1.16 release. That's sus for sure. It might be valuable to know what Windows builds folks are on. I suspect this only impacts Windows 11 users. Knowing the exact build numbers might help us ID if it's an OS regression, or something due to the win10/win11 package split |
elevate:true
Sure, I'm seeing this on Windows 11 21H2 (22000.1455). I can also confirm that I'm not seeing any (obvious) problems with elevation using the latest 1.17 preview build. Dean |
I noticed that the program has been updated to version 1.16.10262.0. The log shows that the problem is fixed, and the program can run normally after my test. I think it's time to close this issue. What do you think? |
Ah, you're totally right. Thanks! |
Windows Terminal version
1.16.10232.0
Windows build number
windows 11 OS: 25281.1000
Other Software
No response
Steps to reproduce
Double clicking on the icon does nothing. Nothing is displayed.
Expected Behavior
No response
Actual Behavior
Couldn't launch today after Microsoft Store updated with the latest version. Double clicking on the icon does nothing. Nothing is displayed.
The text was updated successfully, but these errors were encountered: