I tried this as well as re-installing the version files as listed on the support page. The article associated with the 209 error. Sadly did not work.Try this: click on the little 'link' in the error for help. Mine seems to be working after this
Right click on the launcher icon.
Select Properties.
Click on the Compatibility Tab.
Check the box that says Run as Administrator.
Click Apply and Ok.
Run the game.
Try this: click on the little 'link' in the error for help. Mine seems to be working after this
Right click on the launcher icon.
Select Properties.
Click on the Compatibility Tab.
Check the box that says Run as Administrator.
Click Apply and Ok.
Run the game.
^^ I get this too since v2.0.4... having to run repair daily is a real PITAI also experience Error 209 - PatchManifestError_VersionFail, but for me it happened immediately after NA Patch v2.0.4 completed.
BTW, I have permanently set Properties for the Launcher to Run as Administrator. In an abundance of caution, I previously had also set the other ESO executables such as eso.exe, etc., to Run as Administrator.
I ran Repair, but that did not fix the problem
I then clicked the KB link on the error box and downloaded the "manifest version" text file "fix", which I dutifully copied to the Program Data folder under the Launcher folder (not Windows > Program Data). Re-ran Repair with the text file in place, but Error 209 reappeared.
Next I searched Support for Error 209, found the KB dated 03/16/2015 and followed the detailed instructions for advanced troubleshooting and repair, and then deleting the various version number files in Client subfolders
Rebooted and ran Repair again. Finally Play appeared!
I successfully logged in (to NA) and played for about 90 minutes with only one minor movement bug, for which I sent a /bug report.. Unfortunately, after I quit the session, when I returned to the Launcher screen, a different Manifest Error message appeared. This time the Repair button appeared, highlighted. I'm running yet another Repair session as I repot this.
During Beta I had several problematic instances of Error 209 around August 2014. Until today, the issue seemed resolved.
Is Monday's instance of Error 209 caused by a fault in the v2.0.4 download? I look forward to a resolution.