-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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 Terminal/new tab as admin #15576
Comments
Same issue happened after updating. |
Older version works. |
@WiLuX-Source Which version works for you so I can roll back? |
@xenobytezero I rolled back to the latest version where they seperately give win10 and win11 release i dont remember the number rn but it was released at this year Jan 27 |
/feedback |
Hi there! |
I modified my windows install heavily so i dont have that one hopefully author can record it. |
Though, I tried every version and found out only releases that are not seperated by win11 and win10 is effected. (At least for me.) |
Having the exact same issue here on Windows 10. I've submitted feedback via Feedback Hub. Unfortunately, there was no option to share the link. Terminal version 1.17.11461.0 |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
1 similar comment
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
This comment was marked as spam.
This comment was marked as spam.
I have the same issue, but new tab is just not opened as Admin. |
Same here, 1.17.11461.0 |
This issue is not the only one about While some of them are due to issues in Windows Terminal itself, even more unfortunately turned out to be something out of our control. In particular, your event log entry looks exactly like #15526. In particular: #15526 (comment) Can you run this in an elevated shell?
If you don't get the expected output of
|
Not necessarily "exactly," as I have one fewer If you see anything other than |
Sorry for the delay. @zadjii-msft - The issue is appearing on a work machine that appears to have locked out Feedback Hub, so I can't submit this. @lhecker - I've got the exact correct response you mentioned. |
Can you try following the steps in "Capture automatically" to get an automatic crash dump/? If that works, then you should be able to automatically get a |
Managed to get a crash dump, find attached. |
Is it safe to update now any news? |
notes from dump
watson was useless. BUT that stack looks really similar to #15745. Though, this one's from the Store, so it's not running unpackaged. In this one,
but all of that seems.... normal. I need to reach out to someone to check out how to get at the stowed exception. |
I'm just gonna start aggregating all these into /dup #15583 |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Windows Terminal version
1.18.1462.0 (also tested with non-Preview release)
Windows build number
Microsoft Windows [Version 10.0.19042.508]
Other Software
No response
Steps to reproduce
Expected Behavior
A new Command Prompt tab opens as Admin
Actual Behavior
The cursor turns to a spinner for a second, then nothing. No new tab appears.
Windows Event Log has the following
Standard CMD opens fine as Admin.
The text was updated successfully, but these errors were encountered: