If the Windows Features dialog (optionalfeatures.exe) shows a blank list or no items at all, the Component-Based Servicing (CBS) store or the registry keys that populate the list are corrupted or missing. The fix is to repair the system files and rebuild the registry entries, usually with DISM and a registry edit, and in most cases this restores the full list without reinstalling Windows.
Why the Windows Features List Goes Blank
The Windows Features window is not a static list—it is populated on the fly by the Component-Based Servicing (CBS) infrastructure. When you open it, Windows reads the component store (usually C:\Windows\WinSxS) and the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex to enumerate every optional feature, from .NET Framework to Internet Information Services (IIS).
A blank list almost always means one of these three things:
- The CBS store is corrupted or has missing manifests.
- The
PackageIndexregistry key is missing or damaged (often after a failed update or a third-party “cleaner” tool). - System file corruption has broken the enumeration service (Windows Modules Installer).
It is rarely a display bug—the list is genuinely empty because Windows cannot find the feature definitions.
Before You Start: Check the Obvious
Spend 30 seconds ruling out simple causes before running repairs:
- Reboot the PC—a hung Windows Modules Installer service can cause a temporary blank list.
- Run
sfc /scannowfrom an elevated Command Prompt. If it finds and fixes corrupt files, reopen Windows Features. - Check if the list is blank for all users. Create a temporary local admin account and test—if it works there, the issue is profile-specific.
- Make sure you are looking at the right window:
optionalfeatures.exeshows the full list, while Settings > Apps > Optional Features shows a different, smaller set.
If those don’t help, move to the repair steps below.
Fix 1: Run DISM to Repair the Component Store
DISM (Deployment Imaging Servicing and Management) is the primary tool for repairing CBS corruption. Run these commands in an elevated Command Prompt, in order:
DISM /Online /Cleanup-Image /CheckHealth—quick check, no repair.DISM /Online /Cleanup-Image /ScanHealth—scans for corruption (can take 10–20 minutes).DISM /Online /Cleanup-Image /RestoreHealth—repairs using Windows Update.
If RestoreHealth fails because Windows Update itself is broken, point it at a known-good source:
DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
Replace C:\RepairSource\Windows with the path to a mounted Windows ISO or a WIM file from the same Windows version. After DISM finishes, run sfc /scannow again, then reboot and check the Features list.
Fix 2: Rebuild the PackageIndex Registry Key
If DISM reports no corruption but the list is still empty, the registry key that lists features is likely missing. This is common after aggressive registry cleaners or manual deletion of “Windows old” files.
Open Registry Editor (regedit) as administrator and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
Look for a subkey named PackageIndex. If it is missing, create it:
- Right-click
Component Based Servicing> New > Key. - Name it
PackageIndex. - Right-click
PackageIndex> New > DWORD (32-bit) Value. - Name it
Currentand set its value to1(hexadecimal).
Close Registry Editor and reboot. If the key existed but had a wrong value, set Current to 1 and reboot. This key tells Windows where to start enumerating features; a missing or zero value often results in an empty list.
Fix 3: Re-register the CBS and Modules Installer DLLs
Sometimes the list is blank because the DLLs that read the component store are not properly registered. In an elevated Command Prompt, run:
regsvr32 /s /i C:\Windows\System32\cbs.dll regsvr32 /s /i C:\Windows\System32\wmic.dll regsvr32 /s /i C:\Windows\System32\wuapi.dll
These commands re-register the servicing components. Reboot and test. This is a quick fix that works when the registry is intact but the DLLs are unregistered (often after a botched update rollback).
Fix 4: Use DISM to Rebuild the Component Store (Reset Base)
If the component store is so corrupted that RestoreHealth cannot fix it, you can reset the base with:
DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
This removes superseded versions of components and compacts the store. It does not remove features you have installed—it only cleans up old versions. Run this only after RestoreHealth succeeds, because it cannot repair corruption itself. After a reset, the Features list often repopulates because the store is rebuilt from the current manifests.
If none of the above works, the last resort is an in-place upgrade repair install using the Windows Media Creation Tool. That reinstalls Windows while keeping your files and apps, and it always rebuilds the component store from scratch.
Frequently Asked Questions
Why is my Windows Features list blank after a Windows Update?
Updates sometimes leave the CBS store in an inconsistent state—usually because a servicing stack update failed midway. The DISM RestoreHealth command is specifically designed to fix this, so run it first. If that doesn’t work, the PackageIndex registry key may have been reset to zero by the update; check and set it to 1 as described above.
Can I manually add features to the list?
No—the list is generated from the component store. You cannot type a feature name into the registry to make it appear. The only way to add a feature is to repair the store so Windows recognizes the installed manifests. If a specific feature is missing from the list, it usually means the feature’s manifest is corrupted, not that the list is broken.
Will these fixes remove my installed programs?
No. DISM and registry repairs only touch Windows system files and component store metadata. They do not affect user data, installed applications, or personal settings. The only exception is the in-place upgrade repair install, which reinstalls Windows but keeps your files and apps—it may remove some third-party drivers, but not your programs.
Is it safe to delete the PackageIndex registry key and let Windows recreate it?
Do not delete it manually. If the key is missing, Windows may not recreate it automatically, and you could end up with a broken servicing system. Instead, create the key with the Current value set to 1 as shown above. If the key exists but is corrupt, setting Current to 1 is the safest repair.
How long does DISM RestoreHealth take?
It depends on the size of your component store and the speed of your disk. On a typical system, ScanHealth takes 10–20 minutes, and RestoreHealth can take 20–40 minutes if it needs to download files. If you are using a local source (a mounted ISO), it is usually faster. Do not interrupt it—let it finish even if it appears stuck.
What if the list is blank but I can still install features via PowerShell?
If you can install a feature with Enable-WindowsOptionalFeature -Online -FeatureName but the GUI list is blank, the issue is likely a display-only problem with the optionalfeatures.exe window. Try running it as administrator, or use the DISM commands to repair the store—the same corruption that breaks the GUI may eventually break PowerShell too.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- VPN Setup on iPhone SE: Step-by-Step Guide
- Fix Internet Not Working on Windows 11
- How to Turn Off Shutter Sound on iPhone
- Fix Right Click Not Working in Firefox
- Compare Two Columns with Comma Separated Values in Excel
- How to Limit Ad Tracking on iPhone Apps