| Previous | Next |
| QPLIST_E_EXPECTING_CLOSE_PAREN | QPLIST_E_BAD_GUID |
QPLIST_E_EXPECTING_GUID
A property-set GUID is missing
QPLIST_E_EXPECTING_GUID is HRESULT 0x80041658. Windows documents it as “Expecting GUID.”
Operation and state
This result belongs to legacy Windows property-list parsing and is returned while reading the namespace portion of a structured property specification. The exact condition is: the GUID field is empty, a friendly name is used, a macro expands to nothing or only the property ID is present.
This value belongs to the legacy property-list parser used to describe indexed properties and their types. Diagnose the external list as structured configuration: preserve line, column, token, type grammar and the property-list version instead of treating the file as arbitrary text. The exact public message comes from the legacy SDK contract; current property-system documentation does not replace the property-list grammar that rejected this file.
Failure paths to examine
Rejection of the property list does not yet distinguish file access, tokenization, type composition, GUID syntax or duplicate-definition failure.
Data to collect first
- Record raw specification before releasing the relevant objects.
- Associate expected property-set GUID with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for property ID under the same provider or handler version.
- Record the source and normalization path of macro expansion, not only its display form.
- Record property-list file identity and hash before releasing the relevant objects.
Hash the complete file if it is sensitive while retaining encoding, line, column, raw token class and the surrounding property declaration.
Step-by-step diagnosis
- Capture raw specification and expected property-set GUID at the call boundary that returns this result.
- Confirm the operation reached reading the namespace portion of a structured property specification with the intended property ID.
- resolve the property-set GUID and property ID as one authoritative schema pair.
Begin with a one-property list accepted by the same parser, then restore the failing declaration token by token while preserving encoding and line endings.
Continuation policy
Emit the exact GUID in the accepted form and round-trip it through a strict GUID parser. Delay cannot repair a deterministic file, token or type-grammar defect; retry only after the property list or its readable source changes.
Limits of this HRESULT
It does not prove that every property definition is unusable or that reindexing is required; it identifies a property-list read or grammar boundary.
Distinguishing similar results
QPLIST_E_BAD_GUID means a candidate GUID exists but is malformed.
Developer and administrator guidance
Operational case
A migration keeps the numeric property ID but loses the format GUID. Schema-backed conversion restores the complete identity pair.
Official Microsoft references
Looking for a different code? Search another status or error code.