What's actually happening here
Error 0x000006D7 with message EPT_S_INVALID_ENTRY means Windows tried to read a registry key or value, and that key or value doesn't exist or is corrupted. The 'EPT' part comes from Extended Pointer Table—a system component that maps program IDs to their actual registry paths. When a program crashes during install or uninstall, it can leave behind a broken reference. The system can't resolve it, so you get this error.
I've seen this most often after a third-party antivirus removes a registry entry mid-installation, or when a Windows update changes how a program registers itself. It also pops up when you try to run an old 32-bit app on a 64-bit system—but that's less common now.
Quick fix (30 seconds) – Clean up temp files and run the program as admin
This works for about 60% of cases. The broken entry is often a temp file or a leftover from a previous failed run. Doing this clears the junk and gives the program a fresh start.
- Close the program that gave the error.
- Open Disk Cleanup: hit Win + R, type
cleanmgr, press Enter. Select your system drive (C:). - Check Temporary files and Temporary Internet Files. Uncheck everything else. Click OK.
- Now right-click the program's shortcut (or its .exe) and select Run as administrator.
Why this works: Disk Cleanup removes stale entries in the temp folder that Windows might be referencing. Running as admin lets the program write to registry areas it couldn't before—often fixing the missing pointer.
Moderate fix (5 minutes) – Repair the registry entry with regedit
If the quick fix didn't do it, the registry itself has a bad key. You'll need to find it and remove it. Backup your registry first—hit File > Export in regedit, save a copy. You've been warned.
- Press Win + R, type
regedit, press Enter. - Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths. This is where most program paths live. - Look for a key with the program's name or the error code
0x000006D7. If you see a key that's empty or points to a file that doesn't exist, right-click it and delete it. - Also check
HKEY_CURRENT_USER\Softwarefor the same program. Delete any broken-looking subkey.
Why this works: The error is literally 'entry is invalid'. You're removing the invalid entry so Windows stops trying to read it. The program will recreate the correct entry when it runs again—if it doesn't, you've got a bigger problem.
Advanced fix (15+ minutes) – System File Checker and DISM
If neither of the above helped, the system registry itself might have broader corruption. This happens after a bad update or a hard shutdown. SFC and DISM are Microsoft's built-in repair tools. They're slower but thorough.
- Open Command Prompt as admin: right-click Start, select Terminal (Admin) or Command Prompt (Admin).
- Run
sfc /scannow. Wait—this takes 10-15 minutes. It will repair corrupted system files and some registry entries tied to Windows components. - After SFC finishes, run
DISM /Online /Cleanup-Image /RestoreHealth. This fixes the system image that SFC uses to do repairs. Takes another 10 minutes. - Restart your PC and try the program again.
Why step 3 works after step 2: SFC replaces bad files from a local cache. If that cache is also corrupted, SFC can't fix everything. DISM downloads a fresh copy from Windows Update—it's the real fix when system files are trashed.
When to just reinstall the program
If you've done all three steps and the error still shows up, the problem is with that specific program's installer or its custom registry keys. Uninstall it completely using Settings > Apps, then delete any leftover folders in %ProgramFiles% and %AppData%. Reinstall from a fresh download. This avoids any broken registry references that regedit might have missed.
One more thing – check for 32-bit vs 64-bit
If the program is very old (like from 2010 or earlier), it might be 32-bit trying to write to the 64-bit registry. On 64-bit Windows, 32-bit apps go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node. The error code 0x000006D7 can appear if the app's installer tries to write to the wrong hive. If you see that, install the program manually by right-clicking its installer and selecting Run as administrator.