MicrosoftHi. About VBScript (cscript.exe) deprecation, I have scripts to create desktop shortcuts using WScript.Shell:
Set oWS = WScript.CreateObject("WScript.Shell")
sLinkFile = "%USERPROFILE%\Desktop\Publico.lnk"
Set oLink = oWS.CreateShortcut(sLinkFile)
oLink.TargetPath = "P:"
oLink.Save
How can I create the same script using PowerShell without cscript.exe? From what I've seen, the option for PowerShell is to use WScript.Shell, doesn't this mean that PowerShell still uses cscript.exe?
$ShortcutPath = "$env:USERPROFILE\Desktop\MyShortcut.lnk"
$TargetPath = "C:\Path\To\Your\Target.exe"
$WshShell = New-Object -ComObject WScript.Shell
$Shortcut = $WshShell.CreateShortcut($ShortcutPath)
$Shortcut.TargetPath = $TargetPath
$Shortcut.Save()
Thanks in advance.
Regards.
Instead of re-writing your desktop shortcut script in PowerShell, consider re-writing it in JScript. Save the code below as "a.js", then execute from the Command Prompt with "cscript.exe a.js".
var oWS = WScript.CreateObject("WScript.Shell");
var sDesktop = oWS.SpecialFolders("Desktop");
var sLinkFile = sDesktop + "\\Publico.lnk";
var oLink = oWS.CreateShortcut(sLinkFile);
oLink.TargetPath="P:";
oLink.Save();
Hi Ken, thanks for your reply.
That's the message in Event Viewer:
VBScriptDeprecationAlert
ID 4096
VBScript is scheduled for deprecation. Our telemetry indicates that your system is currently utilizing VBScript.
We strongly recommend identifying and migrating away from any VBScript dependencies at the earliest.
The following process has been detected as using VBScript. The associated process tree and call stack are provided below to assist in identifying the scenario in which VBScript was invoked.
ProcessName = "cscript.exe"
ProcessTree = "cscript.exe;cmd.exe;userinit.exe;winlogon.exe"
CallStack = "vbscript.dll+0x68C16;vbscript.dll+0x5571F;vbscript.dll+0x40348;cscript.exe+0x114C;cscript.exe+0x1835;cscript.exe+0x4970;cscript.exe+0x40CF;cscript.exe+0x3A74;cscript.exe+0xD648;KERNEL32.DLL+0x2E8D7;ntdll.dll+0x8C48C"
ProcessTreeEnhanced = "cscript.exe("cscript /nologo
The matter is that vbs and js uses cscript.exe (marked for deprecation), and the suggestion is to move to PowerShell, and what I've found is that even PowerShell uses WScript.Shell, so if PowerShell calls to cscript.exe under the hood, what's the solution?
Regards.
Y O,
Interesting. I am running Windows 11 25H2 and the 6-line JScript file I posted worked as expected. I don't see any 4096 events. In exactly which log did you see the event? (FYI, I don't have an "Event Viewer → Applications and Services Logs → Microsoft → Windows → Windows Script Host" entry on my system which an internet search tells me where these events might be logged.)
Hi, Ken.
The event appears in Windows 11 Pro 25H2.
So far what I've found is that the COM object WScript.Shell in PowerShell has nothing in common with cscript.exe, so I'll build a new script in PowerShell.
The recommendation is to migrate your vbs scripts to PowerShell or JavaScript; I choose PowerShell. Source: https://techcommunity.microsoft.com/blog/windows-itpro-blog/vbscript-deprecation-timelines-and-next-steps/4148301
Regards.