Future compatibility of ScriptCryptor with Windows 11 (24H2 / 25H2 and beyond)

[steph78630]

Hello,

I’m currently using ScriptCryptor to compile my VBScript code into standalone EXE files. I read on your website that ScriptCryptor includes its own runtime and does not depend on wscript.exe or cscript.exe, which is great.

However, I’d like to clarify a few critical points regarding long-term compatibility with future versions of Windows :

Since Microsoft announced that VBScript.dll will be completely removed starting with Windows 11 version 25H2, can you confirm that ScriptCryptor-compiled executables will still run without issues (because they don’t rely on the system’s VBScript engine) ?

Does ScriptCryptor rely on any other Windows components that might be deprecated or removed in the future (e.g. WMIC has already been retired, but WMI remains) ?

If my scripts use COM objects such as WScript.Shell, Scripting.Dictionary, or WMI via GetObject("winmgmts:..."), am I correct in assuming these calls still depend on Windows system components, and therefore the only risk of incompatibility would come from Microsoft itself removing or modifying those COM/WMI services ?

Is there any official roadmap or guarantee of continued compatibility of ScriptCryptor executables with Windows 11 24H2 / 25H2 and beyond ?

I just want to make sure that the applications I distribute today will remain functional in the next major releases of Windows, without having to migrate everything to PowerShell.

Thanks in advance for your clarification !

Best regards,
Stephane