QUICK ANSWER

OptionalFeatures.exe opens the Windows Features dialog, where an administrator can enable or disable operating-system components such as Hyper-V, Internet Information Services (IIS), Windows Sandbox, legacy .NET Framework components, and certain networking services. Press Windows+R, enter optionalfeatures, and select OK.

Windows normally services these components from its component store. Some features require files from Windows Update, installation media, or an organization-managed source. Changes may require administrator approval, dependent features, additional downloads, or a restart.

 

OptionalFeatures.exe and Windows Features: Complete Guide to Enabling, Disabling, and Managing Optional Components

What Is OptionalFeatures.exe?

OptionalFeatures.exe is the Windows system program that opens the Turn Windows features on or off dialog. It is normally located at:

C:\Windows\System32\OptionalFeatures.exe

The dialog manages optional components integrated into Windows. These components are not ordinary desktop applications: Windows services them as part of the operating-system image.

Common examples include:

• Hyper-V components
• Internet Information Services (IIS)
• Windows Sandbox
• Windows Subsystem for Linux
• Virtual Machine Platform
• .NET Framework 3.5 components
• Microsoft Print to PDF
• Legacy networking and file-sharing components

The exact list depends on the Windows edition, version, architecture, installed packages, device capabilities, and organizational policies.

Windows Features Versus Optional Features in Settings

Windows exposes two related management interfaces.

The categories can overlap conceptually, but they are not interchangeable. A component missing from OptionalFeatures.exe may be available through Settings, DISM capability commands, another Windows package, or a separate Microsoft installer.

To open the Settings page directly, press Windows+R and run:

ms-settings:optionalfeatures

Microsoft documents Settings as the primary interface for adding and removing many modern optional features. learn.microsoft.com

How Windows Features Work

Windows uses its servicing infrastructure—including the component store and Deployment Image Servicing and Management—to control optional components.

When you enable a feature, Windows may:

1. Check whether the required payload is already stored locally.
2. Enable required parent or dependent components.
3. Obtain missing files from Windows Update, a Features on Demand repository, installation media, or an organization-managed repair source.
4. Configure services, drivers, packages, or system files.
5. Request a restart if files or services cannot be changed while Windows is running.

When you disable a feature, Windows normally turns off its functionality but may retain the payload in the component store. Some management commands can remove the payload more completely; reinstalling such a feature then requires a valid source.

Microsoft supports servicing features in both the running operating system and mounted offline Windows images. learn.microsoft.com

Benefits of Optional Windows Features

Reduced default attack surface

Windows does not need to activate every server, virtualization, legacy, or development component on every computer. Leaving unnecessary components disabled can reduce the number of active services and protocols that must be secured.

Support for specialized workloads

Administrators and developers can add functionality only where it is required—for example, IIS for local web development, Hyper-V for virtualization, or WSL for Linux development tools.

Centralized servicing

Windows can service integrated features through supported Windows servicing mechanisms rather than relying on unrelated third-party installers.

Easier standardization and automation

IT departments can use DISM, PowerShell, provisioning processes, or management platforms to configure consistent feature sets across multiple devices.

Offline image management

DISM can enable or disable features in a mounted Windows image before that image is deployed to computers.

How to Open Windows Features

Method 1: Run command

1. Press Windows+R.

2. Enter:

   optionalfeatures

3. Select OK.

4. Approve the User Account Control prompt if Windows displays one.

You can also run the full path:

C:\Windows\System32\OptionalFeatures.exe

Method 2: Windows Search

Search for:

Turn Windows features on or off

Open the matching Control Panel result.

Method 3: Control Panel

1. Open Control Panel.
2. Select Programs.
3. Under Programs and Features, select Turn Windows features on or off.

Understanding the Check Boxes

The Windows Features dialog can display three checkbox states:

A partially selected parent feature is not necessarily faulty. Expand it to see which child components are active.

How to Enable a Windows Feature Safely

