> 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/why-is-there-a-grey-x-on-my-files-and-folders.md).
# Why is there a grey "X" or "brown suitcase" on my files and folders?
KONNEKT users (Windows 10 or earlier) may see a grey "X" on file and folder icons in Windows File Explorer.
In Windows 11 it looks like
**This is not an Error or a Problem.** You can still work with your files without any restrictions.
This is a visualization in Windows Files Explorer of a setting that KONNEKT folders and files have, to save bandwidth.
**Background:**
The setting is called "FILE\_ATTRIBUTE\_OFFLINE". It indicates to the operating system, that this file or folder is not available immediately. As a result, Windows File Explorer does not generate previews for the files.
**Workaround:**
This symbol comes usually after a new installation, as a workaround, you can restart the Windows file explorer to remove it.
**We use this setting with KONNEKT files & folders to save bandwidth between the client and SharePoint Online.**
The visualization is not visible to every client.
See also: [Offline attribute](/configuration/system-settings/offline-attribute.md)
---
# 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/why-is-there-a-grey-x-on-my-files-and-folders.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.
