Ok I tried that. So what I did is replace the old Dyndolod.exe with the new one (The old one is stored on a different folder just in case) then rewired the new executable to launch from MO2. If any of that was incorrect do tell. Now with the new executable I'm getting a new problem that being:
DynDOLOD
[Main Instruction]
Access violation at address 0000000001025B99 in module 'DynDOLODx64.exe' (offset CE5B99).
[Content]
Read of address 0000000000000000.
Click on this link for additional explanations and help for this message
For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum.
That's the error message. Here are the Debuglog and LOG, again theres no bugreport.txt
This new problem also hits before dyndolod gets to where the old one happened so for now I cant now whether or not it persists.
Ive tried to troubleshoot this myself with some of the recommendations for Access Violation problems from other post but I haven't managed to make it go away.
Ive tried the following:
Cleaning the problematic mod with xEdit, in this case the problem seems to be Dyndolod itself.
Disabling antivirus.
Making sure to close as many programs running in the background.