| Previous | Next |
| WCM_E_INVALIDATTRIBUTECOMBINATION | WCM_E_MISSINGCONFIGURATION |
WCM_E_ABORTOPERATION
WCM_E_ABORTOPERATION is the failure HRESULT 0x80220028 (signed decimal -2145255384, unsigned decimal 2149711912). Its severity bit is 1, facility is 34 (FACILITY_STATE_MANAGEMENT), and the facility-specific code field is 0x0028.
AllStat records the Windows SDK description as “Current operation should be aborted”
Exact meaning and contract boundary
The current SMI operation must be abandoned. The operation reached multi-step processing where a result object or state-engine decision declares that continuing is unsafe or invalid. The first branch to test is whether a prior validation result makes later application meaningless; keep that separate from the possibility that the state engine detects an unrecoverable condition within the current batch.
Where the result appears
At this boundary, capture the earliest preceding error or warning in the result array, then correlate it with operation phase and last successfully processed namespace/item. Assign ownership only after checking whether any changes were staged versus persisted.
Likely cause branches
- a prior validation result makes later application meaningless
- the state engine detects an unrecoverable condition within the current batch
- a handler requests termination to prevent partial configuration
- the operation context has been invalidated by target/store changes
Evidence that resolves the ambiguity
- the earliest preceding error or warning in the result array
- operation phase and last successfully processed namespace/item
- whether any changes were staged versus persisted
- handler and target information
- rollback/cleanup outcome before a new attempt
Diagnostic sequence
- stop processing immediately
- collect every result object before releasing the context
- roll back or discard staged changes through the owning API contract
- recreate the operation after correcting the initiating condition
- do not skip the item and continue unless Microsoft explicitly documents that behavior for the caller
Retry and recovery
A new attempt is safe only after cleanup and root-cause correction. Continuing the same operation contradicts the HRESULT’s contract.
Difference from nearby WCM results
WCM_E_INTERNALERROR gives an unspecific engine failure; ABORTOPERATION specifically communicates required control flow to the caller.
Practical scenario
A batch deserialization reports a fatal namespace problem followed by this result. The deployment tool must abandon the batch instead of applying later fragments.
Logging and engineering guidance
For operational telemetry, retain whether any changes were staged versus persisted; also record handler and target information. Preserve a redacted summary of rollback/cleanup outcome before a new attempt; use a cryptographic hash when that evidence is a file, stream, or generated artifact.
Official Microsoft references.
- Microsoft: SMI error and success constants.
- Microsoft: Settings Management Infrastructure API.
- Microsoft: SMI interfaces.
- Microsoft: ISettingsResult::GetErrorCode.
- Microsoft: ISettingsResult::GetLine.
Looking for a different code? Search another status or error code.