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

Start command shell in Administrator mode (Ctrl Shift K) starts in wrong folder #365

Closed
ScottHollows opened this issue Dec 10, 2022 · 5 comments

Comments

@ScottHollows
Copy link

Issue) If you press CTRL SHIFT K the command shell opens in Administrator mode with the current working directory being C:\Windows\system32

Expected Behaviour the current working directory should be the current directory in file manager

This issue only occurs when opening the shell in Administrator mode (CTRL SHIFT K).
It does not occur when opening the shell in normal mode (CTRL K)

When fixing the issue, please test for the current drive being C: and also test another drive as well as C: is the default

Occurs in;

  • File Manager 10.1.4.0
  • File Manager 10.1.4.49
  • File Manager 10.2.0.0 - latest release

image

@schinagl
Copy link
Contributor

schinagl commented Dec 10, 2022

I came around this too, but I doubt this is a bug but more a feature:

The 'Start in' is explicitly ignored when elevation is performed so that malicious binaries can do less harm.

We could overcome this by appending /k cd /d <path> when issuing cmd.exe

@craigwims
Copy link
Contributor

Well, it is not by design, just a bug I never got around to fixing.

@schinagl
Copy link
Contributor

Then lets change it: #367

@schinagl
Copy link
Contributor

#367 has been merged. Can we close this now?

@ScottHollows
Copy link
Author

I logged the bug.

I am closing it now as resolved

Thank you to everyone who helped with this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants