Jump to content
  • 0
Sign in to follow this  
Dormdude

Can't Use Wrye Bash from MO2

Question

I use to be able to use Wrye bash with mod organizer a couple months ago. But I recently started messing around with mods again and updated MO2. But since I updated it i can't launch wrye bash. Whenever i do i get the error "the action cannot be complete because the folder or file is open in another program" But wrye bash isn't open in anything else. I've tried uninstalling and reinstalling MO2 and Wrye bash. I've tried moving the install location for both. But i still keep getting the error. I've been trying to get it working for a couple weeks now and now I kinda need it because i've almost hit the esp limit for skyrimSE. I would use merge plugins but i've had nothing but an endless amount of problems with that and wrye bash is just so much easier. Anyone know how to fix this issue? 

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

You are a Windows 10 User. You are using a Windows Update that is prior to the 1809 version. You need to force update your Windows installation to 1809 or greater, which can be done using the Windows Update Assistant. If you google that, you should be able to find the links you need... I don't have them handy at work. ;)

Share this post


Link to post
Share on other sites
  • 0

You are a Windows 10 User. You are using a Windows Update that is prior to the 1809 version. You need to force update your Windows installation to 1809 or greater, which can be done using the Windows Update Assistant. If you google that, you should be able to find the links you need... I don't have them handy at work. ;)

Well that worked. Thanks. I don't really get why i had to go through a 2 hour process to update windows to fix something that worked fine before in previous versions of MO2. 

Share this post


Link to post
Share on other sites
  • 0

It's not MO2 that is the problem - it was Wrye Bash and how it works with MO2. The short version is that WB updated in a way that needed the newer Windows version, and likely didn't realize at the time what had happened. That Windows update (and, from what now understand, all to follow) are no longer forced updates unless the system determines it is required somewhere in the background. Hence, not everyone got the 1809 update. The 2 hour install of Windows... well, that's on MS and their file sizes, I guess.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By qwrtui1245
      Hi, 
      I'm modding SkyrimSE with MO2 by following this version of the step guide: https://stepmodifications.org/wiki/SkyrimSE:1.0.0#04-Foundation. I've followed everything until now but experience problems with the first mod I need to install without using Nexus. It's Skyrim SE particle patch for ENB and I downloaded 'SPECIAL EDITION > ALL-IN-ONE INSTALLATION > LATEST VERSION (GOOGLE DRIVE)'. It's installation went fine (Situation A) but when I have to enable the optional ESP 'Particle Patch for ENB SSE.esp' I get the message 'Plugin not found: Particle Patch for ENB SSE.esp' in my log (Situation B). 
      I've tried: reinstalling the mod, refreshing, enabling and disabling the mod, restarting MO2, re-downloading the file. It doesn't fix my problem. I've added the pictures of situation A and B. I hope there are people who can help me here. Thanks so much in advance!
      Situation A

      Situation B

       
    • By Newtant
      Hello!

      I've stumbled upon a weird issue that I haven't encountered or read about before. I'm running Windows 8.1 and a fresh install of Fallout New Vegas with no mods so far. I'm trying to get Mod Organizer and the 4GB exe to work together, but despite following all of the advice, tips and workarounds it's still not happening. Right now I can launch the 4GB exe through Mod Organizer. The game starts, I can load a save and 'play'. The problem is that all of the text has disappeared or is invisible. I can only navigate the main menu by memory, the ingame popups regarding the DLC is missing the text as well.

      This issue does not happen if I start the game on its own with the normal exe.
      This issue does not happen if I start the 4GB exe on its own.

      It only happens if I start the either the normal or the 4GB exe through Mod Organizer.

      NVSE is being loaded, it doesn't matter if I'm using NVSE stable or beta.
      I'm using NVAC, without it the game crashes before arriving at the main menu. NVAC seems to be working, the log is showing several handled errors. (Pastebin)
      Yes, I've added '-laaexe .\FalloutMO.exe' to the launch arguments, that helped me get around the access is denied error but produced this text error.
      I did try compatability modes, I've tried starting MO, the 4GB or both as administrator. No dice.

      I've arrived at a point where I really don't know what it could be or what I could try next. One thing I do know, however, is that I can't go back to the pre-MO modding, so I'm turning to you helpful people and hope that someone here has an idea.

      Thanks in advance!
       
      Pictures:
      New Vegas installation folder
      Mod Organizer executable settings
      Disappeared text main menu #1
      Disappeared text main menu #2
      Disappeared text ingame
       
      Edit:
       
      I deleted all of the fallout .inis as well in case some of my text/font settings were messed up, but that didn't work either.
    • By Dennai
      Is there a way to make GaryBash work with MO in Fallout 3? I tried to use it as executable, but MO wouldn't recognized the Wrye launcher as such. It surprised me, because MO had no problem recognizing the Wrye Bash launcher for Oblivion, but I don't have the same luck with Wrye Flash. When I browse the Moppy folder to try to find the Binary, Wrye Bash Debug is the only application the MO can see.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.