> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/troubleshoot/company/error-claim-ownership-failed-when-trying-to-recover-a-cloud-company.md).
# "Error - Claim Ownership Failed" when trying to recover a Patch My PC Cloud Company
*Applies to: Patch My PC Cloud*
### SYMPTOMS
I can no longer access my Patch My PC (PMPC) Cloud Company as the only admin has left and no other users have been created with the **Full Admin with Access Management** role.
I have tried running through the [Recover Your Company](/patch-my-pc-cloud/manage/settings/company-settings/recover-company.md) process, but after entering the requested information, I see the following:
**Error**
**Claim Ownership Failed**
### CAUSE
This error can occur for several reasons, such as:
1. You have entered invalid data to attempt the recovery.
2. You are trying to recover a PMPC Company from the wrong Entra ID tenant.
### RESOLUTION
To resolve this issue:
1. Verify you are entering the right values in the correct fields of the **Claim Ownership** wizard.
2. Verify that the last five characters shown for the company you are trying to recover match the last five characters of the Entra ID tenant (the **Directory (tenant) ID**).
{% hint style="warning" %}
**Important**
You only have three attempts to complete the **Claim Ownership** wizard. After the third failed attempt, you will see the following error:
**You've reached the maximum number of claim ownership attempts. Please try again later.**
You will be locked out and prevented from attempting the recovery for 12 hours.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.patchmypc.com/patch-my-pc-cloud/troubleshoot/company/error-claim-ownership-failed-when-trying-to-recover-a-cloud-company.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
