Wrye Bash wipes plugin list after patching?

[UnmeiX]

Well, I've been using WryeBash 304.3 without problems for awhile now. I've experienced this issue before, and somehow managed to solve it in the past, but could never find a post that alluded to.. Well, the issue at hand. My setup is pretty heavy, 254 plugins (though maany are compatibility patches), but they run well together, except for this.
 
Simply enough: When Wrye Bash is opened through Mod Organizer and the patch is run, it creates the patch successfully; and proceeds to disable all unofficial plugins and remove them -entirely- from the plugin list on the Wrye Bash screen.
 
I'm a bit OCD with my load order, sorting first with BOSS, then checking Wrye Bash and ordering masters appropriately, then hand-sorting according to author instructions. You can imagine my horror the first time Wrye Bash wiped it completely. Ever since, I've done my best to keep a backup load order before patching with WB, to save myself an insane amount of time. XD
 
Anyway, the load order -isn't- 100% STEP or anywhere near it, but this was a fresh install and mod setup as of a few weeks ago and it worked about flawlessly; and Wrye Bash had even stopped clearing my load order out until today. At random, again, it started, and does it every single time I patch. I'd hoped that, considering how much ya'll have worked with the WB crew, you might have some insight (and, of course, they won't support WB used with MO).

Merged into the Bashed patch are..

Remodeled Armor - Vanilla Replacer - Dawnguard.esp
Remodeled Armor - Vanilla Replacer - Dragonborn.esp
ERSO 06 - Wait More Time Dragon Encounter x4.0.esp
CCO_WAFTrueWeapons_Patch.esp
Mighty Beasts - Werewolf.esp
Hunterborn_Frostfall-Patch
AFT_iNPCFix.esp

 
A couple of pictures to illustrate -exactly- what's going on here.. Everything's fine before patch; and gone after.

I know, I really should create a merged patch or something, but I could never seem to figure out just -how- that works (could never get the entries I wanted to copy over, idk). Anyway, as I said before, it was running fine, even Wrye Bash seemed to like me for once, then today it decided to go ballistic again.
 
Thanks in advance for any help!

Edited April 13, 2014 by UnmeiX

[DoubleYou]

Most of the time I've found this to happen with bad plugins, although sometimes a reinstall of Wrye Bash mysteriously fixes it, or a revert to default settings in bash and repatch. Most annoying.

[GSDFan]

When you start up WRYE Bash do you get any error messages about any plugins? I had a bad skyproc esp from an aborted run and even though it was disabled WRYE would try to enable mods and just about everything would get disabled and my load order would change. When I removed the bad esp WRYE ran fine.

[UnmeiX]

I didn't get an error on starting Wrye Bash, I -did- get errors at one point when trying to fix it.. What I did at the time was open Wrye Bash and click the checkbox for each mergeable mod twice; on the first click I got some popup about 'invalid plugin list' but clicking OK let Wrye continue, so I disabled and marked them for merge, then closed Wrye Bash.. It didn't solve the issue, but I did my failsafe backup and ran SUM, because I'd noticed Wrye Bash was detecting ASIS as having a missing master (an update changed the master name, actually).

 

After ASIS ran, Wrye Bash saw no missing masters but the result after patching was as before, and as you mention; everything is disabled (except official esms) and the load order is scrambled insanely. After restoring my load order from backup, starting a new game a few times, and moving a mod around (after which I put it right back in the same spot) and running WB again.. It worked. Fine. No scrambled load order, no errors of any kind.

 

I'm so confused. I'd close this already, but the issue's persisted awhile and now that I know I'm not the only one that's had it happen, I wouldn't mind giving it a day or so, just in case more insight can be given.

[GSDFan]

I was just finalizing my my new Sykrim load order and decided to create a bashed patch. At the end I got a window with Wrye errors in it, which I dismissed. When I selected OK Wrye wanted to enable the bashed patch and disabled all my ESPs and ESMs. Running Wrye a second time did not with the created BP did not produce any errors on start or rebuilding the patch.

[Kelmych]

I've periodically had this problem also, and it was usually cured by running WB again, installing a new copy of the blank bashed patch, or reinstalling WB. Today I tried all of these, even turning off all mods except the unofficial patches. No matter what I do today, after the bashed patch is created WB initially shows a WB window with only the mods that are physically in the SkyrimData folder followed by a WB window with all mods misordered and disabled except the Bethesda plugins.

