Just a quick note for those playing the Steam version of Football Manager 2010. A recent Steam update has apparently caused a minor issue with the game. To wit, you may see the following Steam error message when you attempt to launch it:
Translation: “You can’t play. Neener neener.”
Here’s how you may be able to solve it.
First, verify FM2010’s files are all there. To do this, right-click on Football Manager 2010 in Steam, select Properties, switch to the Local Files tab then select “Verify integrity of game cache…” If Steam finds an error, it will download any missing FM2010 files the next time you launch the game.
If you still get “error code 83” after this, check your firewall settings. I’m using ZoneAlarm in addition to my router’s firewall. It seems like overkill, I know. However, I find ZoneAlarm very useful when monitoring outbound traffic . I’m particularly fascinated by how some programs attempt to get online even when it’s not at all necessary. Steam would be one example. Even when you set it to offline mode, the Steam executable attempts to contact Valve.
C’mon, Gabe, you don’t need to know the contents of my secret special folder, do you? I keep telling you it’s all nature documentaries.
The most likely reason for “error code 83” is the FM2010 executable now needs online access when it launches. This is a new thing. I previously had ZoneAlarm automatically decline FM2010’s internet access requests and could play the game without issue. After the January 18 Steam update, FM2010 now needs to contact Valve, possibly for Achievements-related purposes.
Or maybe Gabe just wants to know how many nature documentaries you’ve seen this week. That Gabe, such a curious cat.
After switching FM2010’s privileges to “Ask” in ZoneAlarm, I discovered the game executable now tries to go online twice: almost immediately after launching the executable and after the various startup screens. You only need to approve the first request to avoid “error code 83”.
The second request, which can be safely declined, is to contact IGA Technologies, a company dealing with internet gaming ads and almost certainly the company that serves up the ads seen on FM2010’s billboards during matches. It’s interesting how FM2010 tries to contact the ad company even when you’ve declined to view in-game ads and share user data, eh?
The bottom line is if you’re getting error code 083, check your firewall settings.
If that still doesn’t fix the problem, pass some nature documentaries to Gabe.
Jan. 27
I had an “error code 83” with another Steam game, Europa Universalis III. To fix it, I verified all my files were A-OK (five were not so I had to download them again), allowed eu3.exe online access when it asked and managed to eventually get EU3 working. I say eventually because I initially had ISP-related problems with my internet connection. Once my internet connection stabilised, eu3.exe managed to get online (for whatever reason) and I was able to play the game. Same problem, same fix.
I’m more convinced than ever that “error code 83” is a connectivity issue caused by Steam’s January 18 update. Some games now need online access upon launching even when you set Steam to offline mode.
If you’ve tried everything and you’re convinced you don’t have any firewall or ISP-related issues preventing your game executable getting online, please consider posting to one of these Steam threads. The problem is widespread, affecting several Steam games and definitely Steam-caused. Please be sure to point out you had no problem launching the game(s) before the recent Steam update. This will hopefully help Valve pinpoint the source of the problem faster.
Feb. 4
It looks like Valve has isolated the problem. A fix is forthcoming but those who can’t wait can opt to try the beta client.
I do wonder, however, why the Steam client needs to do a DNS lookup even in offline mode.
Bless you. I’ve been tearing my hair out for hours trying to get Star Wars: Knights of the Old Republic to run on Steam, doing everything from reinstalling and changing the ini file to searching for hotfixes. I couldn’t find information about this on the Steam SW forums or the Bioware forums. I finally realized that googling steam “error code 83” was the intelligent thing to do and came across this. Even though Steam is unblocked in my firewall, Windows had auto-blocked KOTOR upon installation. I created a couple of new rules, and voila, it works.
Again, bless you.
Glad to help, Jeremy!
hi mate, i have that problem and still unable to solve it. I tried the verification but it didnt work. Could you help me with the firewall process causw im pretty noob at it and dont want to mess up my firewall settings as well.
hi. i have two games affected (fm2010 and one more). also i am reading about people having same problems with different games (like battlefront). so looks like it’s more steam problem. or thay updated many gameswith 1/18 update.
i run default windows firewall. both my games are allowed there. i also checked ‘notify’ box. but nothing helped. glad it worked in your case though. at least some hope
I can’t help you unless you’re specifically using ZoneAlarm, I’m afraid, Your best bet is to consult your router’s manual. You most likely need to look at application permissions. In FM2010’s case, the executable is fm.exe.
The January 18 update was a Steam-wide thing that apparently changed Achievements, stats and network communication. It apparently also affected several games.
Did you try verifying your FM2010 game cache? Perhaps removing FM2010 from Windows Firewall’s Exceptions list then approving it again (or simply editing the settings) might help.
Hi im getting the error code 83 message verified game fiels and turned both my kaspersky and windows file off and still no luck >.>, any idea mate would be greatly appreciated got Bournmouth into the premiership ='[ dont weanna lose it.
Hi.
Have the same problem as OE. Removing and adding FM again in the Firewall Exceptions doesn’t work. Getting desperate! Any ideas what to do?
If you’ve verified the FM2010 files are all there and there’s nothing preventing the FM2010 executable from contacting Valve, I’m afraid your only recourse is Steam support.
What’s common with Crysis (+Warhead) The Witcher EE, King’s Bounty, and Knights of the Old Republic? Absolutely nothing… one might think.
Except all of the forementioned titles on my Steam account have fallen under Error code 83. None of them work.
Everything else works just fine e.g. MW2, L4D2, Torchlight…
This started after the jan 18th update. I created my ticket at 20th. Still unresolved. I’ve reinstalled Steam, I’ve redownloaded and installed all these titles. Nada. They simply refuse to run… except of course with a no-dvd crack. Which makes this even more depressing situation. Why would I ever bother with Steam again after this debacle?
If a simple update can break a number of completely noninterchangeable titles in this way, what future does this platform even have?
Hi, it worked perfectly for me and from what i ‘m reading above i feel lucky…. Thank you millions and millions of times….
I said that i was lucky yesterday but i’m not because i’m repeating the same procedure to play… My question is will i have to this every time i’m playing manager or somehow they ‘ll do something about it? If you have any idea please answer…..
Valve updated the Steam client in February to fix the issue. If you haven’t updated your client in a while, please do so.
tar, solved it straight away thankyouuuu <3
I was having the same error code 83 on Torchlight 2, my firewall was off and TL2 was already in the program exceptions but still failed to launch with the 83 error code. By adding the Steam program to the exceptions list it launched with no other problems.