Playing Lineage 2 in Windows 7 (Gameguard Fix)


If you’ve tried to play Lineage 2 on Windows 7 you’ve probably been bummed out to find that you get that pesky “GameGuard” error that has been plaguing pretty much every game in Windows 7 that uses GameGuard. What purpose GameGuard serves I have never bear witness to, it’s only given me problems, and this definitely is not the first time.

There is a solution that works for both Aion (not sure if you even need it anymore, they may have patched Aion) and Lineage 2, and probably any game in Windows 7 that needs GameGuard. I guess I should give a little disclaimer and say that you should “do this at your own risk” because you are technically messing with files in the game directory, which is usually against the TOS/EULA, but in reality you’re not doing any harm and without this fix you wouldn’t be giving them $15/mo and playing their games. Since they don’t want to fix it themselves (yet), this is the only option for playing Lineage 2 on Windows 7.

I’ll try to make this simple. You’re basically replacing the “gameguard.des” file (one small, measly file) so that the game will launch correctly, with the trick being that you need to replace it after Lineage 2 has gone through it’s auto-update routine in the patcher. Full details after the jump.

  • Download this Windows 7 proof gameguard.des file (Note: This was stripped straight from another legit game that uses gameguard, I think Rappelz, so it’s not some “hacked” or illegitimate file. From what I understand, it’s simply the file they need to put into the Lineage 2 patcher themselves, but haven’t yet.)
  • Extract the “gameguard.des” file to somewhere handy where you can get to it every time you want to play the game. I myself put it on my desktop.
  • Run Lineage 2 and let the patcher do its thing and leave it open with the play button ready to be hit.
  • Locate the Lineage IISystem folder that already has a “gameguard.des” file in it. Default location is C:Program FilesLineage IISystem or if you’re in 64bit Windows 7, C:Program Files (x86)Lineage IISystem
  • Copy the “gameguard.des” file that you extracted from the download and replace the one that is in the Lineage IISystem folder
  • Now hit the play button

Sure, it’s kind of obnoxious to have to do this every time you want to play, but it’s better than not playing at all if you really want to play.

Enjoy some Lineage II on Windows 7!

27 thoughts on “Playing Lineage 2 in Windows 7 (Gameguard Fix)

  1. That’s good to know, Nozzle… although I doubt I?ll be coming back to L2 anytime soon. Having a blast on AoC, and my Demonologist is now reaching lvl 70 (he will be 70 as soon as I stop RPing enough to PvE him LOL!).

    DOn’t miss L2 at all, not even one bit. Never been happy in a game before in many, many years!


  2. Glad to hear from you and that you’re still enjoying AoC. I still have my Collector’s Edition key waiting to be activated, just haven’t had the itch to try it yet, even with the latest patch coming out. Too many games to play!


  3. James.. if u check this page again …i’m sad to tell u …that doesn’t work :)) …so if u know something else to fix that error … pls leave a reply …ty



  4. @Jerry – It works, but as someone mentioned, perhaps just for x64. I probably should have mentioned I’m running x64 Windows7. Haven’t tested it on 32bit Win7.

    @Daniel – glad to hear it worked and helped you! 🙂


  5. Just like Snorx, I’m using Windows 7 RTM x64 and it doesn’t work. I’ve tried everything and all compatibility modes…nothing. I’m running out of options here..


  6. Sorry for double post, but I forgot to say that it doesn’t even enter the game. I double-click the icon, I get the splash screen and this pops up: L2.exe has stopped working…


  7. 2009.8.14 02:34:22
    OS : Windows Vista 6.1 (Build: 7600)
    CPU : GenuineIntel Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz @ 3006 MHz 4095MB RAM
    Video : NVIDIA GeForce GTX 280 (8618)
    PosCode : LS1(83) 0:0:0 4/0 [436]

    Error setting display mode: CreateDevice failed (D3DERR_DEVICELOST). Please delete your Option.ini file if this error prevents you from starting the game.

    History: UD3DRenderDevice::UnSetRes <- CreateDevice <- UD3DRenderDevice::SetRes <- HandleBigChange <- UD3DRenderDevice::Lock <- UViewport::Lock <- UWindowsViewport::Lock <- Precaching <- UGameEngine::Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- MainLoop


  8. Holy comments batman. I’m not sure what to tell you all, this worked when I played – but I haven’t touched Lineage 2 in a few months and don’t currently have it installed, otherwise I would go do some more troubleshooting to figure out if it still works.



  9. You have to repeat these steps everytime L2 has been patched. An easy way is to let the game do all patches, then close the patcher, copy that gameguard.des into the system-folder and overwrite the existing there. Then rename L2.bin to L2.exe and use that exe file to start lineage each time u want to play. Once it doesn’t work anymore, it means there have been new patches, so rename L2.exe to L2.bin again, start the patcher, let it patch everything, then close it again, copy gameguard.des into system-folder, rename L2.bin to L2.exe and play again using that file till next patch.


  10. in windows 7 enterprise 64 bit, it doesnt work, cause in the Gameguard folder i have got gameguard.ver file not gameguard.des


  11. This doesn’t work for me, without the gameguard.des I mean with the one i used y vista, xp, lineage window pop ups but with the gameguard problem, but with the gameguard.des you posted here, the start up image of lineage shows up but when is going to open the window, a blue screen shows saying windows shutted off to prevent any harm, and then my laptop Restarts itself, please help my I wanna play L2 in my W7


  12. @Rakshas I have the same problem 😦 when i start up L2 before the windows come up my PC restart itself (blue screen)<- i hate you -.- i hope someone can help us
    Sry for bad english!


  13. Anyone familiar with the “side-by-side configuration error”? That’s what I’m getting and with a little trick I got the “insufficent virtual memory error” which can’t be fixed with or without virtual memory enabled. Some said it may be a lack of memory problem which NCsoft claims it ain’t their fault. Awaiting a new attempt of fixing :D. (OS: Win7 x64 Build 7600)


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s