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.
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.
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 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.
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.
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.
Same here in hawaii and with Spectrum, they say they have nothing to do with it.
lordrichter 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.
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.Same here in hawaii and with Spectrum, they say they have nothing to do with it.lordrichter 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?
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?!?
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
lordrichter 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 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)
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)
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