Windows pops up dialog asking how to run VBS scripts on some PCs

I have a mixture of Windows to 1809 and 21H2 PCs. Upgrading all to 21H2.
I have created a scheduled task which runs a script called connect.vbs, which contains the following;

Code:

Dim WinScriptHost
Set WinScriptHost = CreateObject("WScript.Shell")
WinScriptHost.Run "C:\Tools\login.cmd", 0
Set WinScriptHost = Nothing

Which runs the login script. The sole purpose of the vbs script is to hide to dos box that otherwise shows if calling the login script directly.

On some PCs at boot up Windows will ask how I want to open the vbs file. I select the script processor and it runs the script. But instead of remembering that, it asks me on every start up. To make matters worse, it doesn't do it on all PCs. Some 1809, some 21H2... I can't find any common denominator.

.VBS is present on the pathext envrionment variable.
assoc .vbs shows;

Code:

C:\Users\Tanya>assoc .vbs
.vbs=VBSFile

How vbs files are executed seems correct too..

Code:

C:\Users\Tanya>ftype | find /I "VBS"
VBSFile="%SystemRoot%\System32\WScript.exe" "%1" %*

wscript.exe exists in %systemroot%\system32

Any ideas? Thanks

Scheduled tasks don't take into account file type associations, it's not the Explorer shell.

You need to explicitly call WScript.exe script.vbs as the run command. This is true for PowerShell scripts (powershell -f script.ps1) and batch (cmd /c batch.cmd).

garlin said:

Scheduled tasks don't take into account file type associations, it's not the Explorer shell.

You need to explicitly call WScript.exe script.vbs as the run command. This is true for PowerShell scripts (powershell -f script.ps1) and batch (cmd /c batch.cmd).

Thanks for that I'll give it try. Will let you know how it goes.

Do you have any ideas on why this error is occuring on some but not all PCs when they are all calling the script the same way?

File type associations (FTA's) changed a bit in later Windows versions, due to security concerns (to prevent bad actors from secretly replacing programs). If you've upgraded older machines, it may be a little late to compare the before & after settings.

But invoking wscript.exe from Scheduled Tasks, makes it works across all Windows platforms.

garlin said:

File type associations (FTA's) changed a bit in later Windows versions, due to security concerns (to prevent bad actors from secretly replacing programs). If you've upgraded older machines, it may be a little late to compare the before & after settings.

But invoking wscript.exe from Scheduled Tasks, makes it works across all Windows platforms.

I haven't upgraded all of them. I have some 1809 that work, some that dont and also some 21H2 that work and some that dont. Anyway,