I can't play the game anymore

[Jesus Maria José]

After the update, a msg don't let my game run after the launcher.

"Could not patch x64/lotroclient64.exe. Acess denied."

So I checked the quarentine of my antivirus and found that exe there. I realise the two files from the quarentine, but as I opened the folder, those files didn't back to the original place.
Worst than that, I download all the game again, and the problem persist.
Should I delete all Lotro folder to fix the problem?
edit: Solved, answer down on page.

[Running-Target]

No.
- First goto your antivirus software, find the Exceptions control page, set exception for LOTRO game folder.
- Then Try the repair option in the LOTRO game launcher.
Top of the LOTRO launcher, there is buttons : Community, Account, Support, Language (EN, DE, FR), Launcher Menu (V), Minimize( _ ), Close (X). If you put your cursor on the buttons it gives a description. In the Options there is Options, About..., Explore Screenshot folder, Explore Log folder. In the Options there is 3 tabs: General, Repair, Proxy. Look in Repair tab of the Options for the Repair button.

- There are several log files in folder ( lotroclient.txt, lotrolauncher.txt, patchclient.txt, ttepatchclient.txt ) Read them to see if there is any error msgs that show the problem.
> c:\user\yourid\appdata\local\the lord of the rings online

- If your game client not running on Windows 10, try: Loading C++ 2005 and .Net Framework 1.1. Right click the LOTRO game link in your Steam game list, pick Manage from list, then pick Browse Local Files, this brings up the Window explorer for LOTRO. Look in the LOTRO directory for the 3rdParty folder, look inside that folder and run all the .exes you find there while the game launcher Not running and under Admin rights account.

- Make sure your Firewall and active defending anti-malware programs have LOTRO directory or game exes in exceptions.

- Make sure you are running the game as Administrator or account with administrator rights.

- Use the troubleshooting compatibility options in Windows OS.

- Many problems with the game stem from poor or faulty Network connection between your computer and the game servers near Boston, MA, USA. Read the sticky thread on the official forum, > Network and Game Connection Troubleshooting - Updated 1/19/2016

https://www.lotro.com/forums/showthread.php?107727-Network-and-Game-Connection-Troubleshooting-Updated-1-19-2016

https://help.standingstonegames.com/hc/en-us/articles/115015989067-LOTRO-Firewall-Help

[Jesus Maria José]

Thanks for the help, but still not working. I open the exceptions over all the folder.
The log seems to apoint to another problem. Somehow the patch over the 64 bits folder aren't been allowed to execute:

000000000.000: preconfigured proxy settings.
000000000.000: Using settings from INI file [C:\Program Files (x86)\Steam\steamapps\common\Lord of the Rings Online\coreonline.ini], section [PatchClient]
000000000.000: Importing public key
000000000.000: Connecting to patchserver at patch.lotro.com:6015
000000000.000: Setting proxy information for patchserver connection
000000000.868: Checking for file patches.
000000000.868: application directory: <C:\Program Files (x86)\Steam\steamapps\common\Lord of the Rings Online>
000000000.868: temp directory: <C:\Program Files (x86)\Steam\steamapps\common\Lord of the Rings Online\tmp>
000000000.868: forward directory: <C:\Program Files (x86)\Steam\steamapps\common\Lord of the Rings Online\forward>
000000000.868: backup directory: <C:\Program Files (x86)\Steam\steamapps\common\Lord of the Rings Online\backup>
000000001.852: Response received from patchserver.
000000001.852: No file patching necessary.
000000001.852: Patching files...
000000001.852: Processing file patch #1: <x64/lotroclient64.exe>
000000001.852: Applying patch <x64/lotroclient64.exe>
000000001.852: File <x64/lotroclient64.exe> is in use, and must be selfpatched.
000000002.070: File patching complete. 0 patches applied, 0 bytes downloaded
000000002.164: Initiating self patch 08/28/21 19:42:47.

[Running-Target]

Close LOTRO launcher, try deleting that file then restart the launcher.

[Jesus Maria José]

Solved: The exceptions of the Firewall and Antivirus wasn't enought to allow the launcher execute normally. I had to SHUTDOWN the Avast antivirus to then the patch file be able to run.
(what heck is inside that patch?!)

[Dex]

i'm having issues with my 64 bit client as well, except for some reason it keeps trying to install the x86 visual c++ and keeps opening up the microsoft support page for VS c++. it even loads, it just thinks it needs to install vs c++ again. Something is definitely weird with the game.

[Running-Target]

- Make sure your Firewall and active defending anti-malware programs have LOTRO directory or game exes in exceptions. I have found in the past LOTRO and DDO files being hoovered up by even Avast active defense because of behavior. Firewalls exceptions need a refresh every once in a while when they quit letting traffic through from LOTRO and DDO. Do an Advance Exception for MMOs like LOTRO and DDO.

[Running-Target]

Originally posted by Gecko:

i'm having issues with my 64 bit client as well, except for some reason it keeps trying to install the x86 visual c++ and keeps opening up the microsoft support page for VS c++. it even loads, it just thinks it needs to install vs c++ again. Something is definitely weird with the game.

It is doing that with everyone, they hardcoded installing those files every time you start the launcher, and i guess there is a check to see if those files are installed. then skip if they are.

[dandeancook]

I have to solve the 'x64/lotroclient64.exe not accessible' issue as below:
* Reboot PC
* Launch Steam as Administrator
* Right-click on game name >> Browse Local Files
* Right-click on LotroLauncher.exe >> Run as Administrator

Another error shows after the reboot sequence above:
* PatchClientDll::CheckDatFiles

Solve the second issue:
* LOTRO launcher >> Top bar >> Options >> Repair
* Now it works as before

[Yuki]

This thread was quite old before the recent post, so we're locking it to prevent confusion.