steam_api.dll error :/

[Predicador]

I have a problem to start COD black ops 2, will not let me launch the game and when I try manually from the folder it tells me there is an error with: steam_api.dll. Not to do anyone help me?

[×boomcazoo×]

Same here :/

[Kafrat]

Same here.

[Shott]

Same: it happened when i tried to play zombies - re-installed Zombies and still no luck.

[×boomcazoo×]

If you've already tried downloading steam_api.dll and continue gettting this error

I figured out an answer. Right click the game->properties->local files->verify integrity of game cache. It's either going to find some problematic files or it wont (If it won't, you'll have to reinstall the game by deleting all local files, one tab above VIGC button, and then install the game through library). The problematic files will automatically be re-downloaded from steam's search then it will begin to download replacements.

Hope this helps you and whoever else runs into this problem in the future!

If this doesn't help whatsoever (even reinstalling doesn't work) you may have to submit a help ticket into steam for further assistance. Sorry :/

[Delicious]

I found that this happened to me when I had it installed in a location that WASN'T C:\Program Files (x86)\Steam.

Verifying game files didn't fix and neither did re-installing.

Once it was installed in the default location it was fine.

[twolfhound]

So, I ran into this problem and came here looking for a solution. None of the above helped. So, I went looking for steam_api.dll in the game folder. I saw it was there and tried to cut it out of the folder and place it on the desktop. It wouldn't work, said it was open by 't6mpv43.exe'. I opened task manager, but couldn't find that file name running anywhere. So, I opened my command prompt (using administrator), and ran 'tasklist'. I found it there and copied the PID # for it. I then ran 'taskkill /PID ##' (where ## is the actual PID # of the program). Once t6mp43.exe was no longer holding the steam_api.dll file hostage, it was able to write to it, again. Ran the program, and it ran fine.
Hope this helps.