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.

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

Group or resource not in correct state error when launching Terminal Canary when running as Admin #18436

Closed
XenoPanther opened this issue Jan 16, 2025 · 1 comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@XenoPanther
Copy link

XenoPanther commented Jan 16, 2025

Windows Terminal version

1.23.10151

Windows build number

10.0.27768

Other Software

No response

Steps to reproduce

  1. Right click any folder and click Terminal Canary
  2. Click Yes when UAC is shown
  3. Terminal will open in the incorrect directory
  4. The following error will appear

Image

Expected Behavior

Terminal to open in the correct folder without any errors. This sometimes happens, but an additional Terminal window is launched that is in the incorrect directory

Actual Behavior

Terminal opens in the incorrect directory and the error will appear

@XenoPanther XenoPanther added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jan 16, 2025
@XenoPanther
Copy link
Author

Slightly weird fix, but the issue was with my settings.json.
I fixed the issue by removing the json, letting Terminal recreate it and then pasting the contents of my previous settings back

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

1 participant