I see some people getting some Impure Client message with corrupt IWDs or something.

This happened to me once on a map, but then I closed my game, reloaded the map, and it worked fine.

 

Just a bug probably.

I know it is in beta, you don't have to tell me.

If you come from TeknoMW3, reinstall mw3 first

If you come from TeknoMW3, reinstall mw3 first

Oh.. that's just splendid.

Even I got it once, after Overwatch completed to load. Retrying again was fruitful.

 

Just telling, might help.

If you come from TeknoMW3, reinstall mw3 first

Oh.. that's just splendid.

and false

download the game from steam and hit the official records of iw5m

since only the iw5m legitimate funca

For people with that kind of problem, install hashcheck ( http://code.kliu.org/hashcheck/ ) and then extract the attached hash file to your MW3 root folder.

Double click the hash file that you extracted to your MW3 folder, and it will make a diagnose, telling you if any IWD is damaged or missing.

 

EDIT:

Hash file updated. Files not needed for MP got removed.

Thanks for the replies, staff.

I'll get right on the test.

Edit

Test results,

All were readable except the last four localized_english iwds.

Those 4 are DLC ones (2 are even empty, don't know why it's even included).

Anyway, localized IWDs won't give you "Impure Client" errors. The dedicated server doesn't even use those. So, they don't get compared (otherwise different localization clients wouldn't be able to play on the same server)

 

I'm gonna leave you another suggestion then. That "IWD comparison" is done through hash checking. I've seen hash checking randomly failing in some computers wich had their RAMs misconfigured on the BIOS (running at 1600MHz when the processor only supports 1333MHz, for example). That could explain those random "Impure Client" errors. A RAM error that would cause a fail in checking the client's IWDs hashes.

Those errors aren't common on older computer architectures, but seem to be quite common on Sandy/Ivy-Bridge (yes, I've seen it happening on an Ivy-Bridge last week already) based computers (core i* processors and respective chipsets)

You can't fix it, this is something NTA needs to do at a later time, he said so himself.