Jump to content

Wrye Bash won't start


AerolithHD

Recommended Posts

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:

Error! Unable to start Wrye Bash.


Please ensure Wrye Bash is correctly installed.


Traceback (most recent call last):
File "bash\bash.py", line 321, in _main
import bosh # this imports balt (DUH) which imports wx
File "H:\Steam\steamapps\common\Skyrim\Mopy\Wrye Bash Launcher.pyw", line 76, in load_module
exec compile(code, initfile, 'exec') in mod.__dict__
File "bash\bosh\__init__.py", line 45, in <module>
from ._mergeability import isPBashMergeable, isCBashMergeable
File "H:\Steam\steamapps\common\Skyrim\Mopy\Wrye Bash Launcher.pyw", line 63, in load_module
mod = imp.load_source(fullname,filename+ext,fp)
File "bash\bosh\_mergeability.py", line 30, in <module>
from ..load_order import cached_is_active
File "H:\Steam\steamapps\common\Skyrim\Mopy\Wrye Bash Launcher.pyw", line 63, in load_module
mod = imp.load_source(fullname,filename+ext,fp)
File "bash\load_order.py", line 48, in <module>
import balt
File "H:\Steam\steamapps\common\Skyrim\Mopy\Wrye Bash Launcher.pyw", line 63, in load_module
mod = imp.load_source(fullname,filename+ext,fp)
File "bash\balt.py", line 3059, in <module>
class WryeBashSplashScreen(wx.SplashScreen):
ImportError: caused by ImportError(u'caused by ImportError(u\'caused by ImportError(u\\\'caused by AttributeError("\\\\\\\'module\\\\\\\' object has no attribute \\\\\\\'SplashScreen\\\\\\\'",)\\\',)\',)',)

 

 

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • 3 months later...

well, i am having exactly the same problem, the only thing is that running LOOT does not solve the issue, I did exactly all the steps so did mention above with the same result.

The Nexus commenting page for Wrye Bash is closed as welll as the forums, so really, after years and years modding first Oldrim and now SE, I find myself playing without a bash patch and hopping for the best

 

Very, very nice if someone can give me a hint

Link to comment
Share on other sites

  • 5 years later...

In case someone else is looking for a possible fix, I had success with a similar error. After snuffling around the dark corners, I found where Skyrim's load order is kept. Go to C:/users/...../AppData/Local/Skyrim and delete the following files:

loadorder.txt
loadorder.txt.bak
plugins.txt
plugins.txt.bak

Then restart WryeBash.

BE WARNED: This is a last resort that will deactivate ALL your current mods and completely WRECK your load order, which you might have to sort and rebuild manually.

But it still might be better than gutting your whole build while WryeBash repeatedly refuses to work despite multiple uninstalls and installs, while you gnash your teeth and bang your head against the wall until one or the other breaks. 😵‍💫

Edited by randperry
  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
On 11/17/2024 at 2:38 AM, randperry said:

In case someone else is looking for a possible fix, I had success with a similar error. After snuffling around the dark corners, I found where Skyrim's load order is kept. Go to C:/users/...../AppData/Local/Skyrim and delete the following files:

loadorder.txt
loadorder.txt.bak
plugins.txt
plugins.txt.bak

Then restart WryeBash.

BE WARNED: This is a last resort that will deactivate ALL your current mods and completely WRECK your load order, which you might have to sort and rebuild manually.

But it still might be better than gutting your whole build while WryeBash repeatedly refuses to work despite multiple uninstalls and installs, while you gnash your teeth and bang your head against the wall until one or the other breaks. 😵‍💫

 

This worked for me. As the author of the Beginners Guide to Modding here on the Nexus, I will be adding this fix to my guide. 10 years of supporting my guide and this was the first time I ever ran across this problem lol

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...