Can I Open Msconfig Tools Using CMD And Run One Of It's Tools Via CMD

[Zakaria Oussete]

I need to open msconfig>tools>Command Prompt only by using cmd commands in other words using batch script in order to bypass UAC is this even possible to do i'm looking for more info !

 

[Brink]

Hello Zakaria, and welcome to Seven Forums.

If it may help, you could use the method in the tutorial below to create an elevated shortcut to run this elevated without getting a UAC prompt.

Elevated Program Shortcut without UAC Prompt - Create

 

[Zakaria Oussete]

Hi @Brink I appreciate your quick answer i'm familliar with using Task Scheduler but i really need to be able of doing that through cmd i came up with this command which opens Msconfig in Tools tab the command is "msconfig -5" now i want to execute one of it's modules using the command prompt if possible thx again !

 

[wither 2]

Why not run a Command Prompt as the administrator and input your command. Shouldn't be any UAC issues when you launch which tool you want.

 

[Zakaria Oussete]

Well wither 2 there is a special obstacle preventing me from doing that since i want to use it in a batch file which required cmd commands thanks for you approach tho !

 

[file3456]

I don't even see MSCONFIG. Windows commands | Microsoft Docs

What exactly are you needing to do via a batch file?

 

[torchwood]

Hi

I've actually got Admin Command mode pinned to my taskbar, and multiple notepad items on my desktop, i just open command mode and drag the one i want in

 

[wither 2]

Seems that "notepad" items is something in addition to what you originally described that you wanted to do. I mean, the method I described works perfectly to launch the items within Tools. Maybe the issue is that you can send Command Prompt to the desktop but you need to right click on the shortcut and select run as administrator each time you use it. Maybe the properties of the shortcut need to be changed to give full control to the user.

- - - Updated - - -

torchwood- I wasn't paying attention and thought your last response was from the OP. Sorry about that.