Hood Warfare 2 Troubleshooting: Crashes and Kicks

Before you start

Two checks solve more Hood Warfare 2 problems than anything else, and both take under a minute.

1. Confirm your build. The version appears in the bottom-right corner of the main menu. The current build is 1.0.1.4. If you are below that, exit Steam completely and relaunch — the developer's own patch note says this is sometimes required to receive an update.
2. Verify the game files. In Steam, right-click Hood Warfare 2, open Properties, then Installed Files, and choose "Verify integrity of game files". This replaces anything that downloaded incorrectly.

If the problem matches one of the sections below, go straight to it. Several common launch problems were fixed in the October 12 and October 14 patches, so an outdated build can look like a permanent bug.

"Kicked for cheating" and the ImpossibleRpc error

Symptom. You are removed from a match with an anti-cheat message, sometimes naming an error such as ImpossibleRpc, while you were playing normally.

Official status: fixed. Patch 1.0.1.4 states plainly that it "Fixed Issues with Anti Cheat kicking players falsely". If you are being kicked and you are on an older build, updating is the first thing to try.

If it still happens on 1.0.1.4, work through these in order:

• Verify the game files through Steam, then restart the game and Steam itself.
• Close overlays and any third-party tool that hooks into the game — capture software, performance overlays or input remappers can all be read as interference.
• Disconnect and reconnect to the network, then join a different match to see whether it follows you.
• Report it, so the developer has a record. The pause menu has a Report option added in 1.0.10.

Players have proposed their own explanations for the false positives. One commonly repeated theory in the official discussions is that firing around a corner in third person without fully exposing yourself registers as shooting through geometry, which the anti-cheat reads as wall-hacking. That is a player theory, not a developer explanation, and it is repeated here only to show what people are seeing, not as a confirmed cause.

Cannot connect, or cannot join a match

Symptom. The game sits on a connecting screen, drops back to the menu, or refuses to load you into a match your friends are in.

Official status: addressed. Patch 1.0.1.4 lists "Fixed various join game issues and crashes" and also added private password-only lobbies, which removed one common source of join trouble.

Steps to try, in order:

1. Make sure you and your friends are on the same build number. Mixed versions are a frequent cause of a lobby that will not load.
2. Restart Steam fully, then relaunch the game.
3. If you are using a private lobby, check the password and confirm everyone is entering the same one.
4. Switch off any VPN, and check that your broadband connection is stable — the store page lists a broadband internet connection as a requirement.

When it is likely server-side. If nobody in your group can connect at the same time, if the failure happens across different networks, or if the game works again later with no change on your machine, the cause is almost certainly not local. In that case there is nothing to fix on your end.

Crashing on launch or after a match

Symptom. The game closes to the desktop at startup, during loading, or when a match ends.

Official status: partly addressed. Patch 1.0.1.4 lists crashes among the issues it fixed, so updating is again the first step.

Things worth checking:

• Meet the minimum specification. The official minimum is a six-core Intel Core i5-9600K or AMD Ryzen 5 3600, 8 GB of RAM, and a GeForce GTX 1660 or Radeon RX 5600 XT. Running below that is a common cause of crashes and stutter that nothing else will fix.
• Update your graphics driver. The game requires DirectX 12, so a current driver matters.
• Free up storage. The minimum install is 25 GB, and the recommended figure is 30 GB with the game on a drive that has room to spare.
• Verify the files again if the crash began immediately after an update.

Low frame rate and heavy VRAM use

Symptom. Playable but choppy, with frame drops during firefights or in crowded areas.

Hood Warfare 2 is built in Unreal Engine 5, per the developer's own description, and UE5 titles lean heavily on graphics memory. The minimum graphics requirement is a 6 GB card and the recommended one is 8 GB, which is a useful signal about where the pressure sits.

• Lower the resolution scale and shadow quality first — those two settings usually return the most frames per unit of visual loss.
• Close background applications that use graphics memory, especially browsers with hardware acceleration enabled.
• Confirm the game is running on your dedicated GPU rather than integrated graphics, on laptops in particular.
• Check your power plan is set to a performance mode if you are on a laptop.

If the game is below the recommended specification, settings will help but there is a floor. The exact performance cost of each individual setting has not been published by the developer.

Progress showing as zero

Symptom. Your level, unlocks or reputation appear to have been wiped or rolled back.

This is covered in more detail on the progression page, but the short version is that the October 12 patch notes list "progression not properly showing on end of match sometimes" among the bugs that were fixed. If you are on 1.0.1.4 and still seeing it, restart the game before concluding anything has been lost, and check the progression page for what has and has not been confirmed.

Reporting a problem

If none of the above helps, report it, because the developer's patch notes read as though they are driven by player reports — the 1.0.10 note thanks players for launch-week feedback and asks for bugs to be reported in the Discord, and the 1.0.1.4 note promises more updates.

Have these ready before you report:

• Your build number — the string in the bottom-right corner of the menu.
• The exact error text, if one appears, including codes such as ImpossibleRpc.
• What you were doing when it happened — the map, the mode and the moment.
• Your PC specification, matching the categories on the store page: processor, memory, graphics card.

In-game, use the Report option in the pause menu for suspected cheaters; the developer states reports are reviewed. For everything else, the official channels are the Steam discussions and the Discord server referenced in the patch notes. The store page lists an email address for support enquiries.

What not to try

A few widely suggested "fixes" carry real risk and should be avoided.

• Do not install anti-cheat bypasses, injectors or modified game files. These are the fastest route to a restriction on an account, and they cannot fix a false positive that the developer has already patched.
• Do not download the game from anywhere other than Steam. There is no official version outside the Steam store, and builds from elsewhere are unverifiable.
• Do not disable your operating system's security features to make a game launch. If the game is being blocked, prefer an exception for the game folder over switching protections off.