# How to Run Breath of the Wild Natively on Windows: BotW-Native Setup Guide > AI Release · @ai_release1 · https://ai-release.org/guides/kak-zapustit-the-legend-of-zelda-breath-of-the-wild-nat_en.html ## TL;DR - Time to complete: 45–60 minutes, excluding the time you need to produce your own game dump. - Difficulty: Intermediate - You need: a 64-bit Windows PC with a Vulkan-capable GPU and a current vendor driver, Git (or just a browser), the GitHub repository `ryderclanky/BotW-Native`, and your own legally owned Wii U dump of Breath of the Wild **v1.5.0**. The repository ships **no game assets**. - Terms used below: *static recompilation* means the game's original machine code is translated ahead of time into native Windows code, so no emulator interprets it while you play; *Vulkan* is a low-level graphics API that the project uses as its rendering backend. ## Requirements and setup ![Illustration: Requirements and setup](https://ai-release.org/guides/img/kak-zapustit-the-legend-of-zelda-breath-of-the-wild-nat-en-1.jpg?v=1792874982) - **OS:** 64-bit Windows. The post only states the project targets Windows; no minimum build number is published, so treat the exact Windows version as **check with the repository README**. - **GPU:** a graphics card whose driver exposes Vulkan. The renderer is a Vulkan backend, so an unsupported GPU is a hard stop. - **Driver rights:** administrator access to install/repair the GPU driver. - **Tooling:** PowerShell (built in), Git (or the "Download ZIP" button on GitHub), a text editor for the README. - **Game content:** a dump of the Wii U version of Breath of the Wild at version **1.5.0** that you produced yourself. Nothing is bundled. - **Disk space:** enough for the repository, the build output and your dump. The post gives no figure — measure your own dump with the command in Step 2 and keep at least that much free. | Component | Who supplies it | Where it goes | |---|---|---| | BotW-Native source and build | `ryderclanky/BotW-Native` on GitHub | your local clone or extracted release archive | | Vulkan renderer | part of the project | nothing extra to install, but the GPU driver must support Vulkan | | Game content files (v1.5.0) | you — from your own copy | the content folder named in the repository README (``) | If you first need a clean Windows install to start from, follow [How to Install Windows 11 26H2: Step-by-Step Guide with Official ISO](https://ai-release.org/guides/kak-ustanovit-windows-11-26h2-poshagovaya-instruktsiya.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide), then return here. ## Step 1. Confirm that Windows, the GPU and Vulkan are ready **What to do:** record your Windows build, GPU model and driver date, then confirm that a Vulkan loader and device are present. **Why:** the native build launches a Vulkan window almost immediately. If the loader (`vulkan-1.dll`) or a Vulkan-capable device is missing, the executable dies before it can read any game file, and you will waste time debugging the wrong layer. **How to check:** run the commands below and compare the values against the expectations listed after them. ```powershell Get-ComputerInfo | Select-Object WindowsProductName, OsVersion, OsArchitecture Get-CimInstance Win32_VideoController | Select-Object Name, DriverVersion, DriverDate ``` Example output on a working machine: ``` WindowsProductName OsVersion OsArchitecture ------------------ --------- -------------- Windows 11 Pro 10.0.xxxxx 64-bit Name DriverVersion DriverDate ---- ------------- ---------- NVIDIA GeForce RTX 3060 31.0.15.xxxxx 5/12/2024 12:00:00 AM ``` Then verify the Vulkan layer itself: ```powershell Get-ChildItem C:\Windows\System32\vulkan-1.dll | Select-Object Name, VersionInfo vulkaninfo --summary ``` `vulkan-1.dll` must exist, and `vulkaninfo --summary` must list at least one `GPU0` entry with a `deviceName` and an `apiVersion` reported by your driver. If `vulkaninfo` is not installed, install the vendor driver first and re-check the DLL; the loader ships with the driver, not with Windows. Write the reported `deviceName` down — it is the string you will look for when the game window opens. ## Step 2. Get the repository and place your own 1.5.0 content files ![Illustration: Step 2. Get the repository and place your own 1.5.0 content files](https://ai-release.org/guides/img/kak-zapustit-the-legend-of-zelda-breath-of-the-wild-nat-en-2.jpg?v=1792874988) **What to do:** clone the repository, read the README to learn the exact content-folder name and how the published build is distributed, then copy your own dump into that folder. **Why:** the repository contains source code and a build of the recompiled game logic only. Without content files the program has nothing to load, and the project expects a specific version — the post names **v1.5.0** — so an older or newer dump is not interchangeable. The recompiled code calls into fixed data layouts, which is why the version matters. **How to check:** the README is present, the executable of the build is present, and the content folder is non-empty. ```powershell cd C:\Games git clone https://github.com/ryderclanky/BotW-Native.git cd BotW-Native Get-ChildItem Get-Content README.md -TotalCount 80 ``` Expected: a README that describes the project as a static recompilation of the Wii U version of Breath of the Wild v1.5.0 into a native Windows program, with the Vulkan backend named. The folder listing shows the source tree and, for a published build, the packaged archive. Locate the runnable binary before you copy anything: ```powershell Get-ChildItem -Recurse -Include *.exe, *.zip, *.7z | Select-Object FullName, Length ``` Use that output to decide between extracting a release archive and building from source exactly as the README describes. If the README references a build system you do not have installed, follow its instructions rather than guessing — the post does not specify the toolchain. Then stage the content and measure it: ```powershell New-Item -ItemType Directory -Force -Path .\ # copy your own dumped files into .\ using Explorer or Copy-Item "{0:N2} GB" -f ((Get-ChildItem .\ -Recurse -File | Measure-Object Length -Sum).Sum / 1GB) ``` Checklist before you launch: - [ ] Repository cloned or release archive extracted to an ASCII-only path such as `C:\Games\BotW-Native` - [ ] README read, and the exact content-folder name confirmed from it - [ ] Your dump is verified as version **1.5.0** - [ ] Files copied into `` without renaming them - [ ] The size command above printed a non-zero value - [ ] No game files were taken from a source other than your own copy ## Step 3. First launch and verification ![Illustration: Step 3. First launch and verification](https://ai-release.org/guides/img/kak-zapustit-the-legend-of-zelda-breath-of-the-wild-nat-en-3.jpg?v=1792874997) **What to do:** start the binary from the repository root, keep a console window open if the build provides one, and confirm that the window is rendered by Vulkan on the expected GPU and that the game reaches its own menus. **Why:** the whole point of the project is that the game runs as a native Windows program — the recompiled code executes directly, with no emulator process translating instructions at runtime. Verifying that is your success criterion, not just "a window appeared". **How to check:** use the three checks below in order. ```powershell cd C:\Games\BotW-Native .\.exe ``` 1. **Process exists and no emulator is running.** In a second PowerShell window: ```powershell Get-Process | Where-Object { $_.ProcessName -match 'BotW' } | Select-Object ProcessName, Id, CPU ``` Expected: your BotW-Native process with a growing `CPU` value. You should not see a Wii U emulator in the list — if you do, you launched something else. 2. **The GPU is doing the work.** Open Task Manager → Performance → GPU. During the intro and the title screen the 3D engine should show load, and the adapter name should match the `deviceName` you recorded in Step 1. 3. **The game itself reached a known state.** Intro logos, then the title screen, then a loaded save or a new game. That confirms the content files were found and read at the expected version. If the build writes a log next to the executable, read it before reporting anything: ```powershell Get-ChildItem -Recurse -Filter *.log | Select-Object FullName, LastWriteTime Get-Content .\ -Tail 60 ``` Success looks like: window open, stable frame pacing on the title screen, GPU load on the correct adapter, no crash within the first few minutes of play. ## Troubleshooting **Problem. The executable does not start at all; a Windows dialog appears immediately.** - Error: `The code execution cannot proceed because vulkan-1.dll was not found. Reinstalling the program may fix this problem.` - Cause: the Vulkan loader is missing, which in practice means the GPU driver is absent, outdated, or installed without its Vulkan component. - Solution: install the current driver package from your GPU vendor, reboot, then confirm the loader exists: ```powershell Test-Path C:\Windows\System32\vulkan-1.dll ``` If this still returns `False`, the machine has no Vulkan-capable driver and the project cannot run on it. **Problem. The window opens and closes instantly, or the program reports that it cannot find its content.** - Error: a message of the form `Failed to open content file` or `content directory is empty` — the exact wording depends on the build, so **check the repository README** for the string it emits. - Cause: files were copied into a folder other than the one the build expects, were renamed, or the dump is not version 1.5.0. - Solution: re-read the `Get-Content README.md -TotalCount 80` output from Step 2, move the files into exactly that folder name, keep original filenames, and re-run the size command. Escaping the problem with a different dump version is not supported by the project. **Problem. The game starts, renders a frame or two, then crashes or freezes.** - Error: a Vulkan failure of the form `VK_ERROR_DEVICE_LOST`. - Cause: an unstable GPU driver state, aggressive overclocking, or the workload landing on an integrated adapter that only partially implements Vulkan. - Solution: do a clean reinstall of the vendor driver, disable GPU overclocking, and force the discrete GPU on the executable: Settings → System → Display → Graphics → Add desktop app → select `.exe` → Options → High performance. Then relaunch. ## Summary and next steps You now have Breath of the Wild v1.5.0 running as a native Windows program through the BotW-Native static recompilation, with rendering handled by its Vulkan backend and your own content files in place. If you enjoy getting console games to run natively rather than through emulation, the same mindset applies in [How to Run Metal Gear Solid 2 HD and Other NVIDIA SHIELD Ports on Android](https://ai-release.org/guides/kak-zapustit-metal-gear-solid-2-hd-i-drugie-porty-nvidi.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide). ## FAQ **Does BotW-Native include the game?** No. The repository ships code and a build; the post states explicitly that there are no game assets in the distribution and that you must supply the game files yourself from a copy you own. **Which version of the game do I need?** Version 1.5.0 of the Wii U release — that is the version the recompilation targets. **Do I need an emulator to run it?** No. This is a static recompilation: the Wii U code is translated into a native Windows program ahead of time, so nothing emulates instructions while you play. **What GPU do I need, and what performance should I expect?** Any GPU whose driver exposes a working Vulkan device; the Vulkan loader and device list from Step 1 are the concrete test. The source post publishes no benchmark figures, so measure frame rate on your own hardware instead of relying on quoted numbers.