Skip to content

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

@FredThompsonII

Description

@FredThompsonII

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions