AerolithHD

I fixed it, and now I feel silly. I thought about deleting this, but figured I should post my solution since I didn't see it in all the posts I'd looked at: I used LOOT to sort my load order and now Wrye Bash opens and works perfectly fine. Wrye Bash apparently doesn't work if the data folder and the plugins.txt / loadorder.txt aren't the same. Didn't think sorting my load order would help anything, but lo and behold.

I recently reinstalled legendary edition Skyrim for a clean slate, but now I can't open Wrye Bash. Wrye Bash has worked with no problems before I reinstalled; it opened, it made bashed patches, exactly what it was supposed to do. Now it doesn't open when I click on it, and when I try to run it through Mod Organizer (pointed to the WB executable as it always has been), MO locks for a few seconds, nothing happens, and it unlocks again. I've reinstalled Wrye Bash (v307) several times now. I uninstalled Skyrim completely (including the appdata\local\ Skyrim and documents\my games\skyrim files) and reinstalled, got a fresh Wrye Bash from the Nexus, but it still won't open. The BashBugDump in \Mopy is empty whenever I open it, even after running Wrye Bash.exe through the command prompt. I tried following the step-project configuration guide (uncommenting lines in the bash.ini, redirecting the paths to the Skyrim installation folder, etc), but that didn't work either. I restarted my computer several times, I tried installing the standalone version, I've tried shutting off my Avast shields before I run it (despite getting no warnings from Avast before), I've made sure to run Skyrim at least once after each reinstall, but nothing's worked. This last time, I decided to install Wrye Bash including its Python files. Wrye Bash still won't start through the python executable, but the executable does give me this: