ESO Launcher Crashes on Update 9/04/2018

Axtremulus · September 2018

Re-downloading hasn't helped. Still no sign of a solution from Zenimax.

I was going to buy the CE version of the Cyrodiil DLC, guess not anymore.
I was also going to log in everyday this month, now I can't (the people asking about this were never answered).
I was going to keep my subscription up indefinitely, but I will not now that I can't even play the game.

Elsonso · September 2018

technogeek64 wrote: »

There are also people in the thread who are having the problem on Verizon. Regardless, if some people are getting blocked and some are not it is not simply an ISP problem. Especially since there are people who are able to download fine on one device and unable to download on another device using the same connection point. This is not something ZOS can (or should) be blaming solely on the ISPs. If it has been working flawlessly since launch for people, on the same ISP, and they make an update that suddenly breaks it...that is not an ISP issue...ZOS effed something up in the update.

The Verizon people never posted details here in the thread. The only Verizon person who posted anything was the OP, and the details there were pretty thin. Basically, all I was able to determine from the OP was that he was using Verizon (nee MCI Communications). The most detailed information came from the guy having problems with Spectrum Internet (nee Roadrunner).

You think that ZOS messed up the update, but all of us Windows people are using the same launcher, the same downloader, and the same patcher. All of them were released back in May, so nothing has changed there. Akamai is the content distribution system that we get our patch data files from. The same place we got the patch before this, so nothing has changed there, and if they were a problem, ZOS would not have called them an ISP. The only thing that has changed is the patch data itself, and the ISPs should not be interfering with that. They do seem to be selectively messing with that, based on both what ZOS has said and what people have presented in here, and that seems to be the ISP issue that is causing the problem for some people.

Anyway, this thread is about an ISP problem, and that is pretty clear, based on what the forum users have said.

Whether there is something that can be done with the Bethesda Launcher to bypass what the ISPs are doing to cause problems is something that they are going to have to take a closer look at. If they release a new launcher in the near future, maybe they have come up with something that will help keep the ISPs from breaking patches.

pzschrek · September 2018

I have the same ISP at work and at home, my work computer takes the update but my home one doesn't. Guess where it needs to work?

I would think they'd design their game better. Until then, my dollars and time will be elsewhere.

cbrking · September 2018

lordrichter wrote: »

technogeek64 wrote: »

There are also people in the thread who are having the problem on Verizon. Regardless, if some people are getting blocked and some are not it is not simply an ISP problem. Especially since there are people who are able to download fine on one device and unable to download on another device using the same connection point. This is not something ZOS can (or should) be blaming solely on the ISPs. If it has been working flawlessly since launch for people, on the same ISP, and they make an update that suddenly breaks it...that is not an ISP issue...ZOS effed something up in the update.

The Verizon people never posted details here in the thread. The only Verizon person who posted anything was the OP, and the details there were pretty thin. Basically, all I was able to determine from the OP was that he was using Verizon (nee MCI Communications). The most detailed information came from the guy having problems with Spectrum Internet (nee Roadrunner).

You think that ZOS messed up the update, but all of us Windows people are using the same launcher, the same downloader, and the same patcher. All of them were released back in May, so nothing has changed there. Akamai is the content distribution system that we get our patch data files from. The same place we got the patch before this, so nothing has changed there, and if they were a problem, ZOS would not have called them an ISP. The only thing that has changed is the patch data itself, and the ISPs should not be interfering with that. They do seem to be selectively messing with that, based on both what ZOS has said and what people have presented in here, and that seems to be the ISP issue that is causing the problem for some people.

Anyway, this thread is about an ISP problem, and that is pretty clear, based on what the forum users have said.

Whether there is something that can be done with the Bethesda Launcher to bypass what the ISPs are doing to cause problems is something that they are going to have to take a closer look at. If they release a new launcher in the near future, maybe they have come up with something that will help keep the ISPs from breaking patches.

@lordrichter I posted some elaborate details as well as the steps I took as well as posted some speculative guesses.

My logs were too large to paste here, but yes certain URL's/IP's appeared to not be responsive, I did more but didn't really post everything I did such as tracert, pings, and whois lookups. It just seems like some of the URL's are dead or simply being blocked. I more highly suspect something with akamai or the way the URL is launched or generated.

If the URL is even once character off it would be dead, but unfortunately we have no way to know how they designed the patcher and URL's.

Rather than spending time on why, the best thing to do is just do the manual file patch as multiple have posted or if you have access to a vpn try that as many others have.

If nothing else, I guess you are SOL until they fix it.

cbrking · September 2018

You could try using this to confirm what akamai is doing:

See Admintool. If that theory is correct and the ISP is blocking an akamai server, then you might see something there. Since I fixed the issue I can't recreate it currently and check this out.

https://www.akamai.com/us/en/products/media-delivery/download-manager-faq.jsp

Brewergnome · September 2018

I posted as a Verizon user. Got it to work with the manual method.

Unfortunately, I just gave a friend a copy as a gift. We can't get his downloader to work at all. It stalls out like the rest of ours, but it's on the very first file and manually downloading doesn't seem to repair the problem. And if it did, they're many many piece files. It would take forever to do them manually. Not sure what's different about his clean new Windows install vs my Windows steam re-install (which took 5 patch files, but then was fine).

technogeek64 · September 2018

Brewergnome wrote: »

I posted as a Verizon user. Got it to work with the manual method.

Unfortunately, I just gave a friend a copy as a gift. We can't get his downloader to work at all. It stalls out like the rest of ours, but it's on the very first file and manually downloading doesn't seem to repair the problem. And if it did, they're many many piece files. It would take forever to do them manually. Not sure what's different about his clean new Windows install vs my Windows steam re-install (which took 5 patch files, but then was fine).

I had to do a fresh install because I'd uninstalled it (before discovering this thread). It was a LONG process to manually download each of the files.

Aquanova · September 2018

I cancelled my ESO plus membership over this fiasco because I find it hard to believe that at least 2 ISP'S simultaneously started blocking programs on the same day and right after a patch maintenance update. I'm on spectrum btw, the only game in town in hawaii (Hawaiian Tel is too slow for this game).

It seems more likely that ZOS added something that would be blocked by our ISP'S to their update that made us have to preform work arounds to get this game to play again, but regardless, this is unacceptable, I will not spend anymore money on this game. This is the second time ZOS has botched their code, even if it only effects a small percentage of us.

I will continue to play the base game and the 2 expansions (cough, cough) that I paid for but that's it, I've had enough of ZOS fumbling.

If it weren't for good friends playing this game I'd be long gone.

Elsonso · September 2018

Aquanova wrote: »

I cancelled my ESO plus membership over this fiasco because I find it hard to believe that at least 2 ISP'S simultaneously started blocking programs on the same day and right after a patch maintenance update. I'm on spectrum btw, the only game in town in hawaii (Hawaiian Tel is too slow for this game).

It seems more likely that ZOS added something that would be blocked by our ISP'S to their update that made us have to preform work arounds to get this game to play again, but regardless, this is unacceptable, I will not spend anymore money on this game. This is the second time ZOS has botched their code, even if it only effects a small percentage of us.

It is because it is mainly two ISPs, and not even everyone on those ISPs, that I think it is more of a localized ISP problem than a ZOS, Bethesda, or Akamai problem, which would be much more widespread.

I agree that it is possible that something ZOS did could have triggered this, but if that is the case, it just sounds like a couple of ISPs are sensitive to whatever it is. Once the ISP fixes whatever it is they are doing to block the patch, it will resume working. That does not mean that ZOS did anything wrong or that ZOS needs to fix it, or is even able to.

I also have Spectrum Internet, but do not have this problem. So far, it seems to be limited to former TWC west coast infrastructure, and that ain't me. (Thankfully) However, I watch all this with interest because I don't want my ISP blocking my content, deliberately or accidentally.

Sephirajo · September 2018

I was having the same problem and the VPN work around fixed it for me. This is odd, that it seems to be ISP related.

devlyn1 · September 2018

lordrichter wrote: »

technogeek64 wrote: »

There are also people in the thread who are having the problem on Verizon. Regardless, if some people are getting blocked and some are not it is not simply an ISP problem. Especially since there are people who are able to download fine on one device and unable to download on another device using the same connection point. This is not something ZOS can (or should) be blaming solely on the ISPs. If it has been working flawlessly since launch for people, on the same ISP, and they make an update that suddenly breaks it...that is not an ISP issue...ZOS effed something up in the update.

The Verizon people never posted details here in the thread. The only Verizon person who posted anything was the OP, and the details there were pretty thin. Basically, all I was able to determine from the OP was that he was using Verizon (nee MCI Communications). The most detailed information came from the guy having problems with Spectrum Internet (nee Roadrunner).

You think that ZOS messed up the update, but all of us Windows people are using the same launcher, the same downloader, and the same patcher. All of them were released back in May, so nothing has changed there. Akamai is the content distribution system that we get our patch data files from. The same place we got the patch before this, so nothing has changed there, and if they were a problem, ZOS would not have called them an ISP. The only thing that has changed is the patch data itself, and the ISPs should not be interfering with that. They do seem to be selectively messing with that, based on both what ZOS has said and what people have presented in here, and that seems to be the ISP issue that is causing the problem for some people.

Anyway, this thread is about an ISP problem, and that is pretty clear, based on what the forum users have said.

Whether there is something that can be done with the Bethesda Launcher to bypass what the ISPs are doing to cause problems is something that they are going to have to take a closer look at. If they release a new launcher in the near future, maybe they have come up with something that will help keep the ISPs from breaking patches.

I repeat one of my comments then. Why did it work on my desktop and not the laptop if they are both connected to the same router and ISP.? If it was an ISP issue only then wouldn't both my PCs be down? Both are running same windows and same virus protection.

Not saying they are wrong but there has to be more because yes, I was able to remedy it by using a cell phone hot spot to download.

devlyn1 · September 2018

Sephirajo wrote: »

I was having the same problem and the VPN work around fixed it for me. This is odd, that it seems to be ISP related.

what vpn did you use? Got a feeling I will need it in the future

Elsonso · September 2018

devlyn1 wrote: »

I repeat one of my comments then. Why did it work on my desktop and not the laptop if they are both connected to the same router and ISP.? If it was an ISP issue only then wouldn't both my PCs be down? Both are running same windows and same virus protection.

Not saying they are wrong but there has to be more because yes, I was able to remedy it by using a cell phone hot spot to download.

You never provided enough information to draw a conclusion about your situation. Sorry.

LegacyDM · September 2018

ZOS_GinaBruno wrote: »

We’ve reached out to the internet providers who are blocking the associated files, and at this point, it’s up to them to resolve the problem.

sirano wrote: »

Same here in hawaii and with Spectrum, they say they have nothing to do with it.

lordrichter wrote: »

devlyn1 wrote: »

I repeat one of my comments then. Why did it work on my desktop and not the laptop if they are both connected to the same router and ISP.? If it was an ISP issue only then wouldn't both my PCs be down? Both are running same windows and same virus protection.

Not saying they are wrong but there has to be more because yes, I was able to remedy it by using a cell phone hot spot to download.

You never provided enough information to draw a conclusion about your situation. Sorry.

Are you serious? Unless the guy is a lair which he's is not. How much proof is enough for you? Who are you defending here? Another guy has contacted SPECTRUM ISP and they have denied having the issue.

Bottom line folks. Who are you going to believe? ZOS with their horrendous track record for botching things up and owning up to their mistakes? A company that has chronic server performance issues, bugs, lag, loading screens, and errors? Or legit business service providers serving 15+ million customers nationwide. Ranging from businesses to personal residential homes. The fact that Gina pointed it to an ISP issue but provided no amplifying details on the nature of the issue and ignores questions on how we should go about troubleshooting it with our ISPs is all the information I need to know about what's going on here.

If ZOS reached out to the ISPs and concluded the problem is on their end, what is the problem? What should I discuss with my ISP? And why is my ISP denying their is a problem?

Crimsonorion · September 2018

So I managed to fix my problem a few days ago using the manual method, but got another patch coming up it seems and..still nothing, can we get some kind of update on Monday?

Elsonso · September 2018

LegacyDM wrote: »

ZOS_GinaBruno wrote: »

We’ve reached out to the internet providers who are blocking the associated files, and at this point, it’s up to them to resolve the problem.

sirano wrote: »

Same here in hawaii and with Spectrum, they say they have nothing to do with it.

lordrichter wrote: »

devlyn1 wrote: »

I repeat one of my comments then. Why did it work on my desktop and not the laptop if they are both connected to the same router and ISP.? If it was an ISP issue only then wouldn't both my PCs be down? Both are running same windows and same virus protection.

Not saying they are wrong but there has to be more because yes, I was able to remedy it by using a cell phone hot spot to download.

You never provided enough information to draw a conclusion about your situation. Sorry.

Are you serious? Unless the guy is a lair which he's is not. How much proof is enough for you? Who are you defending here? Another guy has contacted SPECTRUM ISP and they have denied having the issue.

Bottom line folks. Who are you going to believe? ZOS with their horrendous track record for botching things up and owning up to their mistakes? A company that has chronic server performance issues, bugs, lag, loading screens, and errors? Or legit business service providers serving 15+ million customers nationwide. Ranging from businesses to personal residential homes. The fact that Gina pointed it to an ISP issue but provided no amplifying details on the nature of the issue and ignores questions on how we should go about troubleshooting it with our ISPs is all the information I need to know about what's going on here.

If ZOS reached out to the ISPs and concluded the problem is on their end, what is the problem? What should I discuss with my ISP? And why is my ISP denying their is a problem?

Yeah, I am serious.

I go with ZOS, this time. This is based on what I read in here, some behind the scenes investigation, and what I have been able to figure out about how ZOS distributes patches. Here is how I lay this out...

1. The launcher that ZOS uses, which as near as I can tell is a licensed product that has been re-branded By Bethesda and used by ZOS, is months old. This gets used almost weekly for patches, and it is common to all the Windows launchers. It is so widely used, and so old, that it is not reasonable to start off assuming that something broke because of the patch.

2. I know ZOS uses Akamai for patch downloads. This means that ZOS is not running some box in the corner to serve up patch files. Akamai is a big, serious, business. While it is possible for the Akamai stuff to get screwed up, this is not the first place I would go to diagnose a problem on the scale that we have here. If Akamai were the problem, this problem would be huge, impacting thousands of people. I don't get the sense that it is that large, so Akamai is not somewhere that I would go first to find the problem.

3. ZOS patch files are just data files. Just a guess, but I figure they are just big "ZIP files" that the downloader gets from Akamai, and the patcher uses to update the game. All ZOS does is stage these on Akamai servers somewhere and when people go to Akamai to get the file, Akamai just delivers it. This is really the only place where I think any "blame" can hit ZOS, and this would be tangential. Data flles should not cause a problem when transmitted across the internet. Sadly, I know that this is not always true, which is why here is the first place I consider ZOS. They may have crafted a patch file that is causing problems in transit. That isn't something that ZOS can predict and correct in advance.

4. I don't know why people are going to 142.129.4.75 and 151.205.0.23. Maybe ZOS knows, but they have more information than I do. All I know is that the first one is owned by Spectrum Internet, the other by Verizon. Two ISPs that seem to be having troubles with downloading the patch files. I am on Spectrum Internet, and I downloaded my patch files from Akamai, not Spectrum. I have no idea why people in here are trying to download patch files from some server owned by their ISP. To me, that is like trying to download the patch from your toaster. Unless you have one damn smart toaster, that ain't gonna work.

142.129.4.75 - AS20001 ROADRUNNER-WEST - Time Warner Cable Internet LLC (Spectrum)
151.205.0.23 - AS701 UUNET - MCI Communications Services (Verizon)

I want to make this clear: Every single time someone comes forward in this thread and says they cannot install the patch, and then say they are either Verizon or Spectrum, but provide no contrary detailed information (IP addresses, logs, etc) , they validate what ZOS says.

6. I don't know why that guy had a laptop that did not work, while the PC did work. Like I said, not enough information. Maybe they provided the information to ZOS. I hope they provided it to ZOS. For both computers. Without that information, I cannot even tell if they are having the same problem as the rest of the people. For me it is an outlier, pending further information. This is likely to be solved long before anyone cares about "further information" here in the thread.

ZOS has already contacted the ISPs in question, which I would assume are Spectrum and Verizon, and explained to them what they saw from all the log files. This is not the first time ZOS has had to contact some internet company that has been causing problems with the game, and I am sure it won't be the last.

corvair62 · September 2018

