Like any software, Yuzu isn’t flawless—issues may arise during use. Fortunately, most of these problems have known solutions. Below, you’ll find categorized tables explaining a range of error types, starting with the most frequent and moving through to rare and internal errors. For additional support, be sure to check out our FAQ and Troubleshooting sections.
What Are Error Codes?
Error codes are numeric or alphanumeric indicators that act as diagnostic references. They help developers identify what went wrong within the software. When users report these codes, it enables the developers to quickly trace the issue and work toward a resolution.
Key Error Codes
| Error Code | Description |
|---|---|
| 0008-000C | Indicates the Production Key File is not present. |
| 0008-000D | Signals that the Header Key is missing from the system. |
| 0008-000E | The Header Key in use is invalid or incorrect. |
| 0008-0011 | Points to a missing Title Key. |
| 0008-0012 | The system cannot find the Title Kek. |
| 0008-0014 | The KeyAreaKey is not available or missing. |
| 0008-0015 | An invalid or wrong Header Key has been used. |
| 0008-0016 | Suggests that either the TitleKey, TitleKek, or both are absent. |
| 0008-0018 | The system cannot locate the NCA (Nintendo Content Archive) file. |
Common Error Codes
| Error Code | Explanation |
|---|---|
| 0008-001C (ErrorNullFile) | This indicates the file you’re attempting to use is either corrupted, an incomplete copy, or completely empty. |
| 0008-001D (ErrorMissingNPDM) | The required main.npdm file is missing from the game directory. |
| 0008-001E (Error32BitISA) | The game you’re trying to launch uses a 32-bit instruction set architecture, which Yuzu currently does not support. |
| 0008-0029 (ErrorNAXInconvertibleToNCA) | This means the game you’re attempting to run uses a format or structure that Yuzu cannot interpret at this time. |
| 0008-002A (ErrorBadNAXFilePath) | You’re mistakenly trying to launch a save file as if it were a game file. |
| 0008-0039 (ErrorMissingBKTRBaseRomFS) | You’ve attempted to run a game update directly, which is not supported. To apply updates properly, use File > Install and select the update from the dialog. |
Corruption Error Codes
All the following error codes are typically linked to issues with your game dumps. These errors often stem from corrupted, incomplete, or improperly extracted game files. In many cases, re-dumping the game from the original source can resolve the issue.
| Error Code | Explanation |
|---|---|
| 0008-0004 (ErrorBadNPDMHeader) | The NPDM header in the file is corrupted or invalid. |
| 0008-0005 (ErrorBadACIDHeader) | The ACID header data is damaged or unreadable. |
| 0008-0006 (ErrorBadACIHeader) | The ACI header is malformed or incorrect. |
| 0008-0007 (ErrorBadFileAccessControl) | File access permissions are misconfigured or corrupted. |
| 0008-0008 (ErrorBadFileAccessHeader) | The file’s access header is either missing or unreadable. |
| 0008-0009 (ErrorBadPFSHeader) | The PFS (Partition File System) header is invalid or corrupted. |
| 0008-000A (ErrorIncorrectPFSFileSize) | The PFS file size is incorrect or inconsistent with expected values. |
| 0008-0013 (ErrorInvalidRightsID) | The Rights ID in the file is incorrect or has been tampered with. |
| 0008-0017 (ErrorXCIMissingProgramNCA) | Essential decryption keys are missing—try re-importing them. |
| 0008-0019 (ErrorNoExeFS) | The file is missing the ExeFS (Executable File System). |
| 0008-001A (ErrorBadXCIHeader) | The XCI header is corrupted or incorrectly formatted. |
| 0008-001B (ErrorXCIMissingPartition) | An expected partition is missing—often caused by a modified or incomplete XCI. |
| 0008-001F (ErrorNoRomFS) | The RomFS (Read-Only File System) section is missing from the dump. |
| 0008-0020 (ErrorIncorrectELFFileSize) | The ELF file size is incorrect or doesn’t match the header data. |
| 0008-0021 (ErrorLoadingNRO) | The system encountered an issue loading the NRO file. |
| 0008-0022 (ErrorNoIcon) | The game lacks icon data required for display in Yuzu. |
| 0008-0023 (ErrorNoControl) | Controller configuration data is missing or unreadable. |
| 0008-0024 (ErrorBadNAXHeader) | The NAX file contains a bad or invalid header. |
| 0008-0025 (ErrorIncorrectNAXFileSize) | The NAX file size doesn’t match the expected format. |
| 0008-0031 (ErrorNSPMissingProgramNCA) | The NSP package is missing the critical Program NCA file. |
| 0008-0032 (ErrorBadBKTRHeader) | The BKTR header is corrupted and needs to be corrected or removed. |
General Error Codes
These error codes are not typically encountered during regular gameplay. If you run into one, it’s likely due to custom modifications, experimental usage, or editing of emulator files or game dumps.
| Error Code | Explanation |
|---|---|
| 0008-000F (ErrorNCA2) | The NCA file you’re attempting to load has an unsupported or invalid format, which Yuzu cannot process. |
| 0008-0010 (ErrorNCA0) | Similar to ErrorNCA2, this indicates the NCA file structure is invalid—just flagged under a different code. |
More Key Error Codes
These error codes are uncommon and typically appear only when essential key derivation components are missing or incorrectly set up. If you encounter any of these, it usually means the decryption keys are incomplete or have not been properly configured.
| Error Code | Explanation |
|---|---|
| 0008-002B (ErrorMissingSDSeed) | The SD Seed is not present in your key setup. |
| 0008-002C (ErrorMissingSDKEKSource) | The SD KEK Source is missing from your configuration. |
| 0008-002D (ErrorMissingAESKEKGenerationSource) | The AES KEK Generation Source is missing and must be correctly supplied. |
| 0008-002E (ErrorMissingAESKeyGenerationSource) | The AES Key Generation Source is not found or improperly configured. |
| 0008-002F (ErrorMissingSDSaveKeySource) | The SD Save Key Source is missing or invalid. |
| 0008-0030 (ErrorMissingSDNCAKeySource) | The SD NCA Key Source is either incorrect, missing, or cannot be found. |
Internal Error Codes – Developer Reference Only
The following error codes were originally intended for use by the Yuzu development team. Since the project is no longer actively maintained, these codes are largely for archival or reference purposes. You are unlikely to encounter them during normal gameplay.
| Error Code | Description |
|---|---|
| 0008-0000 (Success) | Indicates the operation was completed successfully. |
| 0008-0001 (ErrorAlreadyLoaded) | The file or resource you’re attempting to load is already active in memory. |
| 0008-0002 (ErrorNotImplemented) | The feature or function you’re accessing is not yet fully implemented. |
| 0008-0003 (ErrorNotInitialized) | The operation failed because initialization was not completed. |
| 0008-0026 (ErrorNAXKeyHMACFailed) | The HMAC validation for the NAX key failed—potential integrity issue. |
| 0008-0027 (ErrorNAXValidationHMACFailed) | HMAC verification failed during NAX data validation. |
| 0008-0028 (ErrorNAXKeyDerivationFailed) | Deriving the NAX key failed—check configuration or data integrity. |
| 0008-0033 (ErrorBKTRSubsectionNotAfterRelocation) | A BKTR subsection was placed incorrectly in memory relative to its relocation block. |
| 0008-0034 (ErrorBKTRSubsectionNotAtEnd) | The BKTR subsection should be located at the end but isn’t. |
| 0008-0035 (ErrorBadRelocationBlock) | The relocation block is malformed or corrupted. |
| 0008-0036 (ErrorBadSubsectionBlock) | Indicates an invalid or improperly structured subsection block. |
| 0008-0037 (ErrorBadRelocationBuckets) | Relocation bucket data is invalid—consider using a different configuration. |
| 0008-0038 (ErrorBadSubsectionBuckets) | The subsection bucket structure is incorrect or unusable. |
Note: These error codes may no longer have practical use, but they remain part of Yuzu’s historical development records.