Ryath_Waylander wrote: »Hi All, for those of you on Windows 8 encountering this issue, we are investigating a different workaround for you. We will update when we have more information. In the meantime, if you could send your Host File logs, that would be helpful in finding a solution. You can send that to me via private message.
If you need instructions on how to get this file, please refer to the article, linked here.
It's been a few days since the problem arise.
Why don't eso fix the Launcher?
Players not in the forums can't fix this issue and still can't login the game.
Please pay more attention to those who still using win7/win8.
Unfortunately it's a problem with us running Win 7/8 and not the Launcher that's broken. Remember Win 7 is no longer supported. This is not the first game I have recently had to find a manual fix and workaround for. I still prefer Win 7 but even the next CPU/motherboard upgrade I will do is requiring Win 10. It's becoming a hardware issue too when your new cpu isn't compatible with Win 7.
Win7 x64, tried EasyFix, it didn't work.
KB3140245 is an official microsoft update. And MicrosoftEasyFix51044 too.MilitiaMasterV wrote: »I'm not even going to 'test' this 'fix'....because it involves messing around with the registry, and changing a 'default' (Natural state) of the computer from 'off' to 'on'. The fact that you are all just casually OK with a company essentially doing what amounts to 'opening a port for a hacker' on all your rigs because you don't know what it does and just apply it because some person told you to is kind of silly.
MilitiaMasterV wrote: »I'm not even going to 'test' this 'fix'....because it involves messing around with the registry, and changing a 'default' (Natural state) of the computer from 'off' to 'on'. The fact that you are all just casually OK with a company essentially doing what amounts to 'opening a port for a hacker' on all your rigs because you don't know what it does and just apply it because some person told you to is kind of silly. When it opens up a problem later down the line, because someone has easy access to your rig through that opening that is made, then whatever.
I personally use Win 7 (x64, I believe)
Ryath_Waylander wrote: »Hi All, for those of you on Windows 8 encountering this issue, we are investigating a different workaround for you. We will update when we have more information. In the meantime, if you could send your Host File logs, that would be helpful in finding a solution. You can send that to me via private message.
If you need instructions on how to get this file, please refer to the article, linked here.
It's been a few days since the problem arise.
Why don't eso fix the Launcher?
Players not in the forums can't fix this issue and still can't login the game.
Please pay more attention to those who still using win7/win8.
Unfortunately it's a problem with us running Win 7/8 and not the Launcher that's broken. Remember Win 7 is no longer supported. This is not the first game I have recently had to find a manual fix and workaround for. I still prefer Win 7 but even the next CPU/motherboard upgrade I will do is requiring Win 10. It's becoming a hardware issue too when your new cpu isn't compatible with Win 7.
yeah, thats a big shame. Win 10 was designed as OS for mobile and desktop. Windows Mobile failed hard, and now we are stuck with the feeling of using a mobile OS on desktop, while having no mobile version of it at all any more. Its just feels clumsy and bumpy. Even the colors just feel as a faded out version of real colors.
- Did you try launch eso64.exe? It still works.
I lost nothing without a launcher, except news.
- MicrosoftEasyFix51044 didn't work for me (Win7)
buzonnewsb16_ESO wrote: »Hi,
My problems started one day when I launched the game. I got Error 102-DownloadError_InvalidMetafile.
After trying everything, I uninstalled, downloaded a new installer, and launched a fresh installation from scratch.
Then I started getting the 210-PatchManifest_DownloadError error.
I put my problem in this forums but you closed my thread and redirected me to this thread and I could see that apparently the problem was TLS, that I must to install a patch from Microsoft and then run the easy fix.
Well, I have done all that, rebooted, checked the registry entries and all I have achieved is to return to the original error: Error 102-DownloadError_InvalidMetafile.
I went back to following the steps in the KB Article for this error:
STEP 1: TEST FOR CONNECTION ISSUES - Ok
STEP 2: RUN THE ESO LAUNCHER AS AN ADMINISTRATOR - Ok
STEP 3: ENSURE THE ESO FILES ARE ADDED TO YOUR FIREWALL AND ANTI-VIRUS PROGRAMS - Ok
STEP 4: DELETE THE PROGRAMDATA FOLDER - Done
STEP 5: REPAIR THE GAME CLIENT - Not applicable. I am not updating. I'm installing.
I think I need a sixth step.
Shirayuki_Sama wrote: »Someone on Steam on this link found a solution, and it worked for me and my husband and other users
https://steamcommunity.com/app/306130/discussions/0/3084394448721244140/
Looks like this is a problem with Windows 7 not enabling TLS 1.1 by default for the WinHTTP API. Zenimax must have updated the launcher site today.
I was able to get things to work by applying the fix in KB 3140245 (https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392).
Specifically I had to install the "Easy Fix" link (https://download.microsoft.com/download/0/6/5/0658B1A7-6D2E-474F-BC2C-D69E5B9E9A68/MicrosoftEasyFix51044.msi) to make the necessary registry updates, NOT just download the Windows update itself.
I hope it will help
B100d1ust88 wrote: »Hello, again!
Happy to say that I was able to solve this problem with your help guys!
I downloaded and installed "Windows Embedded 8 Standard x64 (KB3140245) from this page https://www.catalog.update.microsoft.com/search.aspx?q=kb3140245 and then i ran MicrosoftEasyFix51044.msi in compatibility mode with the previous version OS.
And it worked!
Before that i tried to add registry keys manually...and without this "kb-update" nothing worked.
Thank you all. And thanks to ZOS_KEVIN!
Shadowshire wrote: »Regardless, the Launcher issue has not been resolved for me, and, probably not for most of the other Windows 7 diehards playing TESO. Why am I still running Windows 7?
The problem dates back to 2015, so do you have enough time to fix it?
Why suddenly does it no longer work?
this is done on purpose to change the operating system!
no then, six years to find a solution should be enough?
Because at the moment the launcher no longer works.
So in the Tuesday update I am no longer playing?
Thank you for your help
PS: I am under win 8
As at the beginning of last year I had two desktop home PCs running Windows 7. In January 2020 I updated one of them to Windows 10, following the tutorial here:-Shadowshire wrote: »Shirayuki_Sama wrote: »Someone on Steam on this link found a solution, and it worked for me and my husband and other users
https://steamcommunity.com/app/306130/discussions/0/3084394448721244140/
Looks like this is a problem with Windows 7 not enabling TLS 1.1 by default for the WinHTTP API. Zenimax must have updated the launcher site today.
I was able to get things to work by applying the fix in KB 3140245 (https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392).
Specifically I had to install the "Easy Fix" link (https://download.microsoft.com/download/0/6/5/0658B1A7-6D2E-474F-BC2C-D69E5B9E9A68/MicrosoftEasyFix51044.msi) to make the necessary registry updates, NOT just download the Windows update itself.
I hope it will help
When I attempted to install the TLS "fix" while following one of the two Troubleshooting protocols, the system declined because it has already been installed -- quite a long time ago, I believe. From your remarks, I suppose that the issue might exist for some Steam users.
Regardless, the Launcher issue has not been resolved for me, and, probably not for most of the other Windows 7 diehards playing TESO. Why am I still running Windows 7? Have you looked at the desktop after Windows 10 is installed? Microsoft's marketing department designed it. They explicitly pretend that the principal, if not only, software that we run is "licensed" by Microsoft. Anything else is irrelevant or trivial to them and shoved aside into a sub-menu box that looks like an afterthought.
OwenDaring wrote: »
[ WinHttp.reg ]Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp] "DefaultSecureProtocols"=dword:00000a00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\Passport Test] "ConfigVersion"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\Tracing]
- Den Inhalt zwischen den [code]-Markierungen in eine Datei mit dem entsprechenden Namen kopieren & speichern.
- Rechts-Klick drauf
- auf „Zusammenführen“ klicken & bestätigen.
- Fertig ist die Laube.