1. Open OptionalFeatures.exe.
2. Locate and, when available, expand the required feature.
3. Select only the components you need.
4. Select OK.
5. Allow Windows to search for or download required files.
6. Restart if prompted.
7. Verify that the required application, service, or command works.

Before enabling virtualization features such as Hyper-V, Virtual Machine Platform, or Windows Sandbox, confirm that the Windows edition and hardware meet their requirements. Virtualization-based components can also affect certain third-party hypervisors, security products, and performance-sensitive workloads.

How to Disable a Windows Feature Safely

1. Confirm that no application, service, or business process depends on the feature.
2. Open OptionalFeatures.exe.
3. Clear the feature’s checkbox.
4. Review any dependency warning.
5. Select OK.
6. Restart if requested.
7. Test affected applications and services.

Disabling a feature can also disable dependent subfeatures. For example, removing a web-server component can stop locally hosted websites and applications.

Warning: Do not disable an unfamiliar feature merely to improve performance. Many disabled components consume no meaningful runtime resources, while removing a required dependency can break applications.

Managing Windows Features with PowerShell

Run Windows PowerShell as an administrator.

List available feature names and states

Get-WindowsOptionalFeature -Online

Show a specific feature:

Get-WindowsOptionalFeature -Online -FeatureName "Microsoft-Hyper-V-All"

Enable a feature

Enable-WindowsOptionalFeature -Online -FeatureName "Microsoft-Hyper-V-All" -All

-All enables required parent features where applicable.

Disable a feature

Disable-WindowsOptionalFeature -Online -FeatureName "Microsoft-Hyper-V-All"

Add -NoRestart when a script must prevent an automatic restart:

Disable-WindowsOptionalFeature -Online -FeatureName "Microsoft-Hyper-V-All" -NoRestart

PowerShell can manage either the running system with -Online or a mounted Windows image with -Path. learn.microsoft.com

Feature names are case-insensitive, but they must otherwise be correct. Always query the device rather than copying an unverified name from another Windows version.

Managing Windows Features with DISM

Open Windows Terminal (Administrator) or Command Prompt (Administrator).

List features

DISM /Online /Get-Features /Format:Table

View details for one feature

DISM /Online /Get-FeatureInfo /FeatureName:NetFx3

Enable a feature and required parents

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

Disable a feature

DISM /Online /Disable-Feature /FeatureName:NetFx3

Prevent an immediate restart

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /NoRestart

/Online means the command targets the currently running Windows installation. DISM can also service a mounted offline image by using /Image:<path> instead. Microsoft documents DISM as the supported command-line method for managing optional components in online and offline Windows images. learn.microsoft.com

Features Versus Capabilities

Not every optional component is managed by Get-WindowsOptionalFeature or DISM /Get-Features. Windows also uses capabilities, commonly called Features on Demand.

List capabilities with:

DISM /Online /Get-Capabilities

Or use PowerShell:

Get-WindowsCapability -Online

Install a capability with its exact reported name:

Add-WindowsCapability -Online -Name "<CapabilityName>"

Remove one with:

Remove-WindowsCapability -Online -Name "<CapabilityName>"

Do not substitute a display name for the capability identity. First query the target computer and copy the exact value from its output. Microsoft notes that available Features on Demand vary by Windows image and can be enumerated with DISM. learn.microsoft.com

Using an Alternate Source for Missing Files

Some components—most notably .NET Framework 3.5 in certain deployment scenarios—may need source files that are not stored locally.

DISM supports a source path:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /Source:X:\sources\sxs /LimitAccess

Replace X: with the drive containing compatible Windows installation media.

Important requirements:

• The source should match the installed Windows release, architecture, language, and servicing level as closely as possible.
• /LimitAccess prevents DISM from contacting Windows Update.
• Do not download component-store files from unofficial websites.
• In managed environments, use the repair source or Features on Demand repository approved by the organization.

A mismatched source can produce “source files could not be found” or package-applicability errors.

Enterprise, WSUS, and Policy Considerations

