vbs file assotiation via gpo preference, Win10


  • Hello.

    I'm trying to prevent users from changing .vbs file assoctiation.

    Via group policy preference (user settings) i set the default .vbs file handler.

    Everythink worked fine(well, almost) on Windows 7 workstations, but on windows 10 i had - "There is no script engine for file extension ".vbs"."

    After a deep digging i'v found that problem is in HKEY_CLASSES_ROOT\.vbs\(Default) registry key. Someow,on windows 10, gpo put "vbs_auto_file" value over there, instead of "VBSFile". If i change it to "VBSFile" manually, everythink works fine againt.


    Why gpo do this?

    How can i report this bug to microsoft?

    Thursday, July 28, 2016 7:56 AM