# Page Not Found

The URL `files/rmX5owG96WHx7DwBJX0q` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Traffic Drops After Windows Update](https://docs.ndi.video/all/faq/common-issues/traffic-drops-after-windows-update.md)
- [I haven't received the email with the download.](https://docs.ndi.video/all/faq/sdk/i-havent-received-the-email-with-the-download..md)
- [I'm having issues with Final Cut Pro](https://docs.ndi.video/all/faq/common-issues/im-having-issues-with-final-cut-pro.md)
- [Will my existing HX-upgraded camera be affected?](https://docs.ndi.video/all/faq/ndi-hx-license-upgrades/will-my-existing-hx-upgraded-camera-be-affected.md)
- [What is happening with NDI HX Upgrades?](https://docs.ndi.video/all/faq/ndi-hx-license-upgrades/what-is-happening-with-ndi-hx-upgrades.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.ndi.video/all/faq/common-issues/traffic-drops-after-windows-update.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.ndi.video/all/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.ndi.video/all/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/all/faq/common-issues/traffic-drops-after-windows-update.md`).

You may also use `Accept: text/markdown` header for content negotiation.