Showing posts with label Punkbuster. Show all posts
Showing posts with label Punkbuster. Show all posts

Sunday, March 07, 2010

PB INIT FAILURE Bad Company 2

Update: 9 Mar, 2010 - EA has a fix for this error:

BFBC2 PC server R6 is going to server providers now. This server version should stop all the PB INIT errors that have been happening.


Battlefield: Bad Company 2 is having a lot of problems with PunkBuster. The first problem resulted from Punkbuster installing in the old BFBC2 Beta folder. I covered the steps for fixing this in this post

However, now players are seeing the following message:



You have been kicked from the game.  The reason is: Punkbuster kicked player 'NAME' (for 0 minutes) ... PB INIT FAILURE. (If this persists, visit evenbalance.com and click support to manually update PunkBuster).




Battlefield: Bad Company 2 Limited EditionI'll admit that I am being kicked with this error message on 50% of the BFBC2 servers I join. So far, I do NOT believe it is related to a player's individual PunkBuster install as I am able to play just fine on my friend's servers that have Punkbuster enabled.

My best guess is that this is server related and some servers are out of date or broken. So far, the way to "fix" the PB INIT FAILURE error is to find a set of servers that are working and bookmark them as favorites.

However, to make sure players have updated their PunkBuster correctly,  I have outlined the steps below.

NOTE: When dealing with any sticky program issues where uninstalling and reinstalling is a valid fix, I highly recommend using a program such as Revo Uninstaller to completely eradicate PunkBuster from the PC.  Revo Uninstaller will remove all traces of Punkbuster.

Steps to manually update Punkbuster

1. Uninstall Punkbuster using an uninstall program, removing all folders, registry, and other entries of PB from the PC.
2. Download pbsetup.exe.
3. Launch pbsetup.exe
4. Once launched, click "Add Game"
5. Select BFBC2
6. Browse to your install folder for BFBC2 (just the install folder, not any existing PB folders)
7. Click OK
8 Once back on the main screen, click "Check for Updates" and it will initiate a new install for BFBC2's Punkbuster.

Again, this may NOT fix the PB INIT FAILURE, which I strongly believe is server related!  This is simply to confirm you've uninstalled and reinstalled PB correctly.

Wednesday, March 03, 2010

How To Fix Punkbuster kicks for Battlefield: Bad Company 2 (BFBC2) on Steam

Battlefield: Bad Company 2 Limited Edition
If you are playing Battlefield Bad Company 2 on PC through Steam, you may be getting kicked by Punkbuster after a few seconds anytime you join an online game. This is most likely due to a conflict with Punkbuster and the BFBC2 Beta installation on your PC.

To fix this:

1. Go to C:\Program Files (x86)\Steam\steamapps\common
2. Delete the Battlefield Bad Company 2 Beta folder, which includes Punkbuster
3. Go to Punkbuster's website and get www.punkbuster.com/index.php?page=pbsetup.php
4. Launch the program
5. Once launched, click add game
6. Select BFBC2
7. Browse to C:\Program Files (x86)\Steam\steamapps\common\battlefield
8. Click OK and then click Check for Updates.

Punkbuster will now initiate a download for the BC2 Punkbuster client.

UPDATE: You may also need to remove the BFBC2 Beta folder from "My Documents" as well before this will work properly.

NOTE: Do not let Punkbuster run in it's default destination. It is set up to go to the BFBC2 Beta folder instead of the correct BFBC2 release version folder.



Saturday, September 19, 2009

Fixed: Punkbuster Error "Disallowed Program/Driver 125120"

This is a quick how-to on fixing the Punkbuster error "Disallowed Program/Driver 125120".
1. Disable all screen overlay features in any running programs.
2. If all screen overlay features are disabled and the problem persists, exit each program with a screen overlay and try again.
3. If FRAPS is installed, exit FRAPS and try again.
If you want the long-winded WHY of this little bug, keep on reading.

This was annoying to track down, as all things Punkbuster are, simply because Even Balance (the developers behind PB) refuse to SHARE with the community what their error codes mean or what may be causing them to kick non-cheating players.

Getting kicked by Punkbuster for "Disallowed Program/Driver 125120" simply means that a program or driver on the computer is trying to overlay something on the game-screen in a way PB does not like. This is a common way for hacks to hook into a game. Instead of interacting with the game, they sit on top of it with an overlay. This has been a common form of hack for years.

Unfortunately, Punkbuster recently made aggressive changes to how they view overlays and thus many programs that legitimately use them are now being seen as potential hacks by Punkbuster. Programs such as FRAPS and EVGA Precision.

Now, FRAPS in particular is having special difficulties. Older versions are flat-out interpreted as hacks by Punkbuster now and running any old FRAPS versions will get a player kicked repeatedly for "Disallowed Program/Driver 125120". Disabling the FRAPS overlay will not work. FRAPS must be shut down anytime a Punkbuster game is running. The FRAPS developer attempted to fix this problem in the current FRAPS version, but as quickly as they did, Even Balance changed Punkbuster to continue the kicking. So, its a tug-o-war between FRAPS and Punkbuster and I don't see FRAPS winning.

Other programs, such as EVGA Precision are in much better shape. Simply disabling the screen overlay features (such as GPU temperature) will fix the issue. This is most likely true for any number of overlay features in many video card manufacturer's software management/monitoring programs.

Unfortunately, for dedicated players of games like Call of Duty 4 or America's Army 3, this means the loss of some great software tools. Fuck Punkbuster. Once upon a time they were decent, but they've become the porta-potty of the anti-cheat world. No one wants to use them, they stink like shit, but unfortunately its the only option.

Thursday, July 17, 2008

Busted Punk

It never fails. Every time I talk up a piece of software, such as Punkbuster becoming part of Warhammer Online: Age of Reckoning (WAR), it comes back and kicks me in the balls. Since Mark Jacobs announced that WAR would be using Punkbuster, I've been out on the message boards giving my side of the argument. Punkbuster has never really given me problems, aside from an issue with Quake Wars: Enemy Territory's second demo and a brief stint with a Call of Duty 4 patch. I've dealt with Punkbuster on both the client and server side.

My argument all fell apart when I went to play Call of Duty 4 yesterday.

Punkbuster Failed to Initialize.
Punkbuster Failed to Initialize.
Punkbuster Failed to Initialize.
Punkbuster Failed to Initialize.
You were kicked for PB INIT FAILURE.

No amount of firewall finagling or anti-virus witchery did the trick. All the changes and tweaks suggested by the official Punkbuster support team didn't help. In the end, I was left doing what I always do with computer problems that befuddle me: Google.

A few clicks through Google in search of PB INIT FAILURE fixes and I came across a posting including a download for a new, and supposedly working, PB folder. I downloaded the folder, deleted my old PB folder, and replaced it with the new one. Problem solved. No re-installs, no updating, no nothing. Just a working Punkbuster.

Now I'm curious what Punkbuster support will say about my fix.