This works fine on my remaining Windows 7 computers, but fails in Windows 10 and Server 2019. Is there a security setting I can change that will fix it?
1. Make sure c:\scripts is in PATH 2. Create a vbs script "arch.vbs" and put it in c:\scripts. 3. Also create a batch file called "archivethis.bat" in c:\scripts. 4. Click the Classic Start button and in the Search box, type "arch".
In Windows 7, the arch.vbs shows up and pressing Enter runs it.
In Windows 10 and 2019, the archivethis.bat shows up and pressing Enter runs that instead.
I know a workaround is to put a shortcut in the Start menu. Then it works fine. But I am trying to use my arch.vbs script on dozens of computers and virtual machines. I don't want to put a shortcut to it in the Start menus.
I understand that vbs is dangerous. So I tried making a .lnk pointing to the .vbs - no luck there either.
I created a file called 'arch.bat' containing "arch.vbs %*" and so far it works, though it pops up an annoying cmd window first. I assume I could work around that by changing arch.lnk to point to arch.bat and start minimized.
Is there a way to tell the Search box to trust a vbs lnk like it does on my Windows 7s?
Thank you!
|