How to fix Monster Hunter World error code 50382-MW1 in Windows?

Error code 50382-MW1 means Monster Hunter: World could not open a player-to-player connection to the other hunters in time. If it happens with one friend only, Capcom says the problem may be on their network. If it happens with everyone, restart the PC, modem and router first, then put the PC on a cable and turn on UPnP.

Facts checked on 15 October 2026. Steps written for Monster Hunter: World and Iceborne on Steam, Windows 11 (25H2 and 26H2) and Windows 10 22H2, read against Capcom Support's 50382-MW1 page, its Steam network troubleshooting guide and Steam Support's list of required ports.

What Monster Hunter World error code 50382-MW1 means

Monster Hunter: World puts hunters in the same session by connecting their PCs straight to each other, player to player. Capcom Support says error 50382-MW1 occurs "when a player-to-player (P2P) connection with another user cannot be established and the connection attempt is timed out". The game waits, gives up, and shows the message. Your save, your hunter and your copy of the game are not affected.

The code is the same in the base game and in the Iceborne expansion, and Capcom uses it on PlayStation 4 and Xbox One too. People search it as 50382-MW1, 50382 MW1, "MHW error code 50382" and by the text "Failed to connect to session members". All of them are the same error.

What causes error 50382-MW1, from most to least likely

Capcom's network guide for Steam lists the things that block a direct connection, but publishes no numbers. The order below is ours, from the cheapest check to the one that needs your router or your internet provider.

How to fix Monster Hunter World error code 50382-MW1

Fixes 1 and 2 take a few minutes and need no settings. Fixes 3 and 4 are on the router and solve most stubborn cases, because they decide whether other PCs can reach yours. Fixes 5 to 7 cover the PC itself.

Fix 1. Check Steam, then restart the PC, the modem and the router

5 minutesNo riskEveryone starts here, above all when online play worked until today.

Capcom's first steps for any network error are to check whether Steam is down and to refresh the modem and router. A router that has run for weeks can lose its port mappings, and the game then cannot be reached by other players.

1. Check whether Steam reports an outage. Capcom points to the Steam Support account on X (Twitter) for news of outages. If Steam is down, wait.
2. Exit Monster Hunter: World, then exit Steam from the Steam menu with Exit.
3. Restart Windows: Start > Power > Restart.
4. Unplug the modem and the router and leave them off for a few minutes, as Capcom asks.
5. Plug in the modem first. When its lights are steady, plug in the router.
6. Start Steam and the game, and join the session again.

If Windows itself shows no internet after the restart, fix that first. Step by step: How to check your internet connection in Windows

Fix 2. Play on a cable, turn off Wi-Fi, and free the bandwidth

5 to 10 minutesNo riskYou play on Wi-Fi, have both Wi-Fi and a cable connected, or others use the internet while you play.

Capcom recommends a wired Ethernet connection for Monster Hunter: World online and asks you to turn off other devices that use the internet. A P2P link needs a steady connection, and Wi-Fi drops or a full line make the join time out.

1. Connect the PC to the router with an Ethernet cable.
2. Press Win + R, type ncpa.cpl and press Enter. Network Connections opens.
3. Right-click the Wi-Fi adapter and select Disable, so Windows uses the cable only. Leave the Ethernet adapter on.
4. Stop streams, downloads and cloud backups on the other devices at home, as Capcom suggests.
5. Start the game and join again.
6. If you are already on a cable, test once with the cable straight from the PC to the modem, without the router. Capcom suggests this to rule the router out.

Fix 3. Turn on UPnP, check the NAT type, and fix a double router

10 to 20 minutesLow riskIt fails with every session, also on a cable, or the game or router reports a Strict NAT.

Other players can only connect to your PC if the router lets their traffic in. Capcom asks you to turn UPnP on, turn packet filtering off, and put one of two routers in Bridge Mode. It also says a Strict NAT, common in dorms, can block online play.

1. Open the router's settings page. The address and login are usually on a label on the router or in its manual.
2. Find UPnP (often under Advanced, NAT or Network) and turn it On. Save.
3. Find packet filtering and turn it off, as Capcom asks. Ask your internet provider whether they filter packets too.
4. Check whether you have two routers, for example the provider's box and your own Wi-Fi router. If so, put one of them in Bridge Mode, as the router manual explains.
5. Restart the router, then the PC, and join a session again.

