Debugged one of the launcher issues

Uristqwerty · July 13

Seems there are a wide variety of problems that people have been having. Digging around in a debugger*, I can at least share the technical details for one of them in hopes it can help:

If pressing Play crashes in AcLayers.dll, then it seems to be a problem on older Windows 10 (and, presumably, <10) versions; someone on the steam forum says that 22h2 works and 1809 doesn't.

For fellow programmers, I can add what appears to be the cause: If CreateProcess is called with dwCreationFlags having the EXTENDED_STARTUPINFO_PRESENT flag set, it appears that AcLayers' ElevateCreateProcess::APIHook_CreateProcessW (at least, that's what Windows' public debug symbols calls it) will blindly assume that lpStartupInfo is a STARTUPINFOEX with a non-null lpAttributeList. Presumably Microsoft added their own additional null check to Windows 10 some time in the past few years.

Apparently there are steam users who can't play at all as a result, though at least anyone who (also) bought a non-steam edition can manually launch eso64.exe and log in via username and password.

(*Didn't look at any Zenimax code, just the faulting Windows DLL and parameters it was called with, should anyone care. Any assembly's bad enough; I'd hate to see what an optimizing compiler does when it can invent its own internal calling conventions or inline things.)

Verling · July 14

I noted the same thing.
I see problems on many computers at once. Both on their own 4x and with friends and comrades from different guilds.
1. windows 7 and 8.1 update is normal - startup error with a message about AcLayers.dll,
2 windows 10 build 1809 (and others)- update is normal - nothing happens at startup and the launcher closes.
3. Windows 10 build 22h2 - different consequences. it may not be updated, and the launcher closes when updating. It can close without starting the game. or it may work fine. There are many cases.
The worst thing is that the developers are silent. Enough time has passed and the players can't log in to the game.

The problem with the steam client is solved, you just
need to replace the launcher with the previous one.
- launch steam
- turn off the Internet
- launch the game via Steam
- when the launcher is fully running, turn on the Internet.
- The play button lights up and you can safely play.

It sometimes happens that you need to disable Windows Defender for the duration of the launcher launch and turn it on after the game is fully launched.

Vraedlich · July 14

Verling wrote: »

I noted the same thing.
I see problems on many computers at once. Both on their own 4x and with friends and comrades from different guilds.
1. windows 7 and 8.1 update is normal - startup error with a message about AcLayers.dll,
2 windows 10 build 1809 (and others)- update is normal - nothing happens at startup and the launcher closes.
3. Windows 10 build 22h2 - different consequences. it may not be updated, and the launcher closes when updating. It can close without starting the game. or it may work fine. There are many cases.
The worst thing is that the developers are silent. Enough time has passed and the players can't log in to the game.

The problem with the steam client is solved, you just
need to replace the launcher with the previous one.
- launch steam
- turn off the Internet
- launch the game via Steam
- when the launcher is fully running, turn on the Internet.
- The play button lights up and you can safely play.

It sometimes happens that you need to disable Windows Defender for the duration of the launcher launch and turn it on after the game is fully launched.

On Win 7 I get a reference to "api-ms-win-shcore-scaling-l1-1-1.dll" missing, which isn't a dll in Win 7, only 8,1+
If I download the dll and stick it in launcher folder, the launcher loads and play lights up, but "cannot display news" and game crashes on clicking play. Repair and settings stuff all works fine. Just doesn't fix anything.
They've done this before changing one thing that requires Win 8.1+
I remember having to install an "easyfix" patch to Windows 7 once to upgrade the TLS version to 1.2 but no idea if related, there's no TLS 1.3 support for Win 7.
Doesn't really explain it not working on later Windows though.

Can't get launcher to work with internet dropping trick, or turning windows defender off.

camperov · July 14

Same problem with Win 7. After the last launcher update that happened a few days ago, the game stopped launching. I already encountered this once and the only way that helped was a complete reinstallation of the steam version of the game.

This time I first got the "api-ms-win-shcore-scaling-l1-1-1.dll" error. And after I downloaded it, I started getting the "AcLayers.dll" error. Removing "api-ms-win-shcore-scaling-l1-1-1.dll" does not return an error with it. Now the launcher crashes only with an "AcLayers.dll" error.

Another reinstallation, disabling Windows Defender, disconnecting the Internet before starting the launcher and other described methods did not help. The game works fine on my wife's laptop with Win 10. For the sake of interest, I tried to download the folder with the launcher from her laptop and move it to my PC with Windows 7. Also without any visible result.

By the way, an interesting fact. Of course, the game runs directly, without a launcher. In this regard, I wanted to switch to a non-steam version. But the installer from the official site also does not work. It just hangs in the processes for a minute or so without any reaction and then turns off.

There are a couple of threads on reddit about this problem, but people there also haven't found a solution for Windows 7.

Verling · July 14

Vraedlich wrote: »

Can't get launcher to work with internet dropping trick, or turning windows defender off.

camperov wrote: »

disconnecting the Internet before starting the launcher and other described methods did not help.

Were you able to find a previous version of the launcher file that worked? we must first replace the launcher file with the old one.
It wasn't a problem for me. As soon as I saw the problem, I made a copy from another computer.

Verling · July 14

Bethesda.net_Launcher.exe
ver 6..44.00
ZeniMax Online Studios Launcher
64,4 МБ (67 565 808 b)

with this, I'm starting in 8.1 with the internet turned off.

B100d1ust88 · July 14

I once upgraded my windows 8 to 10 to play teso because of steam, now i have to do it because of stupid launcher? Is there a way to just play this game? Why so many requirements and why i need to be on the cutting edge of software evolution to launch this game? It's just a launcher, a shortcut, a link it can be fixed easely. And ZOS can solve this problem, but they wont bcause they dont care. And for this tiny launcher bug i need to upgrade windows and get a lot of problems with the latest microsoft "product"? No, thanks...

Uristqwerty · July 14

Verling wrote: »

2 windows 10 build 1809 (and others)- update is normal - nothing happens at startup and the launcher closes.

Just because Microsoft no longer shows error details to mere users from 10 onwards doesn't mean it's not the same crash, just that you'd need to dig into system logs, flip some configuration setting in the registry to re-enable the UI, or pre-emptively attach a debugger in order to see the details and check whether they're the same or not.

Also, seems someone in the Steam thread figured out why Application Compatibility is getting involved in the first place: The launcher .exe has 'launcher' in its filename. Re-naming it is enough to avoid the crash, though Steam-only users are still out of luck, since they need Steam to run the launcher .exe, and it expects the original filename.

Vraedlich · July 14

Verling wrote: »

Vraedlich wrote: »

Can't get launcher to work with internet dropping trick, or turning windows defender off.

camperov wrote: »

disconnecting the Internet before starting the launcher and other described methods did not help.

Were you able to find a previous version of the launcher file that worked? we must first replace the launcher file with the old one.
It wasn't a problem for me. As soon as I saw the problem, I made a copy from another computer.

How would I find a previous launcher version.. lol.

Vraedlich · July 14

camperov wrote: »

Same problem with Win 7. After the last launcher update that happened a few days ago, the game stopped launching. I already encountered this once and the only way that helped was a complete reinstallation of the steam version of the game.

This time I first got the "api-ms-win-shcore-scaling-l1-1-1.dll" error. And after I downloaded it, I started getting the "AcLayers.dll" error. Removing "api-ms-win-shcore-scaling-l1-1-1.dll" does not return an error with it. Now the launcher crashes only with an "AcLayers.dll" error.

Another reinstallation, disabling Windows Defender, disconnecting the Internet before starting the launcher and other described methods did not help. The game works fine on my wife's laptop with Win 10. For the sake of interest, I tried to download the folder with the launcher from her laptop and move it to my PC with Windows 7. Also without any visible result.

By the way, an interesting fact. Of course, the game runs directly, without a launcher. In this regard, I wanted to switch to a non-steam version. But the installer from the official site also does not work. It just hangs in the processes for a minute or so without any reaction and then turns off.

There are a couple of threads on reddit about this problem, but people there also haven't found a solution for Windows 7.

Yeah I have non steam, and downloaded steam launcher in case that somehow worked, but it's all the same.
I did have an old launcher patched to high isle, but that just updated and did the same thing.
It is unusual that the steam installer works (or rather installs the game and the broken launcher) given that the one from the official site doesn't.

I really feel like this is just the quiet death of compatibility with Windows 7. They announced it wasn't officially supported anymore quite a while ago.

Verling · July 15

Vraedlich wrote: »

How would I find a previous launcher version.. lol.

Ask your friends. Ask the guild. I was given an even earlier version. Since the days when such problems were frequent. And it's still working fine. Yes, it's all based on trust.

Verling · July 15

Uristqwerty wrote: »

Verling wrote: »

2 windows 10 build 1809 (and others)- update is normal - nothing happens at startup and the launcher closes.

Just because Microsoft no longer shows error details to mere users from 10 onwards doesn't mean it's not the same crash, just that you'd need to dig into system logs, flip some configuration setting in the registry to re-enable the UI, or pre-emptively attach a debugger in order to see the details and check whether they're the same or not.

Also, seems someone in the Steam thread figured out why Application Compatibility is getting involved in the first place: The launcher .exe has 'launcher' in its filename. Re-naming it is enough to avoid the crash, though Steam-only users are still out of luck, since they need Steam to run the launcher .exe, and it expects the original filename.

the mistake is the same
P4: AcLayers.DLL
P5: 10.0.17763.292

working version
Windows 10 or 11 - v22H2
AcLayers.dll
10.0.1904

Verling · July 15

I managed to launch a new version of the launcher in Windows 8.1.
maybe this solution is suitable for other versions of windows. I can't check the windows 10 1809 version because I can't get to that computer.

I'll tell you right away so that there are no questions.
I work as a computer hardware maintenance engineer.

I replaced the old system files in windows 8.1 AcLayers.dll for new windows 10 22h2 versions 10.0.1904 (x 32 and x64)
You need to be able to do this and be sure to have a USB flash drive with a recovery environment download. If something goes wrong.

ZOS_GinaBruno · July 15

Hi all, thanks for all the info here. We'd love to get some specific log files from anyone affected.

We need the host.developer.*.log files from the Launcher folder, and the host.developer.selfupdate.log file from the selfupdate folder. These are inside the Zenimax Online folder. The default paths are these:

BAM: c:\Program Files (x86)\Zenimax Online\
Steam: c:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\
Epic: c:\Program Files (x86)\Epic Games\TheElderScrollsOnline

camperov · July 15

ZOS_GinaBruno wrote: »

Hi all, thanks for all the info here. We'd love to get some specific log files from anyone affected.

We need the host.developer.*.log files from the Launcher folder, and the host.developer.selfupdate.log file from the selfupdate folder. These are inside the Zenimax Online folder. The default paths are these:
BAM: c:\Program Files (x86)\Zenimax Online\

Steam: c:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\

Epic: c:\Program Files (x86)\Epic Games\TheElderScrollsOnline

Hi! How can I send it to you? Also I don't have a "selfupdate" folder in my Zenimax Online folder. Steam version.

Vraedlich wrote: »

Yeah I have non steam, and downloaded steam launcher in case that somehow worked, but it's all the same.
I did have an old launcher patched to high isle, but that just updated and did the same thing.
It is unusual that the steam installer works (or rather installs the game and the broken launcher) given that the one from the official site doesn't.

I really feel like this is just the quiet death of compatibility with Windows 7. They announced it wasn't officially supported anymore quite a while ago.

This is a conspiracy by Zenimax and Microsoft to force everyone to switch to Win 11

Freezbeez · July 15

ZOS_GinaBruno wrote: »

Hi all, thanks for all the info here. We'd love to get some specific log files from anyone affected.

We need the host.developer.*.log files from the Launcher folder, and the host.developer.selfupdate.log file from the selfupdate folder. These are inside the Zenimax Online folder. The default paths are these:
BAM: c:\Program Files (x86)\Zenimax Online\

Steam: c:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\

Epic: c:\Program Files (x86)\Epic Games\TheElderScrollsOnline

I'm having all the problems reported above for WIN7.

How do I send the requested host files?

Uristqwerty · July 15

Similarly unsure where to submit details, though I took the time to run through different test cases and write up what I did to trigger (or avert) the problem in each. I don't know which lines might contain identifying information, so I won't post the full files here, just the notes/summary I'd planned to attach alongside the logs.

App version lines at the start of the file:
  07/15/2025 11:01:16 Log Level: DEBUG
  07/15/2025 11:01:16 Version: 7.1.46
  07/15/2025 11:01:16 File Version: 7.1.46.0
  07/15/2025 11:01:16 Product Version: ZeniMax Online Studios Launcher 7.1.46.0

Selfupdate opens with
  07/11/2025 07:28:24 Version: 6.2.44
  07/11/2025 07:28:24 File Version: 6.2.44.0
  07/11/2025 07:28:24 Product Version: ZeniMax Online Studios Launcher 6.2.44.0

Test cases:
  First:
    Directly running a copy re-named to Bethesda.net_Lnchr.exe,
    Clicking Play (successfully),
    Closing the launcher then the game.
    No crash.
      Log lines at game launch
        07/15/2025 11:01:38 CONSOLE - Starting App with args 'Language.2=en viewer_id=false onetime_token=false product_id=215828 is_steam=false'
        07/15/2025 11:01:38 CONSOLE - --- Launching Process - Live_Prod - G:\steam\steamapps\common\Zenimax Online\The Elder Scrolls Online\game\client\eso64.exe
        07/15/2025 11:01:38 CONSOLE - [ANALYTICS] trackEvent {"event":"ProcessStart","application":"eso64.exe"}
      Log lines at launcher exit
        07/15/2025 11:01:54 CONSOLE - [ANALYTICS] trackEvent {"event":"ApplicationStop","timeLoad":13.421999999991385,"timeRunning":38.406}
        07/15/2025 11:01:55 CONSOLE - [RESTART] Starting G:\steam\steamapps\common\Zenimax Online\Launcher\RestartHelper.exe with args ' /modulename Bethesda.net_Lnchr.exe /pid 5860 /norestart'
        07/15/2025 11:01:55 CONSOLE - [INTEROP] PatcherInterop dll unloading: G:\steam\steamapps\common\Zenimax Online\Launcher\PatcherInterop.dll

  Second:
    Directly running Bethesda.net_Launcher.exe
    Immediately closing with the X button, no attempt to start game
    Crash starting RestartHelper.exe
      07/15/2025 11:03:19 CONSOLE - [ANALYTICS] trackEvent {"event":"ApplicationStop","timeLoad":3.312000000005355,"timeRunning":20.531}
      07/15/2025 11:03:19 CONSOLE - [RESTART] Starting G:\steam\steamapps\common\Zenimax Online\Launcher\RestartHelper.exe with args ' /modulename Bethesda.net_Launcher.exe /pid 3564 /norestart'
    Log cuts off here, and the next run's version data immediately starts.

  Third:
    Directly running Bethesda.net_Launcher.exe
    Clicking Play
    Crash starting eso64
      07/15/2025 11:03:58 CONSOLE - Starting App with args 'Language.2=en viewer_id=false onetime_token=false product_id=215828 is_steam=false'
      07/15/2025 11:03:58 CONSOLE - --- Launching Process - Live_Prod - G:\steam\steamapps\common\Zenimax Online\The Elder Scrolls Online\game\client\eso64.exe
    Log cuts off again

  Fourth:
    Running Bethesda.net_Launcher.exe through Steam
    Clicking Play
    Crash starting eso64
      07/15/2025 11:04:28 CONSOLE - Starting App with args 'Language.2=en viewer_id=false onetime_token=false product_id=215828 is_steam=true'
      07/15/2025 11:04:28 CONSOLE - --- Launching Process - Live_Prod - G:\steam\steamapps\common\Zenimax Online\The Elder Scrolls Online\game\client\eso64.exe
    End of file

Knowledge from attaching a debugger:
  Crash is in AcLayers.dll; Application Compatibility
    The crashing function is ElevateCreateProcess::APIHook_CreateProcessW, according to the Microsoft dll symbols that Visual Studio downloaded upon attaching to the process.
      Presumably, Application Compatibility is replacing calls to CreateProcess with its own wrapper, in order to inject a compatibility shim.
      According to a user in a steam forum discussion, this is something Windows does automatically for any .exe with 'launcher' in its filename.
    Looking at the debugger's disassembly of the Microsoft function,
      When CreateProcess' dwCreationFlags parameter has EXTENDED_STARTUPINFO_PRESENT set,
        APIHook_CreateProcessW will dereference lpStartupInfo.lpAttributeList without checking whether it's null.
        (Or to be more precise, NULL + 0x10, as it's not looking at the first field of the structure, whatever that may be.)
    According to some users Windows 10 22h2 doesn't crash there, so presumably Microsoft added their own null check in a service pack, or whatever they call it these days.

Workarounds:
  For those who can log in without steam,
    Running eso64.exe manually works. Launcher might still be able to install game updates, too?
    Re-naming/copying the launcher .exe so that it doesn't contain 'launcher' also avoids the crashes
      Good quick way to diagnose whether you're affected by this specific issue, or whether it's something else.

MageCatF4F · July 15

So technical! Glad you technicians are sharing your insight with ZOS.

An insignificant note: On one of our old Windows 7 machines the bugged up launcher will not launch the game, of course, with an immediate "Zenimax online has stopped working" crash, but just for fun I thought I'd see if it would still download the PTS patch Monday. It did.

I haven't tried playing the PTS on this old machine (via shortcut to the .exe) for reasons related to how our family plays ESO, but plan to try that eventually to make sure that the patch downloaded and the game still actually plays.

If so, and ZOS does nothing about these problems, there still may be a way to keep playing on Win 7, without monkeying around.

Note: On the other old machine we have, the launcher simply never finishes the update. It closes before finishing. No hope there.

By the way, both old machines still play the game fine (via shortcut to the .exe). They are just too old and need to be swept to the curb.

Uristqwerty · July 15

So technical!

Heh. I figure that the more work I can do to track down the problem up-front, the less dev time it'll take to fix, and so the more it's cost-effective to keep unofficially supporting older operating system versions. Only ZoS would know how many players there are on each, and how much those demographics still pay in any given month, but with any luck it's well worth the programmer time to fix. Hope it's not a problem buried deep in a third-party library, so it only takes a single line of code and a comment or two of documentation.

And if not? Writing down the details may still help fellow community members to figure out their own workarounds. Or even random strangers who find their way here through google, having problems with some other piece of software, who happen to search for the right keyword.

MageCatF4F · July 15

Yeah, I'm genuinely glad you do this. They need the help. Also my "too old" comment was sarcastic. I'm also too old.

B100d1ust88 · July 15

Where can I send the log file?

Vraedlich · July 15

MageCatF4F wrote: »

So technical! Glad you technicians are sharing your insight with ZOS.

An insignificant note: On one of our old Windows 7 machines the bugged up launcher will not launch the game, of course, with an immediate "Zenimax online has stopped working" crash, but just for fun I thought I'd see if it would still download the PTS patch Monday. It did.

I haven't tried playing the PTS on this old machine (via shortcut to the .exe) for reasons related to how our family plays ESO, but plan to try that eventually to make sure that the patch downloaded and the game still actually plays.

If so, and ZOS does nothing about these problems, there still may be a way to keep playing on Win 7, without monkeying around.

Note: On the other old machine we have, the launcher simply never finishes the update. It closes before finishing. No hope there.

By the way, both old machines still play the game fine (via shortcut to the .exe). They are just too old and need to be swept to the curb.

I had this bug and the PTS client installed, which updated but pressing Play did the exact same thing.

camperov · July 16

Verling wrote: »

Were you able to find a previous version of the launcher file that worked? we must first replace the launcher file with the old one.
It wasn't a problem for me. As soon as I saw the problem, I made a copy from another computer.

Unfortunately, this method didn't work for me. I found an old version from a friend who hadn't played ESO for a long time. When completely replacing the folder with the launcher, it only has an "install" button. And when the Internet is turned on, it of course updates immediately. Replacing only the launcher file also didn't lead to a result - the launcher just hangs in processes for a while and turns off.

camperov · July 16

ZOS_GinaBruno wrote: »

Hi all, thanks for all the info here. We'd love to get some specific log files from anyone affected.

We need the host.developer.*.log files from the Launcher folder, and the host.developer.selfupdate.log file from the selfupdate folder. These are inside the Zenimax Online folder. The default paths are these:
BAM: c:\Program Files (x86)\Zenimax Online\

Steam: c:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\

Epic: c:\Program Files (x86)\Epic Games\TheElderScrollsOnline

Here is a link to the latest logs you requested:
https://drive.google.com/drive/folders/12xLhqGuHnhBGn4wUlzJD4c0b5qVe8Fud

I'm not sure if it's possible to post links to Google Drive here. If not, please delete my post.

Verling · July 16

camperov wrote: »

Verling wrote: »

Were you able to find a previous version of the launcher file that worked? we must first replace the launcher file with the old one.
It wasn't a problem for me. As soon as I saw the problem, I made a copy from another computer.

Unfortunately, this method didn't work for me. I found an old version from a friend who hadn't played ESO for a long time. When completely replacing the folder with the launcher, it only has an "install" button. And when the Internet is turned on, it of course updates immediately. Replacing only the launcher file also didn't lead to a result - the launcher just hangs in processes for a while and turns off.

maybe the version is too old
there is another solution. I wrote about him above.

I replaced the old system files in windows 8.1 AcLayers.dll for new windows 10 22h2 versions 10.0.1904 (x 32 and x64)
You need to be able to do this and be sure to have a USB flash drive with a recovery environment download. If something goes wrong.

MageCatF4F · July 16

Vraedlich wrote: »

MageCatF4F wrote: »

So technical! Glad you technicians are sharing your insight with ZOS.

An insignificant note: On one of our old Windows 7 machines the bugged up launcher will not launch the game, of course, with an immediate "Zenimax online has stopped working" crash, but just for fun I thought I'd see if it would still download the PTS patch Monday. It did.

I haven't tried playing the PTS on this old machine (via shortcut to the .exe) for reasons related to how our family plays ESO, but plan to try that eventually to make sure that the patch downloaded and the game still actually plays.

If so, and ZOS does nothing about these problems, there still may be a way to keep playing on Win 7, without monkeying around.

Note: On the other old machine we have, the launcher simply never finishes the update. It closes before finishing. No hope there.

By the way, both old machines still play the game fine (via shortcut to the .exe). They are just too old and need to be swept to the curb.

I had this bug and the PTS client installed, which updated but pressing Play did the exact same thing.

I just tried playing the PTS on our Win 7 machine that has this problem we are talking about with the launcher by direct shortcut to the .exe -

And...I was able to play the PTS just fine.

I'm sure I was on PTS because it had that latest disgusting nerf to NightBlade where Grim Focus has what used to be good replaced by Major Prophecy and Savagery - very useful that for an oakensoul NB /s. But I digress.

The launcher downloaded and installed the latest PTS patch, even though it is incapable of...actually launching the game. The game can still then be played by shortcut to the .exe.

Vraedlich · July 17

MageCatF4F wrote: »

I just tried playing the PTS on our Win 7 machine that has this problem we are talking about with the launcher by direct shortcut to the .exe -

And...I was able to play the PTS just fine.

I'm sure I was on PTS because it had that latest disgusting nerf to NightBlade where Grim Focus has what used to be good replaced by Major Prophecy and Savagery - very useful that for an oakensoul NB /s. But I digress.

The launcher downloaded and installed the latest PTS patch, even though it is incapable of...actually launching the game. The game can still then be played by shortcut to the .exe.

This is something that was established very early on. Yes the direct link to the client works.

If the launcher can update the main client still, then this problem is a minor inconvenience at best.

ZOS_GinaBruno · July 17

Ack, sorry all. Apparently there's a bug on the forums that is not allowing anyone to upload files in existing threads. We do have a custom launcher that we built for you all to try but unfortunately, the zip file is too big to upload here. We're working on another solution, though. Sit tight and we should have it available soon!

S_Northman · July 17

@ZOS_GinaBruno

Hello

While you have a look at the launcher, do not forget the 'unable to laod skin' error which affects mainly players with an Intel Core i9 and W11 24H2.
https://forums.elderscrollsonline.com/en/discussion/674955/summary-unable-to-load-skin-error#latest

I have a ticket open for several weeks (monthes ?), last answer: transmiited to the devs. No news and no upgrade.

I should add that not only this bug prevents the launcher to start, but also this bug affects as well the Steam installer and the ESO installer (donwloaded from ESO account), so that players are not able to install or reinstall the game, either from Steam, either with the ESO installer.

ZOS_GinaBruno · July 17

Just posted links to some zip files here over in this thread: https://forums.elderscrollsonline.com/en/discussion/680787/launcher-issues-click-here-for-zip-files

MageCatF4F · July 17

Vraedlich wrote: »

MageCatF4F wrote: »

I just tried playing the PTS on our Win 7 machine that has this problem we are talking about with the launcher by direct shortcut to the .exe -

And...I was able to play the PTS just fine.

I'm sure I was on PTS because it had that latest disgusting nerf to NightBlade where Grim Focus has what used to be good replaced by Major Prophecy and Savagery - very useful that for an oakensoul NB /s. But I digress.

The launcher downloaded and installed the latest PTS patch, even though it is incapable of...actually launching the game. The game can still then be played by shortcut to the .exe.

This is something that was established very early on. Yes the direct link to the client works.

If the launcher can update the main client still, then this problem is a minor inconvenience at best.

I'm not sure what you are getting at. Everyone knows the direct link to the client works, and has for years. I was checking to see if the launcher was successful in installing the patch or not by actually running the game.

Just trying to be helpful. I'll stop doing that.