Windows System Errors
Object Already Exists
0x80071392Reviewed for reference consistency: August 11, 2026
a creation request collided with an object using the same identity
What 0x80071392 Means
The 0x80071392 error on the Windows System Errors indicates object already exists — a creation request collided with an object using the same identity. This typically occurs due to a resource, group, or configuration object with the requested name is already registered.
Two objects cannot hold one identity, and a creation that tries anyway fails with 0x80071392, Win32 error 5010, ERROR_OBJECT_ALREADY_EXISTS — 'The object already exists'. The constant originates in the cluster resource API family — its message speaks of resources and groups — and servicing or management operations that register uniquely named objects trip it whenever identity is enforced.
How to fix 0x80071392
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Query the task store before recreating
Listing existing registrations under the name shows whether the collision is a completed earlier attempt that can simply be adopted.
Get-ScheduledTask | Where-Object TaskName -eq "<task-name>" | Select-Object TaskName, StateSearch the servicing log for the duplicate step
The servicing log records which operation attempted the registration; searching for the collision text locates the line.
findstr /C:"already exists" %windir%\Logs\CBS\CBS.log
Technical Background
Identity enforcement is the mechanism behind the code. Namespaced stores — the cluster configuration database, service and task registries, package registrations — keep unique keys, and a create operation is a claim on a key that has not been taken. The error means the claim collided, which is information about the store's current content, not about the caller's privileges or the object's validity.
Retries and races are the common stories. A partially completed operation that gets re-run hits its own earlier creation; two workers started simultaneously both attempt the same registration and one loses. Distinguishing the two is a matter of timing evidence: the race shows two creations seconds apart from different processes, while the retry usually shows the same process attempting twice after an interrupted first pass.
Common Causes
- A resource, group, or configuration object with the requested name is already registered
- A retry loop re-issued a creation that the first attempt had already completed
- Two concurrent operations raced to create the same uniquely named object
Typical Scenarios
- A failover-cluster operation creates a resource or group whose name is already registered in the cluster configuration
- An installation or provisioning step re-runs after a partial completion and re-creates an object the first pass registered
- Parallel automation tasks race to create the same uniquely named configuration object
What to Know
Before re-attempting any creation that returned this code, querying the store for the name tells you whether the existing object is your own earlier result — reuse it rather than recreate it.
Frequently Asked Questions
Common questions about Windows 0x80071392 error
WinError.h defines 5010 as ERROR_OBJECT_ALREADY_EXISTS in the cluster API range, with the plain message 'The object already exists'. Components outside clustering reuse the constant whenever a namespaced store enforces unique keys.
No. Access was sufficient to attempt the creation; the refusal is about the store's existing content. The same request with a different identity would succeed.
Error 32 (sharing violation) guards a file already in use, while 5010 guards a name already registered. Both are collision codes, but they enforce different kinds of exclusivity.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
You have unresolved file conflicts preventing Git from completing the current operation.
You tried to add a remote named 'origin', but one with that name already exists.
Git does not know which remote branch should receive your pushed commits.
You checked out a specific commit, detaching your working directory from the branch history.