What does Windows error code 13025 (WARNING_IPSEC_QM_POLICY_PRUNED) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: the request failed while processing addition of an IPsec Quick Mode policy with unsupported.

Previous	Next
WARNING_IPSEC_MM_POLICY_PRUNED	ERROR_IPSEC_IKE_NEG_STATUS_BEGIN

WARNING_IPSEC_QM_POLICY_PRUNED

The Quick Mode policy was successfully added, but some of the requested offers are not supported.

Windows assigns decimal 13025 and hexadecimal 0x000032E1 to WARNING_IPSEC_QM_POLICY_PRUNED. The constant belongs to Windows IPsec, IKE, and AuthIP policy processing; its name is not enough to identify the affected directory object, DNS zone, policy, installer, package, or resource context.

Operational meaning

The key question is whether the effective Quick Mode offer set still contains acceptable data-protection algorithms and lifetimes. The value describes addition of an IPsec Quick Mode policy with unsupported offers removed; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Traffic can be protected successfully while the effective cryptographic choices differ from the requested policy. Record the scope that was actually tested instead of escalating from one rejected object or phase to a system-wide outage.

Where the result appears

This result can appear while processing addition of an IPsec Quick Mode policy with unsupported offers removed.
This result can appear while adding or validating Main Mode or Quick Mode policy offers.
This result can appear while classifying IKE negotiation status values returned by policy or VPN components.
It can appear while a firewall, VPN, or IPsec management tool that exposes Win32 policy status.

Typical causes

unsupported ESP or AH proposals were requested.
algorithm policy differs between systems.
invalid lifetime or PFS combinations are pruned.
an old template targets obsolete capabilities.

Diagnostic sequence

capture it immediately after the failing or status-returning call and record whether the API uses Win32, DNS_STATUS, HRESULT conversion, or callback semantics.
identify the exact target involved in addition of an IPsec Quick Mode policy with unsupported offers removed, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
prove the state boundary: the effective Quick Mode offer set still contains acceptable data-protection algorithms and lifetimes.
collect requested and effective Quick Mode offers and ESP/AH algorithms and lifetimes before restarting services, deleting objects, rebuilding packages, or changing policy.
correlate PFS settings with IKEEXT operational events, Windows Filtering Platform events, IPsec security audits, policy export, peer configuration, and packet capture.
determine whether the result is a failure, warning, informational completion, continuation request, or marker constant before choosing retry behavior.
after changing one responsible condition, repeat the same smallest operation and verify both success and absence of unintended partial effects.

Evidence to preserve

collect requested and effective Quick Mode offers.
collect ESP/AH algorithms and lifetimes.
collect PFS settings.
collect OS and provider capabilities.
collect test Security Association parameters.

Correlate this evidence with IKEEXT operational events, Windows Filtering Platform events, IPsec security audits, policy export, peer configuration, and packet capture. Preserve raw identifiers and the first detailed diagnostic: translating everything to 13025 can hide whether the cause was validation, topology, authorization, replication, policy, file I/O, packaging, or an intentional continuation state.

Recovery and retry

The recovery objective for it is to compare the installed offers with the intended security baseline and replace unsupported combinations; do not treat the warning as a complete rollback.

Retry only after the recorded boundary changes and prior completion is known. Read-only discovery for it can usually be repeated with bounded backoff; directory mutations, DNS updates, policy installation, servicing actions, and PRI writes require a state check first. Backoff for it cannot repair malformed input, unsupported structure, identity collision, missing authority, or incompatible package metadata.

Telemetry and support fields

record ipsec_qm_policy_pruned_operation — producing API, command, callback, or servicing phase.
record ipsec_qm_policy_pruned_target — stable object, zone, policy, package, file, or account identity.
record ipsec_qm_policy_pruned_state_before and ipsec_qm_policy_pruned_requested_state.
record ipsec_qm_policy_pruned_first_status — earliest component-specific code before translation.
record ipsec_qm_policy_pruned_server, ipsec_qm_policy_pruned_process, UTC timestamp, and correlation ID.

A support bundle for it should include decimal 13025, hexadecimal 0x000032E1, the smallest reproducible request, target identity, effective configuration, and evidence from the owning Windows component. When documenting it, remove secrets from exported logs but keep SIDs, GUIDs, package-family names, record types, and hashes when they are needed to distinguish objects.

Difference from nearby results

WARNING_IPSEC_MM_POLICY_PRUNED concerns Main Mode negotiation; this warning concerns traffic-protection offers after peer establishment This distinction determines whether the correct next step is input correction, topology repair, continuation, policy review, package rebuild, or no error handling at all.

Practical validation scenario

A template requests three Quick Mode suites, one unsupported. The remaining two install, and a test SA confirms which suite peers actually negotiate. A negative test should reproduce it with the responsible condition preserved; the recovery test should alter only that condition and confirm the intended final state.

Developer and administrator guidance

Developers should model it explicitly in the result domain instead of collapsing every nonzero value into “failed.” Administrators should capture evidence before destructive remediation and use the component that owns addition of an IPsec Quick Mode policy with unsupported offers removed. Monitoring for it should suppress range markers and classify warning, informational, cancellation, and continuation values separately from terminal failures.

References

Microsoft: exact Win32 system error range — official context relevant to it.
Microsoft: Audit IPsec Main Mode — official context relevant to it.
Microsoft: Windows Filtering Platform diagnostics — official context relevant to it.

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