> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/da/knowledge-base/troubleshooting-articles/requested-operation-cannot-be-completed.md).

# Den anmodede handling kan ikke fuldføres

Ret delegeringsfejlen requested operation cannot be completed i Remote Desktop Manager Windows ved at sætte Registry-værdien ProtectionPolicy til 1.

Remote Desktop Manager Windows kan fryse, vise en fejlmeddelelse eller gå ned uventet. Følgende fejl vises:

"The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation".

### Løsning

Rediger ***Registry-editoren*** for at tillade den lokale sikkerhedskopi af hovednøglen uden at kræve en domænecontroller med læse- og skriveadgang (RWDC). Følg disse trin:

1. Åbn ***Registry-editoren***, og gå til følgende nøgle:

   `HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb`
2. Højreklik på nøglen, og opret en ny DWORD-værdi (32-bit) med navnet `ProtectionPolicy`.
3. Sæt værdien af `ProtectionPolicy` til ***1***.

Denne ændring bør løse problemet med det samme og kræver ikke, at Remote Desktop Manager genstartes.


---

# 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.devolutions.net/rdm/da/knowledge-base/troubleshooting-articles/requested-operation-cannot-be-completed.md?ask=<question>&goal=<user_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.