Optional-feature installation can fail on domain-managed devices even when the internet works. Common causes include:

• Windows Update access is restricted.
• The device is configured to use WSUS or Configuration Manager.
• Required Features on Demand content is unavailable from the selected scan source.
• A policy specifies an invalid or inaccessible repair location.
• The Settings or Windows Features interface is hidden by policy.
• The user lacks local administrator rights.

Microsoft documents specific deployment considerations for making Features on Demand and language packs available in WSUS or Configuration Manager environments. learn.microsoft.com

Administrators should review applicable Windows Update policies and the Specify settings for optional component installation and component repair policy before bypassing organizational update controls.

Security and Compatibility Considerations

Avoid enabling legacy protocols without a documented requirement

Legacy features can introduce unnecessary risk. A prominent example is SMB 1.0/CIFS File Sharing Support. Do not enable it merely to work around access problems with an old device. Updating or replacing the device is safer.

Install only the required IIS components

IIS contains numerous subfeatures. A development computer may not need FTP, legacy management compatibility, all authentication mechanisms, or every application-development component.

Understand virtualization changes

Hyper-V, Windows Sandbox, WSL 2, and Virtual Machine Platform can activate Windows virtualization infrastructure. Confirm compatibility with other virtualization software, device security requirements, firmware settings, and licensing before deployment.

Do not remove payloads casually

Disabling a feature is usually easier to reverse than removing its payload. Payload removal saves some disk space but creates a future dependency on Windows Update or a compatible source.

Restart when requested

A pending restart can leave a feature in a transitional state. Save work and restart promptly when Windows requires it.

How to Verify a Feature’s Status

PowerShell

Get-WindowsOptionalFeature -Online -FeatureName "<FeatureName>"

Review the State property. Possible results can include enabled, disabled, or disabled with its payload removed.

DISM

DISM /Online /Get-FeatureInfo /FeatureName:<FeatureName>

Graphical interface

Reopen OptionalFeatures.exe and check the feature’s checkbox. Remember that a filled box means only some subfeatures are selected.

For capabilities, use:

Get-WindowsCapability -Online

Troubleshooting Windows Features

The feature list is empty or OptionalFeatures.exe does not open

1. Restart Windows and try again.

2. Install pending Windows updates.

3. Open an administrator terminal and check the Windows image:

   DISM /Online /Cleanup-Image /ScanHealth

4. If corruption is reported or strongly suspected, run:

   DISM /Online /Cleanup-Image /RestoreHealth

5. Then verify protected system files:

   sfc /scannow

6. Restart Windows and test again.

These repair commands address component-store or protected system-file problems; they do not override organizational policy or make an unsupported feature available.

Windows cannot find the required source files

• Confirm that Windows Update is accessible.
• Check proxy, firewall, WSUS, Configuration Manager, and Group Policy settings.
• Use compatible Windows installation media or an approved Features on Demand source.
• Verify that the source matches the installed Windows version and architecture.
• Ask the organization’s administrator before changing update-source policies.

A feature name is unknown

Display the names supported by that computer:

DISM /Online /Get-Features /Format:Table

For capabilities, run:

DISM /Online /Get-Capabilities

Feature and capability identities are different and cannot be used interchangeably.

The feature remains disabled after installation

• Restart the computer if a restart is pending.
• Check the feature’s state with PowerShell or DISM.
• Enable required parent features with PowerShell’s -All option or DISM’s /All option.
• Check Event Viewer > Applications and Services Logs > Microsoft > Windows > DISM > Operational for servicing errors.
• Verify edition, hardware, and firmware requirements.

Error 0x800F081F or 0x800F0906 appears

These errors commonly indicate that Windows cannot locate or download the required component files. Verify the repair source, Windows Update connectivity, enterprise servicing policies, and source compatibility.

The feature is not listed

Possible explanations include:

