The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →VBScript is a Windows optional feature, not normally a separate desktop program. On Windows 11 version 24H2, it is delivered as a Feature on Demand, so an upgrade or servicing policy can leave it installed but disabled. You can add, enable, disable, or remove it from Optional features in Settings, or administer it with elevated Windows PowerShell. Confirm the feature state before changing anything, because legacy installers and applications may stop working when Windows Script Host/VBScript is unavailable.
What installing VBScript actually does
VBScript is Microsoft’s scripting technology used by older Windows scripts, setup programs, administration tools, and line-of-business software. Installing it does not install a new editor or a general-purpose application. It adds the Windows components that allow supported VBScript files and programs that call Windows Script Host to run.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The practical terms are slightly different depending on the action:
Recommended Free Tools
- Enable: Turn on a feature that is already present in the Windows image.
- Install or add: Add the optional-feature payload, usually obtained through Windows Update or an enterprise Features on Demand source.
- Disable: Turn off the feature while retaining its payload files, making it possible to re-enable without downloading all content again.
- Remove: Take the optional feature out of the client feature set. Windows may need a servicing source to add it back later.
These distinctions matter most on Windows 11 24H2 and later servicing states. Check the current state instead of assuming that a recent upgrade removed VBScript completely.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Check your Windows version and current VBScript state first
Before changing a feature, identify the edition and version involved. Press Windows + R, enter winver, and press Enter. Windows 11 version 24H2 is the important transition point because VBScript is handled as a Feature on Demand. Windows 10 uses a different Settings layout, while Windows Server has its own Features on Demand servicing workflow.
On a managed computer, also consider whether update policy, WSUS, or installation media controls optional-feature content. A feature can be listed but unavailable to download if the configured servicing source cannot provide its package.
If an older application is failing, note the exact error and test whether it invokes Windows Script Host or a .vbs file. Do this before removing or disabling the feature so you have a baseline for verification.
Install or enable VBScript from Settings
The Settings method is the supported graphical route for a single Windows client. The labels vary slightly by Windows build, so use the path that matches what you see.
Windows 11, including version 24H2
- Open Settings.
- Go to System > Optional features. On some builds, the page is under Apps > Optional features.
- Select View features.
- Search for VBScript, select the matching feature, and choose Next.
- Select Add. Windows will install or enable the feature and show its progress.
If VBScript already appears in the installed-feature list but is disabled, select it and use the available enable or install action rather than trying to add a duplicate entry. Windows 11 24H2 devices initially received the VBScript Feature on Demand pre-installed and enabled by default, but later servicing states and policy settings can leave it disabled.
Windows 10
- Open Settings.
- Go to Apps > Apps & features > Optional features. The exact wording and placement vary by Windows 10 build.
- Select Add a feature.
- Find VBScript, select it, and choose Install or Add.
Windows generally obtains optional-feature content through Windows Update. Give the device network access and make sure update policy permits optional-feature downloads. On an organization-managed PC, the required package may instead come from WSUS, local installation media, or another configured Features on Demand repository.
How to confirm the Settings installation
Return to the Optional features page and locate VBScript in the installed list. If the entry shows an installed or enabled state, retry the dependent script or application. A restart is not always required, but follow any restart prompt before concluding that the change failed.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Install or enable VBScript with PowerShell
PowerShell is the better choice for administrators, repeatable procedures, and computers where the Settings page is hidden. Open Windows PowerShell as Administrator; a non-elevated window normally cannot change optional Windows features.
1. Discover the exact feature name
Feature names can vary by Windows release. Query the online operating-system image and filter the result:
Get-WindowsOptionalFeature -Online | Where-Object FeatureName -match 'VBScript|Script'
Read both the FeatureName and State values. The state tells you whether the feature is enabled, disabled, or otherwise unavailable in the current image. Copy the exact feature name returned by your computer instead of guessing it.
2. Enable the feature
Replace the value inside <FeatureName> with the name returned by the query:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Enable-WindowsOptionalFeature -Online -FeatureName <FeatureName> -All
The -All switch includes required parent features. The command reports progress and whether Windows requires a restart. Restart when prompted, or add -NoRestart if an automation run must control reboot timing:
Enable-WindowsOptionalFeature -Online -FeatureName <FeatureName> -All -NoRestart
Using -NoRestart does not remove the restart requirement; it only postpones the automatic reboot. Schedule the restart before testing software that depends on VBScript.
3. Verify the result
Run the discovery command again and confirm the state has changed to enabled. Then test the actual script or application. A successful feature change does not repair a damaged script, a missing third-party dependency, or an application configured with an incorrect path.
Disable VBScript without removing its payload
Disabling is the reversible administrative option when you want VBScript unavailable but may need to restore it quickly. In elevated Windows PowerShell, first identify the exact name, then run:
Disable-WindowsOptionalFeature -Online -FeatureName <FeatureName>
Windows reports whether a restart is required. For a scripted maintenance window, use:
Disable-WindowsOptionalFeature -Online -FeatureName <FeatureName> -NoRestart
After the scheduled restart, applications that invoke Windows Script Host or VBScript will no longer run until the feature is enabled again. Keep a record of the feature name and previous state if the change is part of a security baseline or troubleshooting experiment.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Uninstall or remove VBScript
Removing the feature is different from deleting .vbs files. User scripts remain in their folders, but Windows no longer supplies the optional component needed to execute them.
Remove it through Settings
- Open Settings and go to Optional features.
- Under Installed features, locate VBScript.
- Expand the entry and choose Remove.
- Allow Windows to complete servicing and restart if requested.
If you later need VBScript, add it again through the same Optional features page. Windows Update, WSUS, or an enterprise Features on Demand source may be required to restore removed content.
Remove or disable it with PowerShell
Use the same discovery command to obtain the exact feature name. To disable while retaining payload files, use Disable-WindowsOptionalFeature. To remove the component from the image, use the Windows optional-feature removal operation available in your servicing workflow and follow the restart instructions shown by Windows. For routine client administration, Microsoft documents PowerShell as the method for disabling specific features; the Settings page is normally simpler for removal on an individual PC.
Do not attempt to uninstall VBScript by deleting system DLLs, registry entries, or files from the Windows directory. Manual deletion can corrupt servicing and will not produce a supported feature state.
Settings versus PowerShell: which method should you use?
| Decision point | Settings | PowerShell |
|---|---|---|
| Best audience | Individual users and technicians working on one interactive client | Administrators, support teams, and scripted maintenance |
| Repeatability | Manual; suitable for occasional changes on one device | Repeatable commands that can be embedded in scripts, deployment tasks, or remediation workflows |
| Feature-name handling | Searches for the friendly name VBScript | Requires discovering and supplying the exact feature name returned by the image |
| Reboot control | Windows presents prompts during the graphical operation | -NoRestart lets automation defer the reboot, while still reporting that one may be required |
| Servicing source | Uses the client’s configured Windows Update, WSUS, or Features on Demand source | Uses the same servicing configuration, but exposes errors and state in command output |
| Windows version coverage | Windows 10 and Windows 11 layouts differ; Windows 11 24H2 treats VBScript as a Feature on Demand | Works with the optional-feature servicing model on supported client and Server releases |
| Fleet use | Not practical for many machines | Suitable for PowerShell scripts, Intune deployment, and servicing policies |
Group Policy can hide the Optional features interface, but it does not itself disable a particular feature. If a policy removes the page, use an approved elevated PowerShell or management workflow to change VBScript state.
Windows 11 24H2 and VBScript Feature on Demand behavior
Windows 11 version 24H2 is the key client transition. VBScript is packaged as a Feature on Demand rather than being treated only as an always-present component. Microsoft’s staged deprecation guidance means that availability can change with servicing state and policy.
- On the initial 24H2 phase, the package was pre-installed and enabled by default.
- A later update, policy, image customization, or administrator action can leave it disabled.
- An entry that is present but disabled usually needs enabling, not a fresh download.
- A removed payload may require Windows Update, WSUS, or enterprise Features on Demand media before it can be restored.
Therefore, check Optional features or the PowerShell state output before troubleshooting an application. Treat “not running” and “not installed” as different conditions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Windows Server considerations
Windows Server uses a separate Features on Demand workflow covering supported Server releases, including Windows Server 2025, 2022, 2019, and 2016. Server administrators should use the feature-management tools and servicing source appropriate to the installed release rather than assuming that a Windows 11 Settings path exists.
On a Server installation, confirm the server version, available Features on Demand source, and maintenance-window requirements. In a managed environment, document whether the package comes from Windows Update, WSUS, mounted media, or an internal repository. The same principle applies: inspect state first, change it with an elevated administrative method, restart when required, and test every dependent workload.
Troubleshooting installation and removal problems
VBScript does not appear in Optional features
- Confirm that the device is running a supported Windows edition and that you checked the correct Settings path for its build.
- Run the PowerShell discovery command to see whether the feature exists under a different displayed name.
- Check whether organizational policy hides Optional features or restricts Feature on Demand installation.
- Verify that Windows Update, WSUS, or the configured Features on Demand source is reachable and authorized to provide the package.
The feature is listed but cannot be added
Optional-feature content is normally downloaded through the configured servicing source. A blocked network connection, paused update service, WSUS classification, or missing local source can prevent installation. On a managed PC, ask the administrator which source should provide Features on Demand; changing update policy on your own may violate the organization’s configuration.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPowerShell says the feature name is invalid
Do not substitute a remembered name from another Windows release. Run Get-WindowsOptionalFeature -Online again, inspect the complete FeatureName, and copy it exactly. Filtering for VBScript|Script helps locate likely entries but does not replace confirmation of the returned value.
Windows asks for a restart
A restart may be required after enabling, disabling, or removing an optional feature. If you used -NoRestart, finish the operation within the planned maintenance window and reboot before testing. Do not judge the change from a process that was already running before the feature transition; close and relaunch the application after Windows has restarted.
An installer fails after VBScript was removed
Some legacy installers invoke Windows Script Host or a VBScript custom action. On Windows 11 24H2 and later servicing states, a missing VBScript dependency can stop installation. Re-enable or reinstall the feature, restart if requested, and run the installer again. If it still fails, verify the installer’s other prerequisites instead of assuming VBScript is the only cause.
A script still fails after enabling VBScript
Confirm the feature state after reboot, then check the script path, file association, permissions, execution context, and any external components it calls. Enabling VBScript only restores the Windows capability; it does not fix a malformed script or a broken application configuration.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsSecurity and compatibility trade-offs
Disabling VBScript can reduce exposure from unwanted legacy script execution, but it can also break software that has not been modernized. Removing it is safest when you have inventoried applications, scheduled a rollback path, and tested representative user and server workflows.
Before a broad rollout, use a staged process:
- Inventory installers, login scripts, scheduled tasks, and applications that may call
.vbsfiles or Windows Script Host. - Test the disable or removal change on a pilot device that mirrors the production Windows version and servicing policy.
- Record the prior feature state and the exact PowerShell command needed to restore it.
- Apply the change during a maintenance window and monitor installation, logon, and automation failures.
- Re-enable or reinstall VBScript promptly if a required dependency is discovered, then plan a supported migration away from the legacy script.
For a single computer, Settings provides the clearest reversible workflow. For a fleet, use an approved administrative script or management policy, include reboot handling, and maintain a documented rollback.
Quick Recap
Quick decision guide
| Your situation | Recommended action |
|---|---|
| One Windows 10 PC needs an old script | Use Settings > Apps > Optional features, add VBScript, restart if prompted, and test the script. |
| One Windows 11 24H2 PC lists VBScript as disabled | Select the existing entry and enable it; do not remove and redownload it unless the payload is missing. |
| You administer many Windows clients | Discover the exact feature name with PowerShell, then automate enable/disable commands through your approved management platform. |
| You want a reversible security test | Disable the feature rather than removing it, record the previous state, and schedule the required restart. |
| You are decommissioning a legacy dependency | Remove VBScript only after application testing and retain a Features on Demand source for rollback. |
| A Windows Server workload requires VBScript | Use the Server release’s Features on Demand workflow and verify the configured servicing source before changing the feature. |
Final checklist
- Identify the Windows version, edition, and—on clients—whether the device is Windows 11 24H2.
- Inspect the current VBScript feature state before changing it.
- Use Settings for a one-off client change; use elevated PowerShell for repeatable administration.
- Confirm that Windows Update, WSUS, or another approved Features on Demand source can provide missing content.
- Honor any restart requirement, including one deferred with
-NoRestart. - Test legacy installers, scripts, and applications after enabling, disabling, or removing the feature.
- Keep a rollback command and servicing source available before changing managed devices.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

