Microsoft has outlined a comprehensive plan for the upcoming removal of the VBScript language from Windows. This move, driven by security concerns and the availability of more robust alternatives, marks the end of an era for a scripting language that has been part of Windows since 1996.
VBScript was included by default in every desktop version of Microsoft Windows since Windows 98, in Windows Server starting with the Windows NT 4.0 Option Pack, and with Windows CE.
VBScript was introduced in 1996 and quickly became a tool for IT administrators to automate tasks. Over the years, it received updates that added functionalities such as regular expressions, command line arguments, and classes. Despite its utility, the scripting language has become outdated, and its vulnerabilities have made it a liability in modern computing.
The environments for running VBScript are Windows Script Host (WSH), Internet Explorer (IE), and Internet Information Services (IIS). Additionally, it can be embedded in other programs through the Microsoft Script Control.
Initial Phase: Windows 11 24H2 Update
The first step in the phased approach will begin with the Windows 11 24H2 update. In this update, VBScript will be relegated to a feature on demand (FOD). Although these FODs, including VBScript, will come preinstalled and enabled by default, Microsoft emphasizes that this is a temporary measure to ensure users have time to transition their applications and processes to other languages.
Microsoft's decision to phase out VBScript is largely motivated by security concerns. Over the years, VBScript has been a frequent target for malware attacks. The company is encouraging IT administrators and web developers to migrate to more secure and modern alternatives such as PowerShell and JavaScript. These languages offer better security features and are more aligned with current technological standards.
Second Phase: Changes in 2027
In 2027, Microsoft will move to the second phase of VBScript's deprecation. During this period, VBScript will no longer be enabled by default in that year's version of Windows. Developers who still rely on VBScript will have the option to manually enable it as a feature on demand. Although an exact date in 2027 has not been specified, Microsoft assures that ample notice will be given to developers to facilitate a smooth transition.
Final Phase: Complete Removal Beyond 2027
The final phase of the deprecation plan will see the complete removal of VBScript from a future version of Windows. This will involve eliminating all VBScript-related dynamic link libraries (.dll files), rendering any projects dependent on VBScript non-functional. Microsoft has not specified the exact year for this final phase but is providing developers with considerable lead time to migrate their applications to other supported languages.
To assist in this transition, Microsoft is offering several resources and recommendations for those who still use VBScript in Visual Basic for Applications (VBA) and web projects. The company aims to minimize disruption and ensure that developers have the necessary tools and information to update their applications effectively.
