how to prevent .batch file focus steal executed from a taskschedular

I have the codes below

taskkill /F /T /IM AAA.exe
start /MIN "" "C:\Users\Administrator\AAA.exe" :0
ping 127.0.0.1 -n 5 > nul
taskkill /F /T /IM CCC.exe
start /MIN "" "C:\Program Files (x86)\CCC.exe" :0
exit

setup with task scheduler to run this every hour, but the focus steal from CMD window is too much. how can this be written to prevent it?

Bree said:

Try this....

How to prevent command window from appearing on scheduled tasks on Windows 10 - Pureinfotech

doing this only execute the taskkill part but not the start program part. not sure why.

Try3 said:

To run something without it stealing focus requires use of VBS.
So it is not a question of modifying what you have now but using VBS to do the job or, at least, using VBS to start it.

I assume you mean that you are running those commands in a batch file from Task scheduler.
I assume you mean that the command window is stealing the focus rather than something is stealing focus from it.

I do not know why you are using the Built-in Admin account.
I do not know why you are putting executable files in any user account folder.

This approach should achieve what you want
Make Task scheduler run a batch file minimised and with a specific icon - TenForums
Despite its title, it also covers the option to run the batch file hidden.
In both cases, hidden & minimised, the batch file will run without stealing focus.

Denis

reason killing task and restarting is because it'll lockup and im tired of restarting them manually. when the application locks up it requires me entering into task manager, kill the task then manually fire it up again.

built in admin account is because using server window 2016 which is basically same as windows10, defaults to administrator and i'll be the only one using it, kind of like a test matchine.

i'll give the VBS thing a try, thanks

m18xr2 said:

built in admin account is because using server window 2016 which is basically same as windows10, defaults to administrator and i'll be the only one using it, kind of like a test matchine.

No. The built-in admin account exists mainly because you can use it to still get in after your other user account(s) get(s) corrupted somehow. Using the built-in admin account as a typical replacement for a separate admin account was not, is not, will not be recommended in any way─even if you can.

Try3 said:

I do not know why you are putting executable files in any user account folder.

Even M$ puts executables in %LocalAppData%\Programs. %LocalAppData% points to %UserProfile%\AppData\Local.

Under Step 6 in that tutorial, if the batchfile needs to run with admin rights, then be sure to also check the "Run with highest privileges" (checkbox at the bottom). In the new Action where you choose "Start a program", put %windir%\System32\wscript.exe under "Program/script:", and, next to "Add parameters (optional):", put the full filepath of the .vbs file enclosed in doublequotes. The .vbs file that runs the batchfile invisibly and doesn't steal the focus can be written like this:
CreateObject("WScript.Shell").Run """%windir%\System32\cmd.exe"" /c start """" ""filepath""", 0
Substitute filepath in the above with the full filepath of the batchfile.