R1152-TAD-W79J:10001

Briefing:

You try to connect to a multiplayer session but are unable to do so. The error "R1152-TAD-W79J:10001" is cited.

Likely Cause:

Firewall rules, IPv6 routing, or VPN status.

Prerequisite:

Check if the servers are actually down.

Before troubleshooting your own network, check the official Monster Hunter status account at @MHStatusUpdates. If they are reporting a widespread outage or maintenance, the issue is on Capcom's end and no local fix will work. Wait for the servers to come back online.

General Fixes (try in order):

1. Allow the game through your firewall, along with its inbound rules.

A frequently reported solution. A device's firewall may prevent it from establishing a connection with the game's servers.

First, verify which network profile you're currently using:

• Press Win + I, and in the left sidebar navigate to Network & Internet.
• Click your current connection type (Wi-Fi or Ethernet). If the dropdown menu is closed, open it. Memorize your "Network profile type". It will be either "Private" or "Public".

• Press the Windows key to bring up your search bar, search for "Allow an App through Windows Firewall" and click it
• If the settings are greyed out, click "Change Settings"
• Click "Allow another app", then "Browse"
• Find the game's executable file. It is usually located in "This PC\Local Disk (C):\Program Files (x86)\Steam\steamapps\common\MonsterHunterWilds"
• Add "MonsterHunterWilds.exe" to the list
• Click "Network types..." and ensure your current network profile type is checked

Note: If you are using a third-party firewall, find its documentation to learn how to allow an app through it.

Allowing the game's inbound rules:

• Press the Windows key to bring up your search bar, search for "Windows Defender Firewall with Advanced Security" and click it
• In the left sidebar, click "Inbound Rules"
• In the large list, find the rules for "Monster Hunter Wilds" and ensure they are enabled. If they are disabled, right-click them and select "Enable Rule"
• If instead of a checkmark, you see a cross symbol, right-click the rule, then Properties. In the "Action" section, select "Allow the connection" and click OK

Test the game's multiplayer functionality after making these changes. If the error persists, continue to the next step.

2. Disable IPv6.

A frequently successful step in troubleshooting connectivity errors in Wilds. Some networks may have IPv6 routing problems that do not affect IPv4. Disabling IPv6 forces the device to use IPv4 instead.

On PC:

• Win + R
• Type "ncpa.cpl" and press Enter
• Find your active Wi-Fi/Ethernet adapter
• Right-click it and press Properties
• Find "Internet Protocol Version 6 (TCP/IPv6)"
• Uncheck it and click OK

On PlayStation and Xbox:

You will have to disable IPv6 through your router's admin page. Note that not all routers have such an option. If you wish to try, visit How to Disable IPv6 for Consoles. If you would like to try other steps first, continue reading.

3. PC only: Change Virtual Private Network (VPN) status.

The game may treat connections differently based on their IP address or geographic origin. First, if you have a VPN enabled, try disabling it and see if that resolves the error. If it does not, consider testing Cloudflare's WARP VPN, which is free and has unlimited data. It does not change your geographic origin, but it does change the route your data takes to reach the game's servers, potentially bypassing routing issues that may be causing the error.

If you wish to try Cloudflare's WARP, you will need to download the application at 1.1.1.1.

After installing 1.1.1.1:

• Open the app
• Make sure the mode is WARP, not 1.1.1.1/DNS-only
• Turn the WARP toggle ON
• Wait until the app shows that WARP is connected
• Launch Monster Hunter Wilds and try hosting/joining a quest again

Note: Conventional VPNs that change your apparent geographic origin may succeed if Cloudflare's WARP fails, but they may also introduce latency and lag, especially if the VPN server is far from your location. If you wish to try, I recommend testing Proton VPN first, as there are confirmed reports of it resolving this error. If it works but introduces latency and lag, consider testing other VPNs with servers closer to your location.