As a precaution several file extensions have been set to be associated with notepad. One of these is .VBS file types which causes an issue. When it is set to notepad VBS scripts will no longer run and give an error about "no scripting engine to use". Normally you can go into Control Panel\Programs\Default Programs\Set Associations and change the program but in this case the correct option was missing. We can use command-line to get around this. Open up an Admin command prompt and use:
assoc .vbs=VBSFile
This will fix the issue. Of course if a GPO was what set the extension to notepad when it refreshes it will reset it back to notepad so if you need to run another .vbs script at a later date you will need to change it again.