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

Doesn't work in Windows batch files - is my call correct? #6

Open
FredThompsonII opened this issue Jan 20, 2023 · 0 comments
Open

Doesn't work in Windows batch files - is my call correct? #6

FredThompsonII opened this issue Jan 20, 2023 · 0 comments

Comments

@FredThompsonII
Copy link

Before Windows 10, this would work properly in a batch file:

forfiles /s /m "*.lnk" /c "cmd /c call @file"

Each lnk points to a batch file. Those batch files now need to run with elevated permission so I tried this:

forfiles /s /m "*.lnk" /c "MinSudo --NoLogo --TrustedInstaller --Privileged --Verbose cmd /c call @path"

That also doesn't work.

Is there a way to use MinSudo such that elevated permission is inherited? If not, is there a way to, somehow, decode the point aspect of a lnk in the batch file line so MinSudo will launch the target of the lnk?

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

1 participant