0x00000492: Property Set Missing on This Object — Fix It Fast

What Causes 0x00000492?

You're seeing ERROR_SET_NOT_FOUND (0x00000492) because software asked Windows for a specific property set on a file or folder, and that property set isn't there. This usually happens when:

• A program (often a backup tool or file manager) expects metadata that got corrupted or deleted
• NTFS security descriptors or extended attributes are partially damaged
• An application wrote incomplete data during a crash or improper shutdown

I've seen this most often when running robocopy with the /COPYALL flag, or when using older backup software like Symantec Backup Exec on Windows 10/11. The fix isn't complicated — you just need to clean up the metadata layer.

1. Corrupted Metadata from a Previous Failed Operation

This is the #1 cause. When a file copy or backup gets interrupted, Windows can leave behind a broken property set entry. The system knows a property set should exist, but the data is corrupt.

Step-by-Step Fix: Clear the Corrupted Metadata

1. Open Command Prompt as Administrator. Press Win+X, then click Terminal (Admin) or Command Prompt (Admin). You'll see a User Account Control prompt — click Yes.
2. Type chkdsk /f X: where X: is the drive with the file. For example, chkdsk /f D:. Press Enter. After you press Enter, you'll see a message like: Chkdsk cannot run because the volume is in use. Would you like to schedule this volume to be checked the next time the system restarts? Type Y and press Enter. Then restart your PC. During boot, you'll see a blue screen with a percentage counter — let it finish. This can take 30+ minutes on large drives.
3. After the restart, open Command Prompt as Admin again (same as step 1).
4. Run fsutil repair query X: (replace X: with your drive letter). You'll see either Self-healing is enabled or Self-healing is disabled. If it's disabled, run fsutil repair set X: 1 to enable it. This flag tells Windows to fix metadata corruption on the fly.
5. Now try the operation that gave you the error. For example, if it was a robocopy command, run it again. The error should be gone. If it still shows up, move to the next fix.

What to expect: After chkdsk finishes its repair, you won't see any visual confirmation for the property set fix unless you check the Application Event Log (Event Viewer > Windows Logs > Application, look for Event ID 1001 from Wininit). But the error will stop appearing.

2. Permissions Misconfiguration — You Can't Read Properties You Don't Own

Sometimes the property set is there, but your user account doesn't have Read Attributes or Read Extended Attributes permission. This is common if the file was copied from a different system with a different security context.

Step-by-Step Fix: Take Ownership and Grant Full Control

1. Right-click the file or folder giving the error, choose Properties.
2. Click the Security tab. After a moment, you'll see a list of group/user names. If you see a warning like You must have Read permissions to view the properties of this object, you need to change ownership.
3. Click Advanced. A new window opens showing the current owner (usually TrustedInstaller or SYSTEM).
4. Next to Owner, click Change. In the Enter the object name to select box, type your username (e.g., yourname@yourdomain.com or just Administrator), then click Check Names. It should underline the name. Click OK.
5. Back in the Advanced Security Settings window, check Replace owner on subcontainers and objects. Then click Apply. You'll see a prompt: You do not have permission to read the contents of this folder. Do you want to replace the directory permissions with permissions granting you Full Control? Click Yes.
6. Wait for the progress bar to complete. For a folder with thousands of files, this can take a few minutes.
7. Once done, click OK to close all property windows. Try the operation again. If the error persists, move to the final fix.

3. Application-Specific Bug: The Software Is Asking for Something That Never Existed

Some programs (especially older ones from Windows 7 days) request a property set that Windows 10 and 11 don't support natively. For example, I've seen this with Adobe Drive and AutoDesk Vault when they try to read the OLE Property Set Storage on a file that never had it.

Step-by-Step Fix: Update or Patch the Software

1. Check the software vendor's website for any updates released in the last 2 years. If it's a legacy app, look for a Compatibility Update or a Hotfix.
2. If no update exists, right-click the program shortcut, select Properties, then the Compatibility tab. Check Run this program in compatibility mode for: and select Windows 7. Also check Run this program as an administrator. Click Apply, then OK.
3. If the error still happens, the real fix is to stop using that software version. I know that's not what you want to hear, but sometimes a app is just too old for modern Windows metadata handling.

Quick Reference Summary

Start with fix #1 — that clears about 80% of these errors. If not, go to #2. The compatibility workaround in #3 is your last resort, and it works about half the time for old software.