> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/es/troubleshooting/failed-to-open-device.md).

# No se pudo abrir el dispositivo

## Problema

#### Problema con sistemas basados en ARM y la instalación de KONNEKT

Si observa que el icono de la bandeja se vuelve rojo y ve entradas de registro como las siguientes, indica el problema:

<pre><code><strong>[error][Core_DriverControl] No se pudo abrir el dispositivo "\.\konnektDevice"
</strong>[error] [Sharepoint] No se pudo crear la clave del registro 'nombre del sitio': 0815
</code></pre>

El problema ocurre en algunos dispositivos que funcionan con procesadores ARM. Cuando se instala o despliega la versión x64 de KONNEKT en un sistema de este tipo, la instalación puede completarse correctamente. Sin embargo, KONNEKT no funcionará como se espera.

## Solución

Instale la versión ARM64 de KONNEKT.

{% embed url="<https://trial.konnekt.io/>" %}


---

# 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.konnekt.io/es/troubleshooting/failed-to-open-device.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.