Windows 10: Can't run command in PowerShell but OK in Cmd

The screen shots show results of running Code: "C:\Program Files\AVAST Software\Avast\ashCmd.exe" /@=Quick[/quote] in both PS and Cmd. The problem is I have made a task in Task Scheduler to run this command daily and, apparently, Task Scheduler insists on using PS. This has worked for a couple of years but after recent updates has stopped.

How can I force Task Scheduler to use Cmd? Or how can I fix PS to recognize /@?

:)

 

problems and suggestion

There is a DOS command you can use to run as administrator in command line, follow provided steps by Leo Huang on this

thread.

Let us know how it goes.

 

problems and suggestion

1.i don't know

2.the problem is not in windows store apps

3.i want to be gaming in safe mode but i can't there is no sound and i don't try that yet

4.also when type cmd in search and click on run as administrator the file explorer restarts and also when clicking on windows PowerShell and windows PowerShell administrator

5.i can't enter cmd as administrator but i can enter to cmd and PowerShell as admin and is there any command to change to admin in cmd

 

Hi, this may help:
Running CMD command in Powershell - Stack Overflow
Run a Dos command in Powershell

 

PowerShell interprets the "C:\Program Files\AVAST Software\Avast\ashCmd.exe" part as a string. You have to use the call operator "&" to tell it to treat it as a command.

Code: &"C:\Program Files\AVAST Software\Avast\ashCmd.exe" /@=Quick[/quote]

 

I tried the suggested command and it does work manually in Power Shell. But Task Scheduler chokes on it.





If i say "Yes" it breaks up the command string to "%C:\program" with the rest of the command as an argument.

 

This is looking increasingly like an "escape character" issue where multiple levels of escapement are coming into play (one level inside PowerShell, another inside Task Scheduler). I'd suggest zooming over to the forums at PowerShell.org where the real PS wizards congregate and deal with stuff like this regularly. I bet if you ask them, you'll get a straight answer pronto (and may even find it covered there already).
HTH,
--Ed--

 

Try this PowerShell.exe &"C:\Program Files\AVAST Software\Avast\ashCmd.exe" /@=Quick at the Task Scheduler.

 

Might as well just run cmd.exe with /c "C:\Program Files\AVAST Software\Avast\ashCmd.exe" /@=Quick as the arguments then then.

 

OP said for some reason command-line does not work why i have no idea.

 

Hi, create a bat file containing
cmd.exe /c "C:\Program Files\AVAST Software\Avast\ashCmd.exe" /@=Quick

and schedule the bat file.I don't have ashCmd.exe but
cmd.exe /c "D:\Utilities\Sysinternals Suite\psinfo" /?
in a bat file works from the task scheduler.

 

dalchina, your idea is brilliant and simple. The batch file works fine when run from the desktop. But, alas, does not run from the task scheduler. It says "Running" but nothing happens. Task scheduler shows in Task Manager while it's running.

... Edited out the /@=Quick part and still won't run. So maybe it has something to do with the ashCmd.exe program or with Avast.

 

Try --%

That tells Powershell not to try to parse the rest of the line but just pass it as is.

So Code: "C:\Program Files\AVAST Software\Avast\ashCmd.exe" --% /@=Quick[/quote]

 

Good to know, lxo7. I'll try it. But right now I've avoided the problem by downloading System Scheduler Splinterware which ran the command perfectly, using "c:\program files\avast software\avast\ashcmd.exe" as the application and /@=Quick as the parameter. It used cmd automatically.

 

Strange. You could convince yourself the bat file is executed by picking something without a parameter that can be run from a command line- even just
DIR C:
Pause

say.

Just wondering if there's a difference in running as admin or a standard user for ashCmd?
I have Avast free, but not that for whatever reason.