XDAY RESEARCH
Vanguard error reference: 47 official documents classified [2026]
A VAN error alone does not prove a ban or a hardware failure. Match the complete code and the game before choosing the official guidance.
Classification
These are XDAY editorial categories, not Riot’s official categories or an error-frequency ranking. When a document describes both startup and connection issues, it remains in the combined category.
| XDAY category | Document count | Where to start |
|---|---|---|
| Startup, initialization and services | 11 | Check the full code and the matching official startup/service instructions. |
| Combined startup and connection | 11 | Keep both startup and connection possibilities; follow the exact code article. |
| Connection and session | 2 | Check the session and connection guidance for the exact code. |
| Windows, security and trust | 15 | Check Windows and required security features against Riot and manufacturer guidance, without changing BIOS settings blindly. |
| Unsupported environment | 3 | Confirm that the game and environment meet the specific official requirements. |
| Driver and software compatibility | 3 | Record the named driver or software and follow the official compatibility guidance. |
| Installation location | 1 | Compare the installation location with the official requirements. |
| HWID restriction | 1 | Read the restriction notice and Riot support guidance; do not infer a remedy from unrelated connection errors. |
Keep VAL and VAN separate
Copy the prefix, minus sign and full RESTRICTION suffix. This review excludes VAL codes. Riot describes VAN 152 as an HWID-ban-related restriction; that does not mean a restart or reinstall removes it, or that other VAN codes represent the same restriction.
Do not apply one BIOS or security-setting change to every error. Follow the matching Riot article and manufacturer guidance. This review did not execute or test those procedures.
All 47 sources
At observation time, all 47 linked pages returned HTTP 200 and an article heading. A successful response does not establish complete Japanese translation or applicability to your PC. This table works without JavaScript.
| Code label | XDAY category | Game and scope | Primary source |
|---|---|---|---|
| VAN: RESTRICTION | Windows, security and trust | Check the game and conditions in the linked article | VAN: RESTRICTION |
| VAN: RESTRICTION: 1 | Windows, security and trust | Check the game and conditions in the linked article | VAN: RESTRICTION: 1 |
| VAN: RESTRICTION: 3 | Installation location | Check the game and conditions in the linked article | VAN: RESTRICTION: 3 |
| VAN: RESTRICTION: 4 | Windows, security and trust | Check the game and conditions in the linked article | VAN: RESTRICTION: 4 |
| VAN: RESTRICTION: 5 | Windows, security and trust | Check the game and conditions in the linked article | VAN: RESTRICTION: 5 |
| VAN: Incompatible Software | Driver and software compatibility | Check the game and conditions in the linked article | VAN: Incompatible Software |
| VAN: STATUS_VMD_9001 | Driver and software compatibility | Check the game and conditions in the linked article | VAN: STATUS_VMD_9001 |
| VAN: Incompatible OEM driver | Driver and software compatibility | Check the game and conditions in the linked article | VAN: Incompatible OEM driver |
| VAN: STATUS_SB_POLICY | Windows, security and trust | Check the game and conditions in the linked article | VAN: STATUS_SB_POLICY |
| VAN Missing -117 | Startup, initialization and services | Check the game and conditions in the linked article | VAN Missing -117 |
| VAN -104 | Combined startup and connection | Check the game and conditions in the linked article | VAN -104 |
| VAN -102 | Combined startup and connection | Check the game and conditions in the linked article | VAN -102 |
| VAN -101 | Unsupported environment | The article explicitly refers to League of Legends system requirements | VAN -101 |
| VAN -92 | Combined startup and connection | Check the game and conditions in the linked article | VAN -92 |
| VAN -83 | Combined startup and connection | Check the game and conditions in the linked article | VAN -83 |
| VAN -81 | Combined startup and connection | Check the game and conditions in the linked article | VAN -81 |
| VAN -79 | Combined startup and connection | Check the game and conditions in the linked article | VAN -79 |
| VAN -72 | Combined startup and connection | Check the game and conditions in the linked article | VAN -72 |
| VAN -1 | Startup, initialization and services | Check the game and conditions in the linked article | VAN -1 |
| VAN 0 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 0 |
| VAN 6 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 6 |
| VAN 25 | Windows, security and trust | Check the game and conditions in the linked article | VAN 25 |
| VAN 57 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 57 |
| VAN 59 | Combined startup and connection | Check the game and conditions in the linked article | VAN 59 |
| VAN 68 | Connection and session | Check the game and conditions in the linked article | VAN 68 |
| VAN 84 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 84 |
| VAN 128 | Windows, security and trust | Check the game and conditions in the linked article | VAN 128 |
| VAN 133 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 133 |
| VAN 135 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 135 |
| VAN 138 | Unsupported environment | Check the game and conditions in the linked article | VAN 138 |
| VAN 140 | Combined startup and connection | Check the game and conditions in the linked article | VAN 140 |
| VAN 148 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 148 |
| VAN 152 | HWID restriction | Check the game and conditions in the linked article | VAN 152 |
| VAN 185 | Connection and session | Check the game and conditions in the linked article | VAN 185 |
| VAN 193 | Combined startup and connection | Check the game and conditions in the linked article | VAN 193 |
| VAN 1067 | Combined startup and connection | Check the game and conditions in the linked article | VAN 1067 |
| VAN 2266 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 2266 |
| VAN 9001 | Windows, security and trust | Check the game and conditions in the linked article | VAN 9001 |
| VAN 9002 | Windows, security and trust | Check the game and conditions in the linked article | VAN 9002 |
| VAN 9003 | Windows, security and trust | Check the game and conditions in the linked article | VAN 9003 |
| VAN 9004 | Windows, security and trust | Check the game and conditions in the linked article | VAN 9004 |
| VAN 9005 | Windows, security and trust | Check the game and conditions in the linked article | VAN 9005 |
| VAN 9006 | Windows, security and trust | Check the game and conditions in the linked article | VAN 9006 |
| VAN 9051 | Startup, initialization and services | Check the game and conditions in the linked article | VAN 9051 |
| VAN 9090 | Windows, security and trust | Check the game and conditions in the linked article | VAN 9090 |
| VAN 9100 | Unsupported environment | Check the game and conditions in the linked article | VAN 9100 |
| VAN 9101 | Windows, security and trust | Check the game and conditions in the linked article | VAN 9101 |
Method and limitations
Population: article links in the five content groups of Riot’s Japanese Vanguard error index. Unit: one unique article URL. Navigation links, related articles, VAL codes and pages absent from the index were excluded. Observation: 11 November 2026, 00:10 JST (10 November, 15:10 UTC). Saved HTML, SHA-256 hashes, responses and headings were checked. One primary category was assigned from the official explanation, retaining combined cases.
Riot Games: Vanguard error codes (Japanese index)
Counts describe indexed documentation, not users, incidence, ban rate, cause probability or repair success. This is not a claim to enumerate every VAN code. The source documents are authored by Riot Games. XDAY performed this independent classification and is not an official or endorsed Riot research organization.
Updates and citation
11 November 2026: initial baseline. No historical change or trend has been measured. Future comparable observations should separate additions, removals and heading/content changes. Changing only the year does not constitute a new study.
Suggested citation: “XDAY’s 2026 Vanguard Documentation Review classified 47 documents from Riot’s Japanese index into eight categories (observed 11 November 2026).” Cite this review and the primary source.