Yes ladies and gentlemen - that is correct
And I finally have an apparently good enough and relatively easy
to utilize as part of my C:\Users\YOUR-USER-NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
I took the -ExecutionPolicy Bypass -File part from the Task I was exploring previously and I added it to a LNK file. So now in the folder Startup I have a shortcut leading to that PS1 file with code
Start-Process Mp3tag -ArgumentList '"M:\My Playlist.m3u8"'
$wshell = New-Object -ComObject wscript.shell;
$wshell.AppActivate('*Mp3Tag')
SLEEP 0
$wshell.SendKeys('(%(" "(n)))')
with the parameters of that LNK file set to
Target: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File "C:\Various Scripts\X.ps1"
Start in: "C:\Various Scripts"
Run: Normal window
And it works; in that after entering Windows Mp3tag will be executed by X.ps1 file [which was a problem - to automatically execute PS1 file and not just open it for editing] with the particular playlist will being loaded to Mp3tag. Although the window of Mp3tag will be open maximized, it will be somehow opened under [behind] the window of FreeCommander, which is set to open also in a maximized form and also by the means of having in folder Start a LNK file leading to its EXE
And I said somehow, because there is no logic here. The C:\Users\YOUR-USER-NAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup apparently works by alphabetical order- whatever is at the top will be loaded [executed] first. So FreeCommander XE.lnk is executed first and only after it an another process happens- of the X.lnk. So Mp3tag should be placed on top of FreeCommander window - but it is not. And yes I have made an experiment- by renaming X.lnk to ! X.lnk I made this file appear above FreeCommander XE.lnk in the folder Start- and thus made it to be executed as the first item from Start. And the result was that Mp3tag was opened with focus [at the front] - and this is the exact opposite of what should be happening [because FreeCommander window should be placed over it]
But what is more, when I went back to re-naming it as X.lnk but also changed its parameter Run: from Normal window to Minimized it also started running in front of FreeCommander window. So once again ladies and gentlemen the minimized parameter from "Start" folder was ignored - apparently on the account of being evoked from Startt folder; plus it broke the workaround
All in all, this method with LNK file is also better than TaskSchduler approach because it does not create a brief appearance of the Mp3tag window - it stays hidden behind FreeCommander [while the TaskScheduler method made a quick flash of Mp3tag window]
So for now this seems to be the solution
But first it is applicable only in peculiar circumstances [of having some third party software auto-running concurrently which happens to be able to hide Mp3tag window]. And secondly I simply do not like the idea to be forced to
And so, if someone has other solutions / ideas - please post them here, even in a distant future