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

Selecting "No" when running as admin produces error state #121

Closed
ismyrnow opened this Issue Apr 27, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@ismyrnow

ismyrnow commented Apr 27, 2015

Required information!
OS version: Win8.1 x64
ConEmu version: 140814 [64]

Bug description
If you try to start a console as Admin, then accidentally select "No", conemu gets into a strange state.

Steps to reproduction

  1. Open conEmu
  2. Right-click the tab and select "Restart as admin"
  3. Select "No" in the Windows prompt.
  4. A conemu error message shows up. Select "No" to keep console open.
  5. Right-click the tab and select "Restart as admin" again.
  6. Another conemu error message shows, allowing you to report a bug. See screenshot:

2015-04-27_1631

My expectation would be that selecting "No" in the Windows prompt would either close the tab automatically, or put me back in to the previous state (un-elevated prompt) and allow me to try restarting as admin again.

This is a super minor bug, since you shouldn't select "No" in the Windows prompt anyways. However, conemu opened my browser and got the issue started for me, so I figured I would submit it with details.

@Maximus5

This comment has been minimized.

@Maximus5 Maximus5 closed this Apr 27, 2015

@Maximus5 Maximus5 reopened this Apr 28, 2015

@ismyrnow

This comment has been minimized.

ismyrnow commented Apr 28, 2015

Issue still present in build 150420 [64].

2015-04-28_0856

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Feb 7, 2016

160207?

@ismyrnow

This comment has been minimized.

ismyrnow commented Feb 21, 2017

I'm no longer using a Windows environment, so I can't test if the issue has been resolved. Feel free to close this if you want, and thanks for the great piece of software.

@Maximus5 Maximus5 closed this Feb 21, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment