Forum Discussion
Solved
WIndows Insider 26016 and Elder Scrolls Online Launcher
After upgrading Windows 11 Canary from 26010 to 26016, the launcher for your Elder Scrolls Online game stopped launching it. Pressing the RUN button in the launcher does not start the game (the wheel spins for a while, and then the RUN button returns to its original state without starting the game). Using the repair and reinstall option for the entire game has no effect. I'd like to mention that this problem hasn't occurred in any previous Canary/Dev build before, and I'm an Insider who has been playing this game for several years.
The latest build 26040 fixes problems with running Elder Scrolls Online. The game client (launcher) runs it, and the game itself - from what I can see - works properly. Congratulations on accurately targeting the source of the error.
15 Replies
Tested on a desktop (Ryzen 9 5950x with EVGA 3080) and 2 different laptops (Asus Rog strix scar R7-5800H with RTX 3080 and old MSI Gt72 Dominator Pro with RTX 980 and i7-6700hq)
The latest build 26040 fixes problems with running Elder Scrolls Online. The game client (launcher) runs it, and the game itself - from what I can see - works properly. Congratulations on accurately targeting the source of the error.So far, all responses to reports end with advice to remove the insider versions of Windows. This was, among other things, the position presented to me by Bethesda support owned by Microsoft.
This is paranoia. In official communications, you call on people to report situations that you have not done anything about for almost a month, and your representatives suggest leaving the insider program.
With all due respect, I think that if the problem concerns YOUR game, for which you also charge a subscription, it should look completely different. You should URGENTLY ask the programmers to stand up and solve this problem, especially since it coincides with the Christmas period and its a money for you. And if someone does not understand the subliminal message, let me put it simply - Windows was successful based on, among others, wide game support, so since subsequent Canary compilations are causing more and more problems with this, it seems to me that you should skip the new bells and whistles and focus on games problem more seriously.You have to wonder if either company is even bothering to look into why eso64.exe is dying.
- I think we expect too much. After reporting the described problem, I received a reply telling me to skip the insider version and go back to regular Windows. What's the point of this whole program if a report generates such a "solution".
Faulting application name: eso64.exe, version: 1.0.0.1, time stamp: 0x657a3f0d
Faulting module name: eso64.exe, version: 1.0.0.1, time stamp: 0x657a3f0d
Exception code: 0xc0000005
Fault offset: 0x000000000221400e
Faulting process id: 0x5AE8Windows 11 Insider Preview Build 26020 (Canary Channel)
Problem still exist on 26020 build.
Oh come on, you really can't kick your own studio (Bethesda) since December 15th, which is pulling a subscription from people to find out the source of the problem? Oh yes, they're probably still patching the content-deprived Starfield....
Same here. Tried enabling the firewall,and security perimeters. No joy. reinstalled previous updated version. Fenris
- Same problem on my laptop after upgrading from Win 11 26010 to 26016
- I would like to add that the eso64.exe executable file also does not run the game.
