> 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/troubleshooting/failed-to-open-device.md).

# Failed to open Device

## Problem

#### Issue with ARM-based Systems and KONNEKT Installation

If you notice the tray icon turning red and see log entries like the following, it indicates the issue:

<pre><code><strong>[error][Core_DriverControl] Failed to open Device "\.\konnektDevice"
</strong>[error] [Sharepoint] Failed to create registry key 'Site name': 0815
</code></pre>

The problem occurs on some devices that operate on ARM processors. When KONNEKT's x64 version is installed or deployed on such a system, the installation may succeed. However, KONNEKT will not work as expected.

## Solution

Install KONNEKT's ARM64 version.

{% 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/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.