What does HRESULT 0xC0090001 (ERROR_AUDITING_DISABLED) mean?

 
Previous Next
SL_E_TAMPER_RECOVERY_REQUIRES_ACTIVATION ERROR_ALL_SIDS_FILTERED

ERROR_AUDITING_DISABLED

Investigate security event not covered by current audit policy at the first returning call, before a wrapper substitutes a generic message. The caller requested or expected auditing for an event category that is not enabled in the effective audit policy.

The contract boundary

The declared return type and source header determine the relevant status namespace.

An audit-disabled result is not evidence that the protected operation itself failed; it says the requested audit record is not currently produced. Keep the numeric value, declared return type, and first returning operation together with ERROR_AUDITING_DISABLED; the same integer can belong to a different status namespace in another API.

Capture before changing state

CaptureDiagnostic value
Audit subcategory GUID/name, effective policy, local/domain policy source, event producer, and caller token.Identifies the concrete object and operation associated with security event not covered by current audit policy.
Auditpol output and the expected Security log event ID before changing policy.Separates argument or lifecycle state from a lower-layer provider failure.
First security/authorization event and the exact API returning the HRESULT.Creates a stable before-and-after comparison.
Effective identity and policy version at the time of the call.Shows whether this condition is the first result or a translated summary.

For ERROR_AUDITING_DISABLED preserve effective identity and policy version at the time of the call while evaluating this condition before reinstalling, rebooting, clearing state, or substituting another device or provider. A success observed only after such a change is useful comparison data for ERROR_AUDITING_DISABLED but it does not identify the original cause.

Focused experiments

  1. Enable only the relevant subcategory in a controlled policy scope. Repeat the original supported operation so the check remains tied to the same API boundary.
  2. Generate one known test event and confirm both success/failure settings. Keep unrelated inputs fixed so the changed result remains attributable to the tested variable.
  3. Repeat after one policy refresh without changing the resource ACL or application data. Record the first returned status and any state transition observed.

Adjacent outcomes

Observed comparisonNext conclusion to test
The first control changes the resultConcentrate on the variable isolated by this check: Enable only the relevant subcategory in a controlled policy scope.
The second comparison reproduces the same first statusPreserve lower-layer provider, driver, service, or runtime evidence before editing application data. The second controlled check was: Generate one known test event and confirm both success/failure settings.
A different status appears after the bounded changeThe operation moved to another boundary after the third controlled check. That check was: Repeat after one policy refresh without changing the resource ACL or application data. Retain both results and interpret the replacement through its own API contract.

A defensible resolution

Targeted correction. Enable the required audit subcategory through the authoritative policy source and document log volume/retention impact. For ERROR_AUDITING_DISABLED modify only the object, argument, policy, provider, or lifecycle state identified by the collected evidence.

Acceptance criterion. The controlled event creates the expected record and policy refresh does not revert the setting. Re-run the original operation that produced ERROR_AUDITING_DISABLED under its original identity and supported configuration, then keep one negative control that still produces the expected neighboring outcome.

Technical references

References for ERROR_AUDITING_DISABLED on the deployed platform version.


Looking for a different code? Search another status or error code.