Several customers are reporting scripting issues after the 24H2 update by Windows11.
It’s known the VBSCRIPT engine would have been provided as optional feature rather than core engine (see official article by Microsoft) , and the evidences show us it has started from such W11 update.
In our tests, adding and removing the optional feature produces a coherent behavior:
- when the VBSCRIPT feature is enabled, Mechworks’ scripts work;
- when the feature is not installed, the .VBS extension is not recognized at all by the OS:
Then, if MechworksPDM scripting is not working anymore after the W11 update, reinstalling the PDM has solved in most of cases.
Last, switching to x64 scripting (see ‘.x64 statement in the Help) helped in some cases.
Posted in: Scripting/API/DBWForms, Operating System