Fix 0x780 ERROR_CANT_ACCESS_FILE (File Locked/Security)

You're trying to open a file—maybe a Word doc from a network share, or a config file inside Program Files—and instead of the content, you get a popup: ERROR_CANT_ACCESS_FILE with code 0x00000780. The file exists, you can see it in Explorer, but Windows flat-out refuses to let you read it. I've seen this on file servers and local drives, usually after an update or when a backup job runs. It's not a corrupt file—it's a lock or a permissions problem.

What's going on under the hood?

That error code translates to "The file cannot be accessed by the system." In my experience, 80% of the time it means another process has the file open exclusively—like a database, an antivirus scanner, or a stuck Windows service. The other 20%? The file's security descriptor (ACL) is messed up, or the file is marked for deletion but still referenced.

I once spent an hour chasing this on a client's QuickBooks file. Turned out their backup software was holding the file open since 2 AM. So before you go changing permissions, check for locks.

Step-by-step: Find the culprit and fix it

Close all obvious programs. If the file is in Office or an app, close them. But if the error persists, go to step 2.
Check for locks with Sysinternals handle.exe. Download it from Microsoft (it's free), open an admin command prompt, and run:

handle.exe -a "C:\full\path\to\file.ext"

This prints the process name and PID that has the file open. If you get something like backup.exe (pid 1234), you've found your villain.

Kill that process (if it's safe—don't kill a system process like svchost.exe without testing first). In the same admin prompt:

taskkill /PID 1234 /F

Then try accessing the file again. If that fixes it, you're done. If not, move on.

Reboot, then test. Sounds dumb, but a reboot clears all handles. If the file opens after a clean reboot, it was a lock. If not, it's permissions.
Check file permissions. Right-click the file → Properties → Security tab. Make sure your user account (or a group you're in, like Users) has at least Read. If the list is empty or shows weird entries like S-1-5-21..., that's a problem.

To fix ACLs safely, open an admin command prompt and run:

icacls "C:\full\path\to\file.ext" /grant "%USERNAME%":F

That grants full control to your user. Test again.

Check if the file is marked for deletion. If you see the file but can't open it and a reboot doesn't help, it might be pending deletion. Try renaming it. If that fails, restart Explorer or the process that held it.

If it still fails after these steps

You're past the common causes. Here's what I'd check next:

Antivirus/firewall interference. Temporarily disable real-time protection and try opening the file. If it works, add an exception.
File ownership. Sometimes the file is owned by SYSTEM and your admin account can't touch it. In the Security tab, click Advanced → Change next to Owner. Set it to your account, then grant yourself permissions.
Disk errors. Run chkdsk /f on that drive. I had a client with a dying hard drive where random files threw this exact error.
If it's on a network share, check the server. The lock might be on the server side. Try copying the file to your local desktop and opening it from there.

Real talk: I've fixed more 0x780 errors with handle.exe than with any permission change. Locks are the sneaky ones. Always check that first.

After you get the file open, take a second to figure out which app was holding it. If it's a backup product, configure it to use Volume Shadow Copy instead of direct file access—otherwise you'll see this again every time you need the file during a backup window.

This error isn't a death sentence. It's Windows being overly protective. With a bit of process hunting, you'll be back in that file before your coffee gets cold.