After Windows11 24H2, there are many compatibility issues with JScript engine as reported in other threads.

There is a known workaround in the registry (per system or per user) using the JScriptReplacement=0.

But, is there a per-application workaround without messing the registry, that is not always acceptable?

Can an application opt-in to use the old engine explicitly?