Maintenance for the week of June 9:
• PC/Mac: No maintenance – June 9
• ESO Store and Account System for maintenance – June 11, 6:00AM EDT (10:00 UTC) - 4:00PM EDT (20:00 UTC)

Launcher launches game twice

Noddegamra
Noddegamra
✭✭
This just started happening a couple days or so ago - I think it coincided with the recent update but I'm not completely sure.

I click Play on the launcher once, and it appears to start launching the game - but there is no sound on any of the logo screens until it gets to the login screen. When I put in the password and click login (or whatever the button says) it pops up a box saying a validation email has been sent. If I don't click on anything for a couple of seconds, the game exits back to the desktop but immediately starts loading as normal with sound on the logo screens all the way to login, which now operates normally.

Windows 11 pro on a laptop where the primary screen has been redirected to the HDMI port and my 4K TV (through a receiver).
  • mctaff
    mctaff
    ✭✭✭
    I am having a similar issue.
    Game will start, no sound and sometimes no actual starting splash screens.
    At the log screen, it will Crash TO Desktop, but then start again automatically and work as normal. Usually I don't get to entering any username/password.

    Norton has just had a real panic attack with eso64.exe today as well, may be unrelated.

    Win 11, desktop, two normal monitors.
    Edited by mctaff on June 5, 2025 5:37AM
  • mctaff
    mctaff
    ✭✭✭
    mctaff wrote: »
    I am having a similar issue.
    Game will start, no sound and sometimes no actual starting splash screens.
    At the log screen, it will Crash TO Desktop, but then start again automatically and work as normal. Usually I don't get to entering any username/password.

    Norton has just had a real panic attack with eso64.exe today as well, may be unrelated.

    Win 11, desktop, two normal monitors.

    For the record, I access my kids accounts too - they are through the launcher from the desktop. That always does this "launch twice" thing. And yes, Norton throws up it's cranky window each time on the first launch.

    My own account - through Steam - does not.
  • Poncho28
    Poncho28
    ✭✭✭
    Same happening with me.

    Norton 360 is flagging eso64.exe on the initial launch. I get a message from ESO to credential because it assumes I'm launching from an unidentified system. Then the ESO launcher launches immediately a 2nd time with sound and I'm able to login.

    I have both the launcher (C:\Program Files (x86)\Zenimax Online\Launcher\Bethesda.net_Launcher.exe) and the executable (C:\Program Files (x86)\Zenimax Online\The Elder Scrolls Online\game\client\eso64.exe) as accepted applications in the smart firewall.

    No word from Norton on a fix.

    I think this is a recycled bug because the same thing was happening on a launch from a couple years ago.
    Poncho-Dovahkiin (Defilers of Molag Bal, Lost Souls of Tamriel, Rebellious Spirit, Greatest of all Time)
  • mctaff
    mctaff
    ✭✭✭
    Ok, confirming that it is indeed Norton.

    I left it so the splash screens would play out, and as soon as Norton finished throwing hands with eso64.exe it killed the task and restarted the game. It's seems directly linked to the process, once Norton spits it out it will launch again normally.
  • Gabriel_H
    Gabriel_H
    ✭✭✭✭✭
    You can add the file to Norton's ignore list.mazt162dfuag.png
  • Gabriel_H
    Gabriel_H
    ✭✭✭✭✭
    Poncho28 wrote: »
    Same happening with me.

    Norton 360 is flagging eso64.exe on the initial launch. I get a message from ESO to credential because it assumes I'm launching from an unidentified system. Then the ESO launcher launches immediately a 2nd time with sound and I'm able to login.

    I have both the launcher (C:\Program Files (x86)\Zenimax Online\Launcher\Bethesda.net_Launcher.exe) and the executable (C:\Program Files (x86)\Zenimax Online\The Elder Scrolls Online\game\client\eso64.exe) as accepted applications in the smart firewall.

    No word from Norton on a fix.

    I think this is a recycled bug because the same thing was happening on a launch from a couple years ago.

    It's the AV not the Firewall. Add the file to exclusions in the AV and it should fix it.
Sign In or Register to comment.