> 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/ja/configuration/gui-behavior/change-konnekt-name-in-explorer.md).

# エクスプローラーで KONNEKT の名前を変更

次のレジストリ キーを編集することで、Windows エクスプローラーでの KONNEKT の名前を、File Server、SharePoint files、会社名などの任意の名前に変更できます。

### **キー パス**

次の 2 つのレジストリ キーの "(Default)" 値を変更する必要があります:

64 ビット アプリ用のキー:

```
Computer\HKEY_CLASSES_ROOT\CLSID\{6E619E0D-21EB-4471-A40B-040815C884EF}
```

32 ビット アプリ用のキー:

```
Computer\HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{6E619E0D-21EB-4471-A40B-040815C884EF}
```

"(Default)" の REG\_SZ の値を、好きな名前に変更します。既定では `KONNEKT`.

次の例では、これを次のように変更しました `SharePoint Data`

![](https://1902283602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8zLVuKYctMIUr68_fs%2Fuploads%2FjeWbpKcntDL0MihaVskd%2F2021-10-22%2012_50_06-Window.png?alt=media\&token=4143de67-600a-4655-97a0-b43db28759cc)

### **結果**

![](https://1902283602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8zLVuKYctMIUr68_fs%2Fuploads%2FePBICdpEfF50MU3cBtpV%2F2021-10-25%2011_07_36-Windows%20Sandbox.png?alt=media\&token=a7be7a7f-01f3-4510-add6-6d1dabcb5b00)


---

# 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/ja/configuration/gui-behavior/change-konnekt-name-in-explorer.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.