I am trying to get onto US servers.
Have downloaded L2, updated all the files
and I get this

"l2.bin failed to run" error.

I've contacted NCSoft, but no love there, anyone have any ideas?
I do not have AVG. Using Vista 64bit (and reverting to Xp isn't an option).

Thanks

Zombie.

avg sometimes removes important files from l2.

ive actualy had it remove the l2.exe on multiple occasions.

id suggest checking if the bin was removed, and also reinstaling with avg deactivated.

Check to see if your anti-virus software (AVG or otherwise) has quarantined the file.

Make sure windows firewall is off or has L2 entered as an exception.

Turn off Vista's Account Control Security feature.

Try running Lineage II in XP compatability mode and/or as an Administrator.

I can't figure this F'ing problem out.
Have googled and googled and googled.
Seems like its a pretty common problem for us poor innocent Vista users.

I have allowed the file in antivirus (Sophos)

I have deleted system folder and done the check files thing (it just downloads L2.bin.zip)

I have done the properties > run as administrator thing...dont know whats left.

Update to windows 7?

I figured it out (touch wood).

I did all of the above and then I went to system Folder and deleted the file

vorbisfile.dll

then did check files and bang goes the budgie, I was in.

Good to hear. You should post a detailed reply with EXACTLY what you did and in what order to help out anyone else that is experiencing this problem.

Okay This problem wasn't 100% solved to my satisfaction.
As I said before I deleted
Programs > Lineage2 > System > vorbisfile.dll

L2 works fine now...Except
After a few hours of Play L2 Crashes and I get a error message about L2.bin
I also cannot Maximise/restore L2 window if its minimised....not sure of this is a related problem or completley seperate...

I think you should upgrade your PC.. Most of online games nowadays is not compatible to vista.. I don't know why but it happened at all times..

sometimes vista gives me issues with games while in admin mode, perhaps this is part of the problem for you?