• The component is a Windows capability rather than a Windows feature.
• It is unavailable in the installed Windows edition or version.
• Required hardware is absent or disabled.
• The organization has restricted access.
• The component has been removed, replaced, or installed by another method.
• The operating system is a modified or specialized image.

When to Use Each Management Method

FAQ

Frequently Asked Questions

Does OptionalFeatures.exe require administrator rights?

Opening the dialog may be possible without elevation, but changing system components normally requires administrative approval. Organizational policy can impose additional restrictions.

Is OptionalFeatures.exe safe?

The Microsoft-supplied executable in C:\Windows\System32 is a legitimate Windows component. The available features are not automatically appropriate for every device, so enable only components you understand and require.

Does disabling a feature uninstall it completely?

Not always. Windows can disable functionality while retaining its payload in the component store. Some servicing operations can remove the payload, after which reinstalling it requires Windows Update or another compatible source.

Will disabling Windows features improve performance?

Usually not by itself. A disabled server, virtualization, or background-service component can reduce resource use or attack surface, but many inactive features consume little or no runtime processing. Disable features for a defined security, compatibility, or operational reason.

Why does Windows request internet access when enabling a feature?

The required payload may not be stored locally. Windows may need to retrieve it from Windows Update or another configured servicing source.

Can OptionalFeatures.exe manage remote computers?

The graphical dialog manages the local computer. Administrators should use approved remote-management, configuration-management, PowerShell remoting, or deployment tools for other devices.

What is the difference between disabling and removing a feature?

Disabling turns off the feature. Removing its payload also deletes the locally staged installation files, reducing disk usage but making future reinstallation dependent on an external source.

Can I enable every Windows feature at once?

This is neither recommended nor always possible. Features can have conflicting requirements, increase attack surface, consume storage, activate services, or require unsupported hardware. Install only what the computer’s workload needs.

Why is Hyper-V or Windows Sandbox missing?

Availability depends on factors such as Windows edition, processor architecture, hardware virtualization support, firmware configuration, security configuration, and operating-system version. Check the current Microsoft requirements for the specific feature.

FINAL RECOMMENDATION / CONCLUSION

Use OptionalFeatures.exe for straightforward, interactive management of integrated Windows components. Use Settings for modern optional capabilities and PowerShell or DISM when you need exact status information, automation, source control, or offline-image servicing.

Before changing a feature, verify its purpose, dependencies, edition requirements, security implications, and source-file availability. Avoid enabling obsolete protocols, use only Microsoft or organization-approved installation sources, and restart when requested. On managed computers, coordinate changes with the IT administrator rather than bypassing update or servicing policies.

 

#Windows #Windows11 #Windows10 #OptionalFeatures #OptionalFeaturesExe #WindowsFeatures #DISM #PowerShell #FeaturesOnDemand #WindowsAdministration #ITSupport #SystemAdministration #HyperV #WindowsSandbox #IIS #DotNETFramework #RSAT #WindowsTroubleshooting #ComponentStore #EndpointManagement

SOURCES

• Microsoft Learn — Add, remove, or hide Windows features: https://learn.microsoft.com/windows/client-management/client-tools/add-remove-hide-features
• Microsoft Learn — Enable or Disable Windows Features Using DISM: https://learn.microsoft.com/windows-hardware/manufacture/desktop/enable-or-disable-windows-features-using-dism
• Microsoft Learn — Get-WindowsOptionalFeature: https://learn.microsoft.com/powershell/module/dism/get-windowsoptionalfeature
• Microsoft Learn — Enable-WindowsOptionalFeature: https://learn.microsoft.com/powershell/module/dism/enable-windowsoptionalfeature
• Microsoft Learn — Disable-WindowsOptionalFeature: https://learn.microsoft.com/powershell/module/dism/disable-windowsoptionalfeature
• Microsoft Learn — Available Features on Demand: https://learn.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-non-language-fod
• Microsoft Learn — Features on Demand and language packs with WSUS or Configuration Manager: https://learn.microsoft.com/windows/deployment/update/fod-and-lang-packs