Why does my computer say 'permission denied' when I own the file?
Because ownership and permission are different things, and the account you are logged in as may not be the account the system associates with that file — which happens far more often than people expect, particularly after moving files between machines, drives or user accounts.
What is actually being checked. Every file carries an owner and a set of permissions describing what the owner, a group and everyone else may do. An operation is allowed only if your current process has the right permission — which is not the same as you believing you own the file.
The common causes:
The file was created by another account. Copying from another machine, restoring a backup, or retrieving files from an old user profile brings the original ownership with it. Your username may look the same and the underlying account identifier is different, which is why the file looks like yours and behaves as though it is not.
System-protected locations. Files in program and system directories are deliberately protected, and an application writing there without elevation fails.
Something else has it open. A file locked by a running process — including antivirus, a sync client or an indexer — cannot be modified, and the error is frequently reported as a permission problem rather than a lock.
Read-only media or attributes, including write-protected cards and drives, and files marked read-only.
A disk error, where a filesystem remounts read-only to protect itself. This one matters — it usually indicates a failing drive, and the correct response is to back up rather than to force the permission change.
External drives formatted for another system, where the permission model does not translate.
Cloud sync placeholders, where a file appears present but is not downloaded.
How to fix it, in order:
Close everything that might have it open, and restart if unsure.
Check the read-only attribute and the media's write-protect switch.
Take ownership and reset permissions through the file's security properties, applying to subfolders where needed.
Run the operation with elevation if it genuinely requires it.
Do not blanket-change permissions on system folders, which breaks things and weakens security.