Microsoft announces VBScript deprecation 2024: Here are the important end of support timelines and next steps

Microsoft has announced the deprecation of Visual Basic Script (VBScript). This decision, detailed in a recent blog post on the Windows IT Pro Blog, outlines a phased approach to retiring VBScript in favor of more advanced scripting languages like PowerShell. The deprecation process is set to begin later this year and will be completed over several phases, with full retirement expected by 2027.

VBScript background

VBScript, once a popular scripting language for automating tasks in Windows environments, has seen a decline in usage with the advent of more modern web technologies. Microsoft’s decision to phase out VBScript is driven by the need to reduce complexity and enhance security. By transitioning to PowerShell, Microsoft aims to provide a more efficient and secure scripting experience for its users.

VBScript Deprecation timeline

The deprecation of VBScript will occur in three distinct phases:

1. Phase 1: Initial availability as Features on Demand (FODs)
   Starting with the new OS release slated for later this year, VBScript will be available as Features on Demand (FODs) in Windows 11, version 24H2 and onwards. This ensures that users who still rely on VBScript can continue to use it while they migrate their dependencies to other scripting languages. VBScript FODs will be pre-installed by default, minimizing disruption for users during the transition period. Users can find VBScript FODs enabled by default under Start > Settings > System > Optional features.
2. Phase 2: Gradual removal from future OS releases
   In subsequent OS releases, it will be gradually removed. Microsoft will provide ample notice and support to help users migrate their scripts and applications to PowerShell or other modern scripting languages. During this phase, Microsoft will offer resources and best practices to assist users in the migration process. The company encourages users to engage with the Windows Tech Community and follow updates on social media platforms like X (formerly known as Twitter).
3. Phase 3: Complete retirement
   By 2027, it will be fully retired from all Windows OS releases. At this point, the feature or capability will no longer work, and users will need to have fully transitioned to alternative scripting solutions. Microsoft emphasizes that removing deprecated components helps reduce complexity and enhances security, ensuring a more productive and efficient user experience.

Support and resources

To support users during this transition, Microsoft has committed to providing extensive resources and support. Users can access additional information and best practices related to functionality and deprecation through the Windows Tech Community. Microsoft also offers support through its Q&A platform, where users can seek assistance and share their experiences.

The deprecation marks a significant step in Microsoft’s ongoing efforts to modernize its scripting capabilities and enhance security. By transitioning to PowerShell, users can benefit from a more robust and efficient scripting environment. Microsoft’s phased approach ensures that users have ample time and support to migrate their dependencies, minimizing disruption and maintaining productivity.