Valve Source Sdk Incompatible With Bitdefender Firewall (x64)
On my 64-bit Vista box, when the Bitdefender firewall is enabled, Source SDK (a highly popular tool used by a wide community of modders) behaves erratically. For example:
- SDKLauncher.exe only starts on approximately 25% of tries.
- Hammer will not start when launched via SDKLauncher (which is essential for it to work correctly), and the same 25% chance of success applies when launching it directly from the exe.
- None of the map compilation tools (vbsp, vvis, vrad) will run correctly from within Hammer, and it is essential for vbsp to be run in this way or it will fail.
This bug did not appear on a 32-bit Vista computer, but the Source SDK has always had x64-related issues in the past so this is not surprising.
This happened after a full reinstall of Steam and the Source SDK (including resetting all settings), so it is not specific to my installation.
A blanket exception allowing everything possible within the firewall across the entire Steam folder doesn't help, but when the firewall is disabled the problem instantly disappears.
This happens with trust at Trusted Local, stealth off and generic set to yes, as was mentioned in another thread.
Any ideas? 
Comments
-
Also I forgot to add (and I don't seem to be able to edit my post) that Bitdefender is on Game Mode (still happens on any other mode though) and I have the following firewall settings:
0 -
Also if it's any help, vbsp shows signs of being unable to read files which actually exist while the firewall is enabled.
0 -
Hello Darkimmortal ,
Because we need to have a look on some BitDefender files from your system and some reports generated by some diagnostic tools, we had to send you an email . Reply with the files that we need and we will contact you back as soon as we have a resolution .0
