The problem
Windows 11 24H2 breaks scripting in FinalBuilder and Automise. You will see a range of different errors depending on your scripts or the actions you use (some actions use jscript).
The cause
Windows 24h2 enables a policy by default that causes JScript.dll (the com dll) to load JScript9Legacy.dll rather than JScript9.dll
JScript9Legacy.dll is a replacement engine using Chakra - which is an odd choice since it seems abandoned since Edge moved to using chromium. The reason they did this was because of a security issue - which is understandable - but unforutnately it introduces a whole host of bugs they do not seem to interested in fixing (I guess it works for them).
This issue even affects some of Microsoft's own applications (like Visual Studio)
The work around
The workaround is to disable the policy
Run regedit.
navigate to (for all users) :
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Main
or (for the current user only)
HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Internet Explorer\Main
Note these keys did not exist on my machine, so I added them.
Right click the Main key and select New DWORD (32-bit) Value, name the new value JScriptReplacement and the value to 0.
Restart FinalBuilder (no need to reboot).
Obviously, this is not ideal - we have been looking to replace JScript for some time - unfortunately so far our efforts have not resulted in something that is 100% backwards compatible - so we still have some work to do in this area.