Fix ERROR_CANT_RESOLVE_FILENAME (0x00000781) on Windows 10/11

Quick fix (30 seconds) — Check for a broken shortcut

This error pops up when Windows tries to resolve a file path that’s gone bad. The culprit here is almost always a shortcut (.lnk file) pointing to a file or folder that’s been moved, renamed, or deleted. You’ll see it most often when you click a desktop shortcut or an item in the Start menu that used to work.

1. Right-click the shortcut causing trouble and select Properties.
2. Look at the Target field — does the path actually exist? If it’s pointing somewhere that’s now empty, that’s your problem.
3. Delete the shortcut. Recreate it from the real file location (right-click file → Create shortcut).
4. Test it. If the error’s gone, you’re done. Skip the rest.

If the shortcut looks fine or you don’t know which one is triggering it, move to the moderate fix.

Moderate fix (5 minutes) — Run the System File Checker and clean up the index

Sometimes the file system itself gets a little confused — a corrupted index entry or a wonky NTFS permission can cause this error. Two things fix it fast.

Step 1: Run SFC

Open Command Prompt as Administrator (Win + X → Terminal (Admin)) and run:

sfc /scannow

Let it finish. If it finds corrupted files, it’ll repair them automatically. Reboot after it’s done.

Step 2: Rebuild the search index

Windows Search maintains a database of file names. If that index gets corrupted, you’ll see 0x00000781 when trying to open files from search results or from certain apps that query the index (like Outlook or File Explorer’s search).

1. Go to Control Panel → Indexing Options.
2. Click Advanced.
3. Under Troubleshooting, click Rebuild. This takes a few minutes — don’t interrupt it.
4. Once it’s done, restart your PC and test the error again.

Advanced fix (15+ minutes) — Check for disk corruption and repair permissions

If the first two fixes didn’t work, the issue is deeper — likely bad sectors on the drive or messed up NTFS permissions. I’ve seen this happen after a sudden power loss or a failed update on Windows 10 22H2 and Windows 11 23H2.

Step 1: Run CHKDSK

Open Command Prompt as Admin and run:

chkdsk C: /f /r

It’ll ask to schedule a scan on next reboot. Say Y, restart, and let it run. This takes 15–30 minutes depending on drive size. It fixes file system errors and marks bad sectors.

Step 2: Reset NTFS permissions

If the file or folder is readable but still throws the error, permissions might be the problem. Navigate to the parent folder in File Explorer, right-click it → Properties → Security → Advanced.

• Click Disable inheritance → Convert inherited permissions into explicit ones.
• Then click Add → Select a principal → type Everyone → give Read & execute permissions.
• Check Replace all child object permissions and hit OK.

This brute-force fix resets all permissions in that folder tree. It’s overkill for most cases, but when nothing else works, it does.

Step 3: Last resort — create a new user profile

If the error follows you everywhere, your user profile might be corrupted. Create a new local admin account (Settings → Accounts → Other users → Add someone else), log into it, and see if the error repeats. If it doesn’t, migrate your files and ditch the old profile.

Pro tip: If this error happens after a Windows update, roll back the update first (Settings → Windows Update → Update history → Uninstall updates). I’ve saved hours of troubleshooting by doing this.