> For the complete documentation index, see [llms.txt](https://wyvern-docs.gitbook.io/wyvern-gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wyvern-docs.gitbook.io/wyvern-gitbook/prerequisites/requirements-and-compatibility.md).

# Requirements and Compatibility

{% hint style="info" %}
Please note that sometimes, new Windows updates can cause Wyvern to break and emit some unexpected behaviour. In the event that this happens, please open a ticket on our [Discord](https://wyvern.cx/discord) server, and we'll be more than happy to help!
{% endhint %}

{% hint style="warning" %}
Please note that old Intel CPUs that are **"Pre Intel 4th-gen or Pre 2013"** have some issues and sadly won't be supported with Wyvern. If you have purchased a key and have an incompatible CPU, contact us on [Discord](https://wyvern.cx/discord) and we will issue you a refund no questions asked.
{% endhint %}

### Compatibility

* Supports Intel, AMD CPU/GPUs and Nvidia GPUs
* Supports all Windows 8.1, 10 and 11 versions/builds
* We do NOT offer official support for custom Windows ISOs but you may have luck with custom ISOs such as AtlasOS or ReviOS.


---

# 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://wyvern-docs.gitbook.io/wyvern-gitbook/prerequisites/requirements-and-compatibility.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.