I asked if using createobject("WScript.shell) would be affected by the vbscript depreciation. This is the response according to Microsoft Copilot....
"If you're using KiXtart or PowerShell to call COM objects, you're fine—until Microsoft decides to deprecate those COM interfaces too (which they haven’t announced yet"
what does safe for now mean?
“Safe for now” means that your current usage of CreateObject("WScript.Shell") in KiXtart or PowerShell is not directly impacted by VBScript’s deprecation—but it’s living on borrowed time.
Here's the nuance:
VBScript deprecation targets the vbscript.dll engine, which interprets .vbs files and embedded VBScript in HTAs and legacy apps2.
WScript.Shell is a COM object, not VBScript itself. You can still instantiate it from:
KiXtart
PowerShell
JScript
VB.NET
Even compiled C++ or C# via COM
So yes, CreateObject("WScript.Shell") is technically safe—but only outside of VBScript.
⚠️ What “safe for now” really means:
If you're using VBScript as the host language, like .vbs files or HTAs with <script language="VBScript">, those will eventually break.
If you're using KiXtart or PowerShell to call COM objects, you're fine—until Microsoft decides to deprecate those COM interfaces too (which they haven’t announced yet).
