InDesign 19.0.1 - VBS scripts have stopped working

[Piotr_W]

As in the topic, VBS scripts have ceased to work in version 19.0.1

[Eugene Tyson]

Can you be more specific?
What's your OS?

What's your system specs? 

All VBS scripts? 

All documents? 

Specific documents?

VBS scripts were reported to be fixed for 19.0 

@Robert at ID-Tasker  maybe you can shed light on this?

[Robert at ID-Tasker]

Thanks @Eugene Tyson, unfortunately, I've not upgraded yet to v19 on my laptop - don't want to mess with my production machine - too buggy ...

But like you've mentioned, we still need more information.

It just might be a case of script trying to connect to a specific version of the InDesign - instead of to the last installed / current.  

[Piotr_W]

Windows 10.

Yes, all VBS scripts, even the default ones, installed with the InDesign.

Yes, all documents.

After running any script, nothing happens, not even any prompt.

On the second computer, the second graphic designer has the same situation.

Windows and InDesign are in Polish language versions.

[Robert at ID-Tasker]

Windows 10 - InDesign 19.0.1 - everything is working perfectly fine.

Have you tried trashing preferences ? CTRL+SHIFT+ALT when starting InDesign.

If it doesn't help - try unistalling and re-installing - or even using CC Cleaner ?

[Piotr_W]

Thank you, I'll try it, but only next week

[Piotr_W]

Thank you very much @Robert at ID-Tasker.

Restoring all preferences and default settings solved the problem.

[Dirk Becker]

Likely the reason is that 19.0 had reused the guid of 18.5, causing e.g. trouble with third party plug-in installers. This was fixed with 19.0.1 by giving 19.0.1 a new guid.

Now either your registry is pointing in the wrong direction (uninstall, reinstall, eventually as admin), or the vbs still goes thru the 19.0 tlb. In that case you need to rebuild the tlb with the changed guid. Moving the tlb out of its location should trigger that in theory, haven't tried it myself.

[Robert at ID-Tasker]

I think registering TLB file is only needed when running external scripts - VB6 code compiled as EXE? Not when VBS script - plain text - is run from inside - Scripts Pallet?