JScript issues with Win11 24H2: per-application "JScriptReplacement"?

Davide Capodaglio 5 Reputation points
2025-02-03T11:04:28.85+00:00

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?

Thanks

Microsoft 365 and Office | Development | Office JavaScript API
Windows for business | Windows Client for IT Pros | User experience | Other
{count} vote

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.