Fix STATUS_NO_MORE_ENTRIES (0x8000001A) Error on Windows

Quick Answer (for pros)

Run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth in an admin Command Prompt. If that doesn't cut it, check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion for missing or corrupt subkeys—specifically ones tied to the app throwing the error.

I know this error is infuriating. You're just trying to run an app or browse a list of devices, and bam—STATUS_NO_MORE_ENTRIES (0x8000001A) kills the whole thing. The cryptic part? It literally means Windows tried to find the next item in a list (like files, hardware devices, or event logs) and found squat—even though there should be more. Usually this is a corrupted enumeration buffer, a broken system file, or a misbehaving driver that's eating your data too fast.

Let's fix it without the fluff.

Step-by-Step Fix

Step 1: Run System File Checker (SFC)

This is my go-to first move. Open Command Prompt as Administrator—right-click Start, pick Command Prompt (Admin) or Terminal (Admin). Type:

sfc /scannow

Let it run. It takes 10-15 minutes on modern hardware. If it finds corrupt files, it'll replace them automatically. Reboot after.

Step 2: Run DISM to Fix the System Image

If SFC didn't catch everything—and it often doesn't—DISM digs deeper. Same admin prompt, type:

DISM /Online /Cleanup-Image /RestoreHealth

This checks for component store corruption. It needs internet to pull fresh files from Windows Update. Takes about 20 minutes on a decent connection. Reboot again.

Step 3: Check the Registry for the Offending App

This tripped me up the first time too. The error often comes from a specific app that's reading a registry key or file list that got truncated. Open Regedit (type regedit in Run). Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

Look for any subkey related to the app that's crashing—like under Uninstall or App Paths. If you see weird entries (e.g., garbage characters, missing values), that's your culprit. Export the key as a backup, then delete the broken subkey. I've seen this fix errors in old printer enumerators and abandoned software.

Step 4: Update or Roll Back Drivers

If the error shows up when you're poking around Device Manager or a hardware list, a driver is likely the problem. Open Device Manager, find the device that triggers the error—say your network adapter or graphics card. Right-click, Properties, Driver tab. Try Update Driver (search automatically). If it's already up to date? Roll back to the previous version. Windows 11 especially has a habit of pushing experimental drivers through Windows Update that break enumeration.

Alternative Fixes (If the Main Ones Fail)

Fix 1: Run a Windows Update Check

Sounds basic, but a recent cumulative update might have a patch for this exact bug. Go to Settings > Update & Security > Windows Update, click Check for updates. Install everything pending, reboot. I've seen this resolve the error in Windows 10 22H2 specifically.

Fix 2: Clean Boot to Find the Problem

Sometimes a third-party service or startup program corrupts the enumeration. Type msconfig in Run, go to Services tab, check Hide all Microsoft services, then Disable all. Reboot. If the error disappears, re-enable services one by one until you find the offender—usually an old antivirus or cloud storage sync tool.

Fix 3: Repair the App That Throws the Error

If the error pops up in a specific program (like an old game launcher or accounting software), try its repair option. Go to Settings > Apps > Installed apps, find the app, click the three dots, Modify, then Repair. This fixed the error for a client using a 2018 version of QuickBooks.

Prevention Tips

Keep your system files clean. Run SFC once a month—I do it on the first of every month.
Don't install random registry cleaners. They delete stuff they shouldn't. Stick to manual edits with backups.
Update drivers only from manufacturer sites. Not Windows Update. Especially for GPUs and network cards.
Check your disk for errors. Run chkdsk /f in admin prompt—it fixes file system corruption that can trigger enumeration failures.

This error is ugly, but it's almost always fixable with SFC, DISM, or a targeted registry clean-up. Start there, and you'll be back to work in under an hour.