ERROR_SET_NOT_FOUND - 1170 (0x492)

The property set specified does not exist on the object.

Updated: Feb 21, 2026

Technical Background

The ERROR_SET_NOT_FOUND error code is a specific error that indicates an issue with the property set specified for an object. This error typically arises when a requested operation involves a property set that does not exist on the target object.

Error Details

  • Error Name: ERROR_SET_NOT_FOUND
  • Numeric Code: 1170 (0x492)
  • Short Description: The property set specified does not exist on the object.

This error suggests that a property set identifier was provided in an operation, but it is not recognized by the system for the specific object being manipulated. Property sets are collections of properties associated with objects and can be used to retrieve or modify multiple related attributes at once.

Common Causes

  • Invalid Parameter Values: The specified property set ID may be incorrect or invalid.
  • Incorrect Object Type: The operation might be attempting to apply a property set that is not supported by the object type.
  • Exceeding Limits: There could be limitations on the number of property sets an object can have, which are being exceeded.

Real-World Context

This error commonly occurs in scenarios where applications attempt to modify or retrieve properties using a specific identifier that does not match any existing property set for the target object. For example, when working with registry keys, files, or other system objects, certain operations might require a valid property set ID.

Is This Error Critical?

The criticality of this error depends on the context in which it occurs. If the operation is non-critical and can be retried with correct parameters, the impact may be minimal. However, if the operation is part of a larger process or system that relies on specific property sets, the error could indicate a more significant issue.

How to Diagnose

  1. Review Operation Context: Ensure that the object being manipulated and the property set ID are correctly identified.
  2. Validate Parameters: Double-check the parameters passed to the operation to ensure they are valid and appropriate for the target object.
  3. Confirm Object Types: Verify that the object type supports the property sets being used in the operation.
  4. Verify Input Data: Ensure that all input data, including property set IDs, is correct and up-to-date.

How to Resolve

  1. Correct Parameter Usage: Use a valid property set ID for the target object.
  2. Adjust Operation Context: If the operation context is incorrect, adjust it to match the requirements of the target object.
  3. Restore Data: If data corruption or invalidation is suspected, restore the correct state of the object and its properties.
  4. Retry Operation with Valid Inputs: After verifying parameters and input data, retry the operation.

Developer Notes

Developers should ensure that all property set IDs used in their applications are valid and appropriate for the target objects. Additionally, they should handle errors gracefully to provide meaningful feedback to users or other components of the system.

Related Errors

  • ERROR_INVALID_PARAMETER: Occurs when a parameter passed to an operation is invalid.
  • ERROR_OBJECT_NAME_NOT_FOUND: Indicates that the object name specified does not exist.
  • ERROR_BAD_PROPERTY_SET_ID: May occur if the property set ID provided is incorrect or unsupported.

FAQ

Q: What causes ERROR_SET_NOT_FOUND?

A: This error typically occurs when a property set identifier is invalid for the target object. Common causes include incorrect parameter values, incorrect object types, and exceeding limits on the number of supported property sets.

Q: How can I prevent this error from occurring?

A: Ensure that all parameters are valid and appropriate for the target object. Verify that the operation context matches the requirements of the object type and that any required property sets are correctly identified.

Summary

The ERROR_SET_NOT_FOUND error code indicates that a specified property set does not exist on the target object. This can occur due to various reasons, such as invalid parameter values or incorrect object types. By carefully validating parameters and ensuring correct operation context, developers can prevent this error from occurring and handle it effectively when it does arise.