Well I'm in the Mid West and have Media Com as my ISP. I have ESO on Steam and on Windows. I was able to make it work on Windows by deleting and reinstalling, but not on Steam. So if it's an ISP issue, Why would it work for one and not the other. Both of mine are one the same PC, but under different drives. I won't get a reasonable answer, just more of " its your ISP" I was born at night, but not last night. I need a better answer than that. My MediaCom rep said it's not an issue on there end. I even paid to have one of there Techs come and check on my end. So again Not my ISP

Sephirajo · September 2018

devlyn1 wrote: »

Sephirajo wrote: »

I was having the same problem and the VPN work around fixed it for me. This is odd, that it seems to be ISP related.

what vpn did you use? Got a feeling I will need it in the future

TunnelBear. I'm poor as *** so had to go free.

corvair62 · September 2018

Well with todays update 9-10-2018, I'm having launcher issues again. Still getting partial downloads. Again I have Media Com, and two versions of game. Today Steam downloaded fine and starts, but Windows is partial and will not. Same ISP for both and same pc for both. Any one else getting this still?

Shantu · September 2018

Add my name to the list. I'm a Mediacom customer. I haven't been able to start the launcher without loading Firefox also for months. Now this morning when I get the launcher to run, it freezes at 19% downloading and then just disappears. I have 6 crashes and counting this morning, all reporting the same thing in Event Viewer:

Faulting application name: Bethesda.net_Launcher.exe, version: 3.6.10.0, time stamp: 0x59038a2e
Faulting module name: libcef.dll, version: 1.1248.785.0, time stamp: 0x515e1207
Exception code: 0x80000003
Fault offset: 0x009ee926
Faulting process id: 0x2228
Faulting application start time: 0x01d44900a957f776
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\Launcher\Bethesda.net_Launcher.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\Launcher\libcef.dll
Report Id: a6a9640f-5eb6-4e74-8d82-b23423411984
Faulting package full name:
Faulting package-relative application ID:

Come on...really?!?

corvair62 · September 2018

HEY ZOS, when you ganna fix this????????????????????

Elsonso · September 2018

Shantu wrote: »

Add my name to the list. I'm a Mediacom customer. I haven't been able to start the launcher without loading Firefox also for months. Now this morning when I get the launcher to run, it freezes at 19% downloading and then just disappears. I have 6 crashes and counting this morning, all reporting the same thing in Event Viewer:

Faulting application name: Bethesda.net_Launcher.exe, version: 3.6.10.0, time stamp: 0x59038a2e
Faulting module name: libcef.dll, version: 1.1248.785.0, time stamp: 0x515e1207
Exception code: 0x80000003
Fault offset: 0x009ee926
Faulting process id: 0x2228
Faulting application start time: 0x01d44900a957f776
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\Launcher\Bethesda.net_Launcher.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\Launcher\libcef.dll
Report Id: a6a9640f-5eb6-4e74-8d82-b23423411984
Faulting package full name:
Faulting package-relative application ID:

Come on...really?!?

libcef.dll error. This is not sounding like the same thing. Is anyone else having an exception in libcef.dll?

(This is Chromium, which I think is what they use to display the "advertising" in the launcher. I do not know what role it might play beyond that. ZOS has to answer for that one.)

Mykelorcrist · September 2018

Issue again this week and I am om Verizon. Same as last time, for some odd reason the file gets downloaded but is marked as partial then a whole series of errors related to the a Verizon IP not being in the whitelist:

09/10/2018 08:34:57 game_playe: Choose next (1:0/71/0) [68:118]
09/10/2018 08:34:57 game_playe: Building full request off index (71:1)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 http://127.0.0.1:57180/applications.js (1932): ---- WebGet Error: http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01 65.216.231.146:80 3 956 ----
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 http://127.0.0.1:57180/applications.js (1932): ---- WebGet Error: http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01 65.216.231.146:80 3 956 ----
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 http://127.0.0.1:57180/applications.js (1932): ---- WebGet Error: http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01 65.216.231.146:80 3 956 ----
09/10/2018 08:34:57 http://127.0.0.1:57180/applications.js (1932): ---- WebGet Error: http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01 65.216.231.146:80 3 956 ----
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 http://127.0.0.1:57180/applications.js (2381): ---- blocking error 956 from being sent again ----
09/10/2018 08:34:57 http://127.0.0.1:57180/analytics.js (214): ---- analytics disabled ----
09/10/2018 08:34:57 http://127.0.0.1:57180/applications.js (1932): ---- WebGet Error: http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01 65.216.231.146:80 3 956 ----
09/10/2018 08:34:57 game_playe: Piece passes authentication [69] [49 left] [6193k]
09/10/2018 08:34:57 game_playe: Filling request queue sequentially (72:0)
09/10/2018 08:34:57 game_playe: Choose next (1:0/72/0) [69:118]
09/10/2018 08:34:57 game_playe: Building full request off index (72:1)
09/10/2018 08:34:57 game_playe: Piece passes authentication [70] [48 left] [6065k]
09/10/2018 08:34:57 game_playe: Filling request queue sequentially (73:0)
09/10/2018 08:34:57 game_playe: Choose next (1:0/73/0) [70:118]
09/10/2018 08:34:57 game_playe: Building full request off index (73:1)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 WebGet Error: (http://151.205.4.5:80/data/01c3227a274f7192/live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (151.205.4.5:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://151.205.4.5:80/data/01c3227a274f7192/live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (151.205.4.5:80) (3:956)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 WebGet Error: (http://151.205.4.5:80/data/01c3227a274f7192/live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (151.205.4.5:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://151.205.4.5:80/data/01c3227a274f7192/live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (151.205.4.5:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://151.205.4.5:80/data/01c3227a274f7192/live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (151.205.4.5:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)
09/10/2018 08:34:57 Hostname not found in whitelist (151.205.4.5)

Manual method worked again however

corvair62 · September 2018

Mykelorcrist wrote: »

Issue again this week and I am om Verizon. Same as last time, for some odd reason the file gets downloaded but is marked as partial then a whole series of errors related to the a Verizon IP not being in the whitelist:

Manual method worked again however

Can you link the url please. For some reason i cant get it to pull up.

Shantu · September 2018

lordrichter wrote: »

Shantu wrote: »

Add my name to the list. I'm a Mediacom customer. I haven't been able to start the launcher without loading Firefox also for months. Now this morning when I get the launcher to run, it freezes at 19% downloading and then just disappears. I have 6 crashes and counting this morning, all reporting the same thing in Event Viewer:

Faulting application name: Bethesda.net_Launcher.exe, version: 3.6.10.0, time stamp: 0x59038a2e
Faulting module name: libcef.dll, version: 1.1248.785.0, time stamp: 0x515e1207
Exception code: 0x80000003
Fault offset: 0x009ee926
Faulting process id: 0x2228
Faulting application start time: 0x01d44900a957f776
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\Launcher\Bethesda.net_Launcher.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Zenimax Online\Launcher\libcef.dll
Report Id: a6a9640f-5eb6-4e74-8d82-b23423411984
Faulting package full name:
Faulting package-relative application ID:

Come on...really?!?

libcef.dll error. This is not sounding like the same thing. Is anyone else having an exception in libcef.dll?

(This is Chromium, which I think is what they use to display the "advertising" in the launcher. I do not know what role it might play beyond that. ZOS has to answer for that one.)

Well, like others in this thread, I got the the launcher to work by installing a VPN. Once installed, the launcher completed downloading the patch files and now functions normally...though "normal" for me means I have to boot up Firefox every time to get the launcher past the "Loading..." screen.

Thanks to those who came up with this suggestion.

Elsonso · September 2018

Mykelorcrist wrote: »

09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)

I want to draw attention to this line in the above log.

The launcher is apparently trying to install ESO is using DNS to resolve "live.patcher.elderscrollsonline.com" and getting 65.216.231.146, and that is a Verizon website.

65.216.231.146 AS701 UUNET - MCI Communications Services

Why is Verizon redirecting the launcher to a Verizon web server? Is Verizon DNS being used? Maybe it is time to get the real IP address for "live.patcher.elderscrollsonline.com" and update hosts to bypass DNS?

(Edit... not a good long term solution, but one resolution for "live.patcher.elderscrollsonline.com" is 23.219.38.11)

Mykelorcrist · September 2018

lordrichter wrote: »

Mykelorcrist wrote: »

09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)

I want to draw attention to this line in the above log.

The launcher is apparently trying to install ESO is using DNS to resolve "live.patcher.elderscrollsonline.com" and getting 65.216.231.146, and that is a Verizon website.

65.216.231.146 AS701 UUNET - MCI Communications Services

Why is Verizon redirecting the launcher to a Verizon web server? Is Verizon DNS being used? Maybe it is time to get the real IP address for "live.patcher.elderscrollsonline.com" and update hosts to bypass DNS?

(Edit... not a good long term solution, but one resolution for "live.patcher.elderscrollsonline.com" is 23.219.38.11)

I agree, the issue seems to be in the Verizon FIOS DNS but it is very odd that the file does download, the size matches that of the actual file but it is still marked as "partial" when the errors begin. Unfortunately, simply removing the ".partial" tag and running the launcher did not correct the issue.

Another interesting observation. I fired up my Verizon Wireless MiFi and the patch worked fine on one of the laptops my wife and I use, I had already manually patched the other. Verizon Wireless is on a different IP range than FIOS and may use a different DNS

UPDATE:

I used nslookup on both Verizon FIOS and Verizon Wireless MiFi to get the IP address for live.patcher.elderscrollsonline.com and both gave 65.216.231.146 as the IP. However using ping I got 23.219.38.11 and using tracert I got 92.242.140.21. No idea at all why I get three different IPs for the same host.

Oh and trying to bypass the DNS by placing 23.219.38.11 in Windows/System32/drivers/etc/hosts on a third laptop that needed to be patched did not solve the problem.

Nhines · September 2018

So I had the same issue. It seems a lot of the people having this issue are with Verizon, but I'm with Mediacom, so it could just be a common routing point. Tried fixing it by manually downloading the patches, which did progress the patching. I then loaded up my VPN (PIA Chicago in my case) and it patched without problem.

I would have posted/PM'd my host.developer.log, but it was around 450MB, so yeah, no.

Elsonso · September 2018

Mykelorcrist wrote: »

lordrichter wrote: »

Mykelorcrist wrote: »

09/10/2018 08:34:57 WebGet Error: (http://live.patcher.elderscrollsonline.com/products/eso/874DCDCF-C40C-4956-92FE-E39B8DC4764E/game_player/game_player_294to295/game_player_294to295.z01) (65.216.231.146:80) (3:956)

I want to draw attention to this line in the above log.

The launcher is apparently trying to install ESO is using DNS to resolve "live.patcher.elderscrollsonline.com" and getting 65.216.231.146, and that is a Verizon website.

65.216.231.146 AS701 UUNET - MCI Communications Services

Why is Verizon redirecting the launcher to a Verizon web server? Is Verizon DNS being used? Maybe it is time to get the real IP address for "live.patcher.elderscrollsonline.com" and update hosts to bypass DNS?

(Edit... not a good long term solution, but one resolution for "live.patcher.elderscrollsonline.com" is 23.219.38.11)

I agree, the issue seems to be in the Verizon FIOS DNS but it is very odd that the file does download, the size matches that of the actual file but it is still marked as "partial" when the errors begin. Unfortunately, simply removing the ".partial" tag and running the launcher did not correct the issue.

Another interesting observation. I fired up my Verizon Wireless MiFi and the patch worked fine on one of the laptops my wife and I use, I had already manually patched the other. Verizon Wireless is on a different IP range than FIOS and may use a different DNS

You can try to set the DNS to Google or Open DNS. I use a variety of them. My router is set to one, and my PCs are often set to different ones. I use Google and Open DNS, as well as the ISP.

People ask why browsers work, or why one computer works and one does not. There is really no good answer to this, and all of them sound like conspiracy theories. When the ISP injects itself between you and the patch files, they can really do anything they want, no matter what assurances they might give. They can block non-browser access, under the assumption that malware is downloading files. They can be enforcing some sort of bandwidth controls to block large file transfers at prime time. They can be doing some sort of virus scanning to prevent malware from being downloaded. Once they are in the middle, they are in complete control. The field of possibilities, real or imagined, is simply too large.

Llyn.Quennel · September 2018

Okay, so I'm definitely getting the same issue. Tried renaming the logs as old files, and this is what I got when I started the program again:

Not sure what I need to be doing. My ISP is Mediacom.