noctred

Depends on what you mean by "run". I did open WB outside of MMO just to make sure it wasn't a fundamental issue with the Wrye Bash installation itself which was giving me issues. I never tried to generate a bashed patch that way though. Regardless, it did make an empty bashed patch .esp in my vanilla Skyrim SE directory whenever I opened it outside of MO, but not the Docs folder. Just the esp.

FYI, for anybody who might be running into the same issue with Wrye Bash and MO2, I seem to have found a fix. Seems that Wrye Bash dies on load if any mod in your load order contains a 'Docs' folder and continues to die even if that mod is removed from your load order. To fix, I had to create a dummy mod with contents mimicing an exported bashed patch - directory/filename size --------------------------------------- Bashed Patch, 0.esp 0 Docs/Bashed Patch, 0.html 0 Docs/Bashed Patch, 0.txt 0 As soon as I created and loaded this mod, I was able to open Wrye Bash from within MO2 without errors or crashes. It also doesn't seem like you need to keep this dummy mod - after the first successful run, I was able to delete that mod and Wrye Bash still opens without error.

Modding SSE w/ MO2 has basically been a hot mess for me. LOOT sort of works. I usually have to run it at least three times before it finally loads its masterlist properly and sorts my plugins without errors. FNIS doesn't work. It consistently tries to look for its files in Steam's SSE directory rather than properly utilizing the MO2 VFS and, as a result, constantly throws error 76 (could not find a part of the path ...). Thankfully I only have a few animation mods so I can copy those over to my Steam install and run FNIS there, then copy the built files back. Fine. No big deal. Yes, the FNIS mod is enabled. Latest issue - Wrye Bash crashes on startup with - Traceback (most recent call last): File "Wrye Bash Launcher.pyw", line 87, in <module> ImportError: cannot import name bash Things I have tried - 1. Completely reinstalled both MO2 and Wrye Bash. Multiple times.2. Ran MO2 in portable and instance mode.3. Wiped and regenerated from scratch any and all ini's and other configuration files related to MO or Wrye Bash in AppData.4. Installed MO2/Wrye Bash in different directories and on different hard drives.5. Disabled UAC.6. Ran one or the other, or both, as administrator.7. Killed a majority of non-essential running processes - Steam, Geforce Experience, AV, firewalls, VPN clients, virtual drives, mouse/keyboard software, and so on and so forth. All stopped, along with their helper processes where applicable.8. Verified system requirements - VC++ redist's, .NET framework, etc.9. Googled that error and tried everybody else's fixes. The worst thing is that I was able to run Wrye Bash through MO2 without problems *literally* just earlier today. Now, all of a sudden, WB crashes every time with the above ImportError logged. I've changed nothing from a system perspective between now and then. The only changes made (listed above) were made as a response to the sudden crashes. Really not sure what's going on or what else I can even attempt as a fix. I'm on Win10 Pro.

I figured that was happening because I'm using a portable install and not an instanced install. If I swap to an instance-based install, the particular scenario you're talking about goes away (MO launches straight into its UI), but I still get all the same errors and crashes regardless.

I'm using the default profile that is created by the application - it is named 'Default', minus quotes. I haven't created any new profiles and I did not rename the default profile. I don't think I'm running anything that would create file or directory locks. I killed my AV software (including the background helper processes), turned off Steam overlay for FO4, killed GeForce Experience, killed my virtual drive apps... there's nothing else of any consequence running. Here's the ModOrganizer.ini, usvfs.log, and crash dump from my most recent session - https://www.mediafire.com/?8x2qe9bjdje1u5v Thanks.

Similar things happen with other executables also. For instance, MO will throw errors and crash after I've been in xEdit for a while, or after I use Bodyslide... but it doesn't seem to be as consistent.

I posted this on the github issue tracker but I'm not sure how much traffic that place gets, so figured I'd repost here along with a brief video demonstration (below). -- Without fail, every time I quit FO4, Mod Organizer dies. Sometimes, it dies right after FO4 starts rather than waiting for me to exit. Basically, the symptoms are - nearly all flags disappear from the mod pane, the filetree for most (but not all) mods turns empty, and nearly everything vanishes from the plugin pane, as if MO is no longer able to properly interact with the VFS. If I try to interact with MO in any way at this point (for example, if I open up the details pane for a mod), it either crashes outright, or I get some series of errors. For example - failed to write log to /path/to/mo_interface.log: Insufficient system resources exist to complete the requested service.failed to write /path/to/mod/meta.ini: error 1An error occurred trying to write back MO settings to /path/to/ModOrganizer.ini.new: File is write protected Sometimes the errors are different (see video), but it always errors out in one way or another. The MO directory is not write protected and I'm definitely not constrained by resources at the hardware level. Once I close and restart MO, all functions seem to work normally until the next time I play and exit FO4. Reproducible 100% of the time. I am on Windows 10 and I am using MO in portable mode. I also tried using instance mode and ran into the same issues. Tried reinstalling MO several times. As a side note, this version of MO is also behaving strangely with F4SE for me. When I launch F4SE through MO, I get a popup stating that some component of F4SE has stopped working - however, I can click cancel on the popup and F4SE seems to initialize properly anyway (I can pull the F4SE version from game console and F4SE-reliant mods seem to work normally). Not really sure what's going on there. -- Brief video example - first clip is of MO throwing a bunch of errors and then crashing (errors aren't the same every time; sometimes I see the ones mentioned above). Second is just a straight crash - https://www.youtube.com/watch?v=mtOJlIIizho Thanks.