> For the complete documentation index, see [llms.txt](https://docs.gyroflow.xyz/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gyroflow.xyz/app/getting-started/troubleshooting.md).
# Troubleshooting
This page contains troubleshooting steps when you run into an error in Gyroflow.
## Failed to start on Windows
If you see the following message or similar mentioning `VCRUNTIME140.dll`, install [**VC redist**](https://aka.ms/vs/17/release/vc_redist.x64.exe)
## Failed to export HEVC
If you see an error message like this:
...then:
* If you're on Windows or Linux, make sure you're using the latest drivers for your GPU.
* If you're using an older GPU, it may not support hardware HEVC encoding, in which case, you should try H.264 instead.
* If H.264 also fails, try disable GPU encoding completely.
## Application failed to start
If you see an error message like this on Windows:
Please try downloading Gyroflow again. Everything you need is in the ZIP file that you download - you don't need to install any other dependancies manually.
## No space left on device
If you see an error message like this:
It means your hard drive doesn't have enough space for `ffmpeg` to render to. Please make some room and try again.
## Doesn't support this pixel format
If you see an popup like this:
It means your physical GPU hardware doesn't support the pixel format you're attempting to render to (i.e. normally it means your GPU hardware doesn't support 4:2:2 10-bit).
You can click **Render using CPU**, to render using the CPU instead of the GPU to maintain full quality, or you can pick another pixel format.
## Unknown Error Occurred
If you see an error message like this:
...then:
* If you're on Windows or Linux, make sure you're using the latest drivers for your GPU.
* If you're using an older GPU, it may not support hardware HEVC encoding, in which case, you should try H.264 instead.
* If H.264 also fails, try disable GPU encoding completely.
## Read Only File System
If you see an error message like this:
...and you're on Mac, make sure you install **Gyroflow** in your **Applications** folder and do NOT run it from the downloaded DMG package. Due to macOS sandboxing, Gyroflow isn't allowed to write to inside the package.
## Invalid data found when processing input
If you see an error message like this:
...and you're working with RED `R3D` files, try deleting the `MOV` file that Gyroflow created next to the `R3D` file, and try again.
##
---
# 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.gyroflow.xyz/app/getting-started/troubleshooting.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.
