> For the complete documentation index, see [llms.txt](https://docs.check.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.check.tech/troubleshooting/common-issues.md).

# Common Issues

<details>

<summary>Policies not appearing in Group Policy Management Console</summary>

* Verify that the ADMX/ADML files are in the correct location (see [Windows deployment docs](/deployment/chrome-edge-deployment-instructions/windows.md))
* Ensure that the files are not blocked (right-click > Properties > Unblock)
* Refresh Group Policy Editor

For complete deployment instructions, see [Domain Deployment guide](/deployment/chrome-edge-deployment-instructions/windows/domain-deployment.md).

</details>

<details>

<summary>Policies not applying to extension</summary>

* Check that the registry values are present (see [Manual Deployment guide](/deployment/chrome-edge-deployment-instructions/windows/manual-deployment.md))
* Restart the browser after policy changes
* Verify that the extension has the necessary permissions

For troubleshooting policy deployment, consult the [Windows deployment documentation](/deployment/chrome-edge-deployment-instructions/windows.md).

</details>

<details>

<summary>Custom branding not working</summary>

* Verify URLs are accessible via HTTPS
* Check that the image format is supported (PNG, JPG, or SVG)
* Ensure that color codes use a valid hexadecimal format

</details>


---

# 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.check.tech/troubleshooting/common-issues.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.