sodcalculator

10 Tech How-To

Fix Unable to Display Current Owner in Windows

Guide 10-47809 · Updated · Step by step

If Windows shows “Unable to display current owner” when you open a file or folder’s Security or Sharing tab, the fix is usually to reset the object’s owner to your account or to the Administrators group using the Advanced Security Settings dialog or the takeown command. This error appears when the current owner SID (security identifier) no longer matches any account on your system, often after a Windows reinstall, a domain account removal, or restoring files from another computer. Below is a step-by-step guide to resolve it, plus background on why it happens and what to do when the standard fix doesn’t work.

Why Windows Says “Unable to Display Current Owner”

The owner of a file or folder is the account or group that controls permissions for that object. Windows stores the owner as a security identifier (SID), not as a readable name. When you open the Security tab, Windows tries to translate that SID into an account name. If the SID belongs to a user or group that no longer exists on your PC — for example, a deleted local account, a former domain account, or a user from a previous Windows installation — the translation fails and you see “Unable to display current owner.”

This is not a sign of corruption or a virus; it’s simply a broken reference. The object still has an owner, but Windows can’t tell you who it is because the account is gone. The same issue can occur with files copied from a different computer or from a backup, where the original user’s SID doesn’t exist on your current system.

How to Fix It Using the GUI (Graphical Interface)

The most direct way is to change the owner through the Advanced Security Settings window. Here are the steps for Windows 10 and Windows 11:

  1. Right-click the file or folder and select Properties.
  2. Go to the Security tab and click Advanced at the bottom.
  3. At the top of the Advanced Security Settings window, you’ll see the current owner (or the error message). Click Change next to it.
  4. In the “Select User or Group” dialog, type your username (or Administrators) and click Check Names, then OK.
  5. If you want to replace the owner on all child objects (subfolders and files), check the box that says Replace owner on subcontainers and objects.
  6. Click OK and then Yes if prompted about permissions.

After this, the Security tab should display your account as the owner. If you also see a message about permissions, you may need to take ownership and then reapply permissions.

Using the Command Line: takeown and icacls

If the GUI fails (for example, you get an access denied error), the command line is more powerful. Open Command Prompt or PowerShell as Administrator and use the takeown command to take ownership, then icacls to grant yourself full control.

takeown /f "C:\path\to\folder" /r /d y
icacls "C:\path\to\folder" /grant "%USERNAME%":(OI)(CI)F /T

Explanation of flags:

  • /f specifies the file or folder path.
  • /r applies recursively to all subfolders and files.
  • /d y answers “Yes” to the prompt about non-admin users (defaults to yes).
  • icacls with /grant gives your user account full control (F) with inheritance (OI and CI).
  • /T applies to all child items.

This method is especially useful when you can’t even open the Security tab due to the error. After running these commands, the owner will be your account and you’ll have full access.

What If You Still See the Error?

Sometimes the error persists because the object’s owner SID is not recognized even after you change it. This can happen if the file is on a network share or an external drive that doesn’t support Windows ACLs (like a FAT32 drive). For FAT32 or exFAT drives, there is no owner concept, and Windows may show this error because the file system doesn’t store ownership information. In that case, the only solution is to copy the files to an NTFS drive or format the drive to NTFS (which will erase data).

Another possibility is that the file is locked by a system process or is a system file. For system files (like in C:\Windows), you should not change ownership unless you know what you’re doing. If you’re trying to take ownership of a system file to modify it, be aware that this can cause instability.

If you still see the error after changing the owner, try restarting Windows Explorer (in Task Manager) or rebooting the computer. Sometimes the security descriptor cache needs a refresh.

Common Mistakes to Avoid

  • Using the wrong account name: If you’re not sure of your exact username, type Administrators instead — that group always exists on Windows.
  • Not applying to subfolders: If you only change the owner on the top folder, subfolders may still show the error. Always check the “Replace owner on subcontainers and objects” box.
  • Ignoring the permission prompt: After changing the owner, you may need to also grant yourself permissions. The owner doesn’t automatically get full control if the existing permissions deny it.
  • Using the wrong command prompt: Both takeown and icacls require an elevated (Administrator) prompt. If you run them in a normal prompt, you’ll get access denied.

How to Prevent This in the Future

This error is most common after migrating data from an old computer or from a backup. To avoid it, always use the Windows “Backup and Restore” or “File History” tools, which preserve ownership correctly when restoring. If you copy files manually, consider using the robocopy command with the /COPYALL flag, which copies all security information including owner.

If you’re moving files to a new computer, you can also use the “Windows Easy Transfer” (though deprecated) or simply re-apply ownership after the move. It’s also a good idea to keep your user account name the same on the new machine, but that doesn’t guarantee the SID will match.

Frequently Asked Questions

Why does the owner show as “S-1-5-21-…” instead of a name?

That’s a raw SID. It means Windows couldn’t translate the SID to a name because the account is missing. The fix is the same as described above — change the owner to a valid account.

Can I delete a file that shows this error?

Yes, if you have permission. If you can’t delete it, take ownership first using the steps above, then grant yourself full control and delete. If the file is in use, close any programs using it first.

Does this error affect my computer’s security?

No, it’s just a display issue. The file still has an owner, but the name can’t be resolved. It doesn’t mean the file is unprotected or that your system is compromised.

Will changing the owner break anything?

Changing the owner on your own files is safe. However, changing the owner of system files (like in C:\Windows) can cause problems if you don’t restore the original owner. Only change ownership when necessary.

What if I get “Access Denied” when trying to change the owner?

You must be logged in as an administrator. If you are, try using the command line method with takeown and icacls. If that still fails, the file may be protected by TrustedInstaller — you’ll need to take ownership from TrustedInstaller first, which is more advanced.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →