Retrospective effect in a batch file - in x32Win10ProV22H2

By using a batchfile, I'm trying to automate capturing a view of the desktop (for storage).
The following code produces the right image, but leaves the TaskBar permanently unhid.

Start "" "C:\Program Files\ToggleTaskbarAutohide\ToggleTaskbarAutohide.exe"
timeout 1
Start "" "C:\Program Files\Macro Express Pro 6\MeProc.exe" /ASaveDeskTopView
REM timeout 1
REM Start "" "C:\Program Files\ToggleTaskbarAutohide\ToggleTaskbarAutohide.exe"


The following prevents the first line from being effective.

Start "" "C:\Program Files\ToggleTaskbarAutohide\ToggleTaskbarAutohide.exe"
timeout 1
Start "" "C:\Program Files\Macro Express Pro 6\MeProc.exe" /ASaveDeskTopView
timeout 1
Start "" "C:\Program Files\ToggleTaskbarAutohide\ToggleTaskbarAutohide.exe"

I find it very peculiar that a late step can influence an earlier step.
Can anyone explain - or better still, REMEDY, this anomaly ?

I have stated the wrong title - the problem is different.

If the batch file has

Start "" "C:\Program Files\ToggleTaskbarAutohide\ToggleTaskbarAutohide.exe"
timeout 1
Start "" "C:\Program Files\Macro Express Pro 6\MeProc.exe" /ASaveDeskTopView
timeout 2
Start "" "C:\Program Files\ToggleTaskbarAutohide\ToggleTaskbarAutohide.exe"

The first line is NOT cancelled, but a CMD screen for the last step gets superimposed over the image.

So the problem is one of timing : how to prevent the CMD screen for the last step from being caught in the snip.

Edited by Bastie, 16 April 2024 - 02:11 AM.

Try adding a /wait to your lines that use the start command.

e.g., 

start "" /wait "C:\My\Command\here.exe"

Edited by pseymour, 17 April 2024 - 07:21 AM.

It seems to me '/wait' should not be added to all the lines, but to the third command. However that does not fix things.

Nor does adding it to all three.