MC1075649 – M365 Change Digest

One-line summary

Admins should detect and migrate away from VBScript, as it is enabled by default on Windows 11 24H2 and will be disabled/removed in future deprecation phases.

Similar updates

Details

Body (from Message Center)

Start detecting Visual Basic Scripting Edition (VBScript) across your organization in preparation for the next deprecation phase. See how to use System Monitor (Sysmon), review VBScript dependencies, or scan for .vbs files and custom MSI packages. Once detected, you should proactively migrate away from VBScript. Now that VBScript is enabled by default on Windows 11, version 24H2 and later, you can also proactively disable it in preparation for the next deprecation phase.

When will this happen:

Currently, VBScript is in its first deprecation phase, available as features on demand (FODs) and enabled by default on Windows 11, version 24H2. It’s the best time to research and migrate to alternatives. Today’s blog article is available to help with this transition. In the future, VBScript FODs will be disabled by default and later removed from Windows.

How this will affect your organization:

If your organization relies on VBScript, you’ll need to identify and remediate it before the next deprecation phase. There are several ways to identify where and how vbscript.dll is still being used within your enterprise environment. The four strategies outlined in the new article are here to help you with this task.

What you need to do to prepare:

Choose one of the following strategies to detect VBScript across your organization:

Use Sysmon to monitor VBScript usage.
Review VBScript dependencies.
Scan for .vbs files across the system.
Scan custom MSI packages for embedded VBScript.

Once detected, proactively migrate away from VBScript and disable VBScript on Windows 11, version 24H2 and later. Read Additional information for details.

Additional information:

Find step-by-step instructions, tips, and considerations in VBScript deprecation: Detection strategies for Windows.
Refer back to VBScript deprecation: Timelines and next steps.
Learn more about Deprecation: What it means in the Windows lifecycle.

Raw JSON (for debugging)

Expand/collapse the full payload below.

Show/hide raw

{
  "snapshot_item": {
    "action_required_by": null,
    "ai_action_required_by": null,
    "ai_actions": [
      "Detect VBScript usage via Sysmon or file scans",
      "Review and remediate VBScript dependencies",
      "Migrate scripts to alternatives",
      "Disable VBScript on Windows 11 24H2+"
    ],
    "ai_master_tags": [],
    "ai_model": "gpt-4.1",
    "ai_summary": "Admins should detect and migrate away from VBScript, as it is enabled by default on Windows 11 24H2 and will be disabled/removed in future deprecation phases.",
    "ai_topics": [
      "Windows"
    ],
    "category": "planForChange",
    "details_map": {},
    "id": "MC1075649",
    "importance": 1,
    "is_major_change": false,
    "last_modified": "2025-05-16T17:04:14Z",
    "ms_products": [
      "Windows"
    ],
    "platforms": null,
    "roadmap_ids": [],
    "services": [
      "Windows"
    ],
    "severity": "normal",
    "tags": [
      "Admin impact"
    ],
    "title": "VBScript deprecation: Detection strategies for Windows"
  }
}