| Previous | Next |
| ERROR_SET_CONTEXT_DENIED | RPC_S_INVALID_STRING_BINDING |
ERROR_CROSS_PARTITION_VIOLATION
The operation crossed a private partition boundary that Windows enforces.
ERROR_CROSS_PARTITION_VIOLATION is Win32 error 1661 (0x67D). Modern Windows can isolate processes and resources in partitions used by containers, silos, application environments, and other virtualization boundaries. A private file or section object created for one partition cannot be accessed as though it belonged to another. The error is about isolation context, not an ordinary path typo.
Situations that can cross the boundary
- a host process passes a private section or file handle into a containerized process
- a broker caches a handle and later reuses it for a client in another partition
- shared-memory IPC is created in the wrong namespace or by the wrong service instance
- a process moves or restarts under a different isolation context while retaining stale identifiers
- software assumes host and container file views refer to the same private backing object
Isolation evidence to record
Capture caller and target process IDs, container or silo identity, partition identifiers available to the platform component, object type, creating process, handle-duplication path, namespace name, file or section backing path, access rights, and lifecycle timestamps. Do not expose container secrets or tenant identifiers in cross-tenant logs; use stable redacted correlation IDs.
How to find the boundary error
Trace object creation and every duplication or IPC transfer. Determine which process created the file or section and which partition owned it at that moment. Validate that the receiving process is still in the same isolation context. A numerically valid handle duplicated through an unsupported broker can still designate an object that policy forbids the receiver from using.
Review container runtime, service-hosting, and update changes that alter partition placement. Reproduce with a minimal object created entirely inside the target partition, then compare with host-created state. If ordinary shared data is required, use the runtime’s supported volume, named-pipe, socket, or mapped-directory mechanism instead of a private cross-partition section.
Correct architecture
Create partition-private resources within the partition that consumes them, or move cross-boundary exchange through an approved broker that copies data rather than leaking private handles. Close cached handles when clients restart or move between partitions. Retries with the same object cannot change its ownership context.
Platform code should include partition identity in cache keys and validate it before handle reuse. Integration tests should cover host-to-container, container-to-container, restart, upgrade, and concurrent tenant scenarios.
Difference from access denied
ERROR_ACCESS_DENIED is a broad authorization result. Error 1661 specifically identifies an invalid cross-partition private file or section access. Granting a wider ACL does not make an object portable across an isolation boundary.
Example
A diagnostics broker creates a memory section on the host and duplicates it to two containerized workers. One receives 1661 because the section is private to the host partition. Replacing the mapping with an authenticated broker protocol that copies bounded records preserves isolation and fixes the design.
References
- Microsoft: System Error Codes (1300–1699)
- Microsoft: Windows container isolation modes
- Microsoft: Troubleshoot Windows containers
Looking for a different code? Search another status or error code.