Open wachuwamekil opened 7 months ago
Did you used the Patcher.exe to patch your Wow.exe?
I did, I additionally got the following note that it was sucessful.
With a fresh wow.exe, I ran the patcher via powershell, it prompted for elevation, I agreed. After complition and running wow.exe I got the following note again.
When I rename the .dll (file.dll.old), after patching the file the client seems starts without issue. Of course the game forces a log out because the mod can't find that the dll has been loaded. I think it's failing in the initialization of the DLL, is there a way to get more detailed logs to TS the issue?
Moving the files and patched wow.exe to the deck resulted in the same behavior. I have a couple laptops with different versions of windows on it and will see if patching on those work. I know windows 11 security can be weird with patching operations. Will update issue once I try an 8 and 10 system.
Patched a clean file on two different Windows 10 devices on a new install/unzip, same behavior. Reporting that the files were corrupted.
It seems that your .exe has signature (GlueXML / FrameXML) protection still enabled, try using this exe as a base and then applying the patcher to it:
After trying an "unglued" exe, the patcher worked as expected on the windows 11 system. My assumption is it'll work on the deck, I'll verify that this afternoon. If that works this issue can be closed.
Confirmed working on deck, thank you for the assist!
I will add the "unglue" patch to the patcher 🔜
Attempting to run on windows 11 to test before putting on the deck the following error pops up:
Running in windows 7 compat mode dosn't throw the error, however the game does not run.
Error in GlueXML.log is 'GlueXML is modified or corrupt".
LMK if you need anything on my side.