[Glanzer]

I have had this exact problem and I posted the FIX for this over in the Wrye Bash area.  Here is what I posted:

 

*** IMPORTANT UPDATE ***

Wrye Bash completely hosed my ESP list again by disabling most of them! So I did more investigation and found the cause of the problem. I had over 900 save games, and Wrye Bash has to PARSE THROUGH ALL OF THEM when it starts up in order to populate the Saves tab. It evaluates each save game against your list of plugins. So I removed 700 older save games and now it's really fast like it used to be and doesn't disable my plugins.

So if anyone has over 500 save games you should think about removing some or you might have the same problem!

BTW, my rig is really fast:
16GB RAM
Quad-core 4.2 GHz overclock
Samsung Pro SSD for all gaming

[EssArrBee]

MO can localize saves for each profile which limits the number of save Wrye bash see on load. Also, delete some saves, why do you need 900 of anything expect dollars and tacos?

 

Edit: MO also let's you enable all plugins at once. Right click on the plugins.

[Garfink]

I know exactly why this happens: after you rebuild the bash patch, you click the close button on the app too quickly, just wait a little the next time before closing and it should be fine.

[whismerhill]

I just wanted to contribute a little bit :

autosave manager  : https://www.nexusmods.com/skyrim/mods/34842/?

is a great tool for handling your saves, having enough to roll back and preventing them to get at extremely high numbers at the same time.

configure it for 50 incremental saves every 10 minutes for example (and disable all other saves)

+ add a manual save hotkey

 

or configure it for 20 incremental saves localized by region  ....

 

a great deal of power and prevents having to clean your own savegames too often

[Kuldebar]

Yup, this happened to me just now...I have 700+ save games...Wyre Bash craps out on Bash Build and wipes load order in MO.

MO can localize saves for each profile which limits the number of save Wrye bash see on load. Also, delete some saves, why do you need 900 of anything expect dollars and tacos?Edit: MO also let's you enable all plugins at once. Right click on the plugins.

Just because I never really thought about needing to delete saves...until now.

[UnmeiX]

Well.. It mysteriously solved itself as it usually does, but by implementing the load/install order backup/restore, the MO team fixed the issue for good, even if it should return.

 

Thank you very much to the people who tried to help, and some responses:

@Glanzer: That isn't a bad fix for WB being slow, but that wasn't my complaint. This can occur on a cloned install with 0 saves; I think it has to do with the plugins themselves.

@EssArrBee: Enabling all esps is good except that you may have many that you merged yourself/that Wrye merges, can be annoying to sort out.

@Garfink: You're exactly off: It happened before I closed Wrye Bash (right after the patch finished), and even if I didn't close Wrye Bash. (In fact, if you'd actually -looked at the pictures I posted showing my problem-, you'd see that Wrye Bash was never closed.)

 

I wish I could mark DoubleYou's answer as the best one, as it's the only one that was even applicable.

 

All in all, I have no idea whatsoever was the cause of it. I would like to thank everyone again, but mostly I'd like to thank the MO team again for developing this amazing tool, and for fixing the issue indirectly.

 

Thank you guys.

Edited May 7, 2014 by UnmeiX

[DoubleYou]

I wish I could mark DoubleYou's answer as the best one, as it's the only one that was even applicable.

So do I

[UnmeiX]

So do I

This made me chuckle.

 

Also, in glancing over the thread again, Kelmych's answer was somewhat applicable also. XD

[Garfink]

I know I know. There is an empty 100k or was it 10K bash patch that needs to be place back into Skyrim data folder. Once that is replaced, reorder your mods again. It should work again. To prevent it occurring again follow my instructions from before and only close wyre bash when it's finish doing its thing. You know it's done when the blue bar highlighting appears and you can click highlight esps again on the main list. If you don't the next time you load it up, everything looks fine until you make a bash and then it will happen again. Totally reproducible on my computer.

 

I am 100% sure.

[DoubleYou]

I know I know. There is an empty 100k or was it 10K bash patch that needs to be place back into Skyrim data folder. Once that is replaced, reorder your mods again. It should work again. To prevent it occurring again follow my instructions from before and only close wyre bash when it's finish doing its thing. You know it's done when the blue bar highlighting appears and you can click highlight esps again on the main list. If you don't the next time you load it up, everything looks fine until you make a bash and then it will happen again. Totally reproducible on my computer.I am 100% sure.

Eh, what?