-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Bug with "Open windows from a previous session" and defaults profile run as admin #14932
Comments
Okay I don't think we have a dupe for this after all. It's different enough from:
Though, it's ultimately the same nexus as all them |
I have this as well on the exact same specifications. Expected behavior is that the old session starts (if "load previous session" is configured) 1:1 without any new windows or tabs UNLESS I exclusively tell it to do something else. :) |
I think I see the real issue in my case. I've installed Terminal from windows store to get auto updates and it has created an app shortcut (or it's not really a shortcut in a normal sense) that calls the terminal with the following: "c:\Program Files\WindowsApps\Microsoft.WindowsTerminal_(version)\windowsTerminal.exe" new-tab --profile [profile path] So t's exclusively asking to launch a new tab when it's opened... but I've never set it up to do that. I cannot change these parameters in any way.. it seems to be hard coded. I can only see this because it's trying to run as admin and I select "show details" on UAC prompt. I'm still not sure what type of shortcut / program this is (I'm not familiar with windows store peculiarities) but these seem to come when you install the terminal using the store. Can someone confirm or explain what's going on? |
@mtaalas Sorry, just seeing that comment after getting back from leave. That looks to me like you've got the Terminal set up to run your default profile elevated (as admin) by default. In that case, when you launch the Terminal unelevated, it needs to explicitly shell out to create another new instance of the Terminal as admin. When that happens, it explicitly passes Now, maybe there's an easy solution here - when the Terminal is getting launched elevated for the default profile, maybe we shouldn't pass those args? That'd cause the Terminal to start up, and either
Right now, because we are passing the |
Hello guys. Is there any ETA of fixing this bug? I have encountered this bug in 1.17 (#15738) and it still exists in 1.19. |
Windows Terminal version
1.16.10261.0
Windows build number
10.0.19045.2604
Other Software
No response
Steps to reproduce
Set "When Terminal Starts" to "open windows from a previous session"
Set Defaults to run this profile as administrator
Expected Behavior
When opening terminal from start menu it opens as administrator with saved tabs
Actual Behavior
Terminal opens with default profile and new window with previous tabs.
This happens even with saved tab being the startup default
The text was updated successfully, but these errors were encountered: