Hytbold and 64-bit client crash and lockout
Is anyone else experiencing a crash-to-desktop when entering Hytbold using the 64 bit client?
This happens every time (tried 3 different alts, Hytbold at different stages of rebuild) for me on both my desktop and laptop PCs (both Win 10, with decent modern gaming h/w specs).
It then becomes impossible for me to log in to that character, unless I revert to the 32-bit client, and once in game, move the character away from Hytbold.
Possibly confirm this issue
Hi, I am currently working my way through the Hytbold series, and am using the 64 bit client - had a crash to desktop a couple days ago - VERY rarely if ever
happens - will keep an eye out and see if this is repeatable - Like the poster - Hytbold is part way thru its rebuild.
Jim
You have encountered an Oh Snap! moment
I think I may have a clue why the problem is happening. After the last patch (33.2.1) I went around and updated all my LOTRO boxes. I encountered a strange bug on my Windows 11-N install.
The patch didn't ask for admin privileges. It then proceeded to "update" the files anyway. In the process I got several errors:
- Could not patch file "Lotrolauncher.exe". error 5: Access is denied.
- Failed to restart the launcher, error 2: The system cannot find the file specified
I got variants of the above for x64/lotroclient64.exe too. Here's where things get weird. Noticing these errors, and lack of requesting admin, I relaunched forcing admin. Apparently the launcher thought everything was okay and took me to login.
But wait there's more. I patched a Windows 11 Pro install without any issue. I then hashed the contents of the LOTRO install folder from this machine. (The idea was to use the hash results to assist other players.) When I compared the hashes from this machine to the previous machine (with borkage) I found something interesting...
The patching had actually failed (on the one that didn't originally ask for admin), and the hashes where markedly different. So essentially, due to a bug in the patcher I have a Windows 11-N machine with different file hashes from another machine where the patching worked perfectly. In both cases the launcher currently loads but clearly one is broken.