Fix 4. Forward the Steam ports on the router and ask your provider

15 to 30 minutesLow riskUPnP is off, missing or did not help, or you play on a university, office or hotel network.

Capcom asks Steam players to forward the Steam ports and to make sure the internet provider does not block them. Monster Hunter: World uses Steamworks P2P networking, whose ports are on Steam Support's list.

1. Find your PC's local IP address: press Win + R, type cmd, press Enter, type ipconfig and note the IPv4 Address.
2. Open the router's settings page and find Port forwarding (sometimes Virtual server or NAT rules).
3. Add the ports from the table below for the PC's IP address, with the protocol shown.
4. Save and restart the router.
5. On a school, office or dorm network, ask the network administrator to open these ports. Steam Support says many such networks block them and that they cannot be moved to other ports.
6. If it still fails, ask your internet provider whether they block any of these ports, as Capcom suggests.

Fix 5. Allow MonsterHunterWorld.exe through the firewall and antivirus

5 to 10 minutesLow riskThe error began after you installed or updated a security program, or you use a third-party firewall.

Capcom asks you to add MonsterHunterWorld.exe to the Windows Firewall and antivirus exceptions. A firewall that blocks the game's incoming traffic stops other players from reaching you, which is exactly a P2P time-out.

1. Press Win + R, type firewall.cpl and press Enter.
2. Select Allow an app or feature through Windows Defender Firewall, then Change settings.
3. If Monster Hunter: World is in the list, tick Private for it. If not, select Allow another app, Browse, and open the file below.
4. Select Add, tick Private, and select OK.
5. Open Windows Security > Virus & threat protection > Manage settings > Exclusions > Add or remove exclusions, and add the same file. In another antivirus, add it as a trusted program.
6. Start the game and join again.

C:\Program Files (x86)\Steam\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe

If you installed the game in another Steam library, right-click it in Steam, select Manage > Browse local files, and use that folder. To test whether the antivirus is the cause, pause it for one join and turn it back on at once: Turn off Microsoft Defender protection for a moment

Fix 6. Set your Steam profile to Friends Only and lower the server browser pings

5 minutesNo riskFriends cannot invite you, or the quest and session lists load slowly before the error.

Capcom says Steam users with a private profile cannot send invites, and asks for Public or Friends Only. Steam's own hint under Server browser pings/minute says to lower the value when browsing game servers gives connection problems.

1. In Steam, select your name at the top and then Profile.
2. Select Edit Profile, then Privacy Settings.
3. Set My profile to Public or Friends Only, as Capcom asks.
4. Open the Steam menu, select Settings, then In Game.
5. Under More, set Server browser pings/minute to 250 (the default is Automatic, 5000).
6. Close the settings, restart Steam and join again.

Users on the Steam forums report that the lower ping value cleared 50382-MW1 for them. That is a report, not a Capcom fix, and it costs nothing to try.

Fix 7. Reset the Windows network stack

10 minutes plus a restartLow riskOther online games or programs also drop, or you changed DNS or IP settings by hand.

Damaged Winsock or TCP/IP settings can break the incoming connections a P2P session needs, while web pages still load. The reset puts these settings back to the Windows defaults.

1. Open Command Prompt as administrator.
2. Run ipconfig /flushdns, then netsh winsock reset, then netsh int ip reset.
3. Restart the PC and join a session again.
4. If that did not help, use Network reset in Settings, which reinstalls the network adapters. Note your Wi-Fi password and VPN settings first. Step by step: Reset the network and flush DNS

If error 50382-MW1 still shows: what to check and whom to ask

The game writes no log you can read for this error. Capcom's page ends with one advice when all steps fail: contact your internet provider about your network environment. Some providers use carrier-grade NAT, which no home router setting can open.

1. Note whether it fails with everyone or with one friend, and whether a phone hotspot works.
2. Note the NAT type the router shows, and whether UPnP is on.
3. Ask your internet provider whether you have a public IP address, whether they block or filter ports, and whether PPPoE settings are needed. Capcom names the last one.
4. Contact Capcom Support with your region, the error code and any other codes you saw. Capcom says this helps them investigate.

• When it is the friend's network: you join others, never them. The friend runs Fixes 1 to 4.
• When it is the provider: a hotspot works and home does not, even with UPnP and ports open.
• When it is not a P2P error: the message names another code. Search Capcom Support for that code, because each code points to a different problem.

How to keep error 50382-MW1 from coming back

The rule behind this list is short. Other hunters must be able to reach your PC directly. Keep the line steady, the router open to the game through UPnP or ports, and the firewall aware of the game, and the message stays away.

Frequently asked questions

What does error code 50382-MW1 mean in Monster Hunter World?

It means the game could not connect your PC directly to another player's PC, and the attempt timed out. Capcom Support describes it as a player-to-player (P2P) connection that cannot be established. The full message is "Failed to connect to session members. Error code: 50382-MW1". It shows when you join a session, a quest or an SOS flare. It does not mean your game files or your save are damaged. Start with a restart of the PC and router (Fix 1), then a cable connection and UPnP (Fixes 2 and 3).

Why do I get 50382-MW1 with only one friend?

Capcom says that if the error happens only when joining one specific friend, the problem may be in the other player's network environment. A direct connection needs both routers to let the traffic through. If either side has a Strict NAT or UPnP off, the link fails. Ask the friend to run Fixes 1 to 4 on this page: restart, cable, UPnP and NAT, ports. To be sure, both of you can try joining a third player. Whoever fails with the third player has the problem.

Is 50382-MW1 the same in Iceborne?

Yes. Iceborne is an expansion of Monster Hunter: World and uses the same online system and the same error codes. Capcom's support pages cover Monster Hunter: World and Iceborne together. The cause and the fixes on this page are the same whether you play the base game or the expansion. If you see the error only with one group, check that everyone runs the latest game version, since Steam updates the game for each player separately.

Does changing the Steam download region fix 50382-MW1?

Some users on Reddit report that changing the Steam download region, for example to New York or Tokyo, stopped the error for them. That is a report, not a Capcom fix, and we could not confirm why it would help. It does no harm to try: open Steam > Settings > Downloads and change Download Region, then restart Steam. If it changes nothing, set it back to the region nearest to you, because a far region slows down game downloads.

Do the -nofriendsui -udp or -tcp launch options fix error 50382-MW1?

We could not confirm it. Many older guides, including our previous version, tell you to add -nofriendsui -udp or -nofriendsui -tcp to the game's launch options. Capcom does not mention them for this error or in its network guide either. If you added them and nothing changed, remove them from the game's Properties > General > Launch Options. Spend the time on UPnP and the ports instead (Fixes 3 and 4).

Should I change my DNS server to fix 50382-MW1?

It is unlikely to help. DNS turns names into addresses; a P2P session between two hunters connects to the other player's address directly, so DNS has little to do with it. Capcom does not list a DNS change for this error. If you still want to try Google's public DNS, the addresses are 8.8.8.8 and 8.8.4.4. Our earlier guide listed a wrong second address. A network reset (Fix 7) also clears DNS settings you changed by hand.

Which ports does Monster Hunter World need on PC?

The PC version runs on Steam, and Capcom asks you to forward the Steam ports. Steam Support's current list: TCP 80 and 443, UDP and TCP 27015 to 27050 for sign-in and downloads, UDP 27000 to 27250 and 4380 for game traffic, and UDP 3478, 4379, 4380 and 27014 to 27030 for Steamworks P2P and voice chat. Forward them to your PC's local IP address in the router, or turn on UPnP so the router opens them by itself.

Will verifying or reinstalling the game fix 50382-MW1?

Usually not. The error is a network time-out between two PCs, and Capcom's page and network guide point only to network steps. Verifying the game files is quick and harmless if you also see crashes or missing content: right-click the game in Steam, select Properties > Installed Files > Verify integrity of game files. Reinstalling the whole game costs a long download and does not touch the router, the NAT or the firewall, where the cause of this error lies.

I get 50382-MW1 on PS4 or Xbox. Does this page help?

Partly. The meaning is the same on every platform: a direct connection to another player timed out. Fixes 1 to 4 (restart, cable, UPnP and NAT, ports) apply to a console too. The Windows steps and the Steam settings do not. Capcom has separate network troubleshooting guides for PlayStation 4 and for Xbox One, linked from its 50382-MW1 page, with the ports those consoles need.