I have WB v287 and a stable FCOM game with 254 mods active (more bashed into the bashed patch).

Everything was A-OK until yesterday. Today, when i open Wrye Bash, it came up with a error message, removed a bunch of esps from the load order, and before I could figure anything out. CLosing the application and restarting the PC was no use. Wrye Bash doesn't start - it comes up with "initializing modinfos", and that windows disappears in 1 second. Then, nothing.

Worse, all my mods are now ghosted - so can't see a damn thing. What gives? I didn't even change any settings, just ran BOMM befoe this...

Is Oblivion.esm ghosted too? If som rename it manually and WB should hopefully start.

Funny thing, bugdump lists Bootstrap errors (can't copy it, had to go through the command window).

Worse, there is no Oblivion.esm file in the Data folder anymore. The esms/esps are all ghosted.

Where/How did the Oblivion.esm disappear? :banghead:

They didn't disappear. Ghosting means WB renames it. So if Oblivion.esm somehow was ghosted its file name is now Oblivion.esm.ghost. Just rename the file back to Oblivion.esm. If you can then start WB you should be able to unghost the rest the usual way.

Nope, oblivion.esm was indeed gone - the rest of the ghosted files were there, but somehow there was no Oblivion.esm!

I was able to recover it from using Recuva, and got my Oblivion.esm back (maybe it was deleted?). Placing it back in the Data folder (without the .ghost extension) doesn't help WB run... :brokencomputer:

Damn, I don't know what caused this. Guess I can reinstall... thanks to Wrye bash the reinstallation should be easy. But how do I get it started? :confused:

Is there a known reason why WB locked up and ghosted all the files? Not sure why Oblivion.esm went missing and a bunch of other esps were deactivated...

Wrye Bash still isn't starting, and I am not sure what to do, or what caused this?

Is there a way to print the Wrye Bash bugdump from command prompt to a text file, so that I can paste it here and help shed some more light on it? I think this is all related to the missing Oblivion.esm master file, but still might be worth a look...

You should be able to copy the bug dump by using CTRL-C. If not a screenshot may do.
Have you tried reinstalling Wrye Bash? Does other Python applications, like Pyffi work? If not you should reinstall Python.
But back up all your ESPs first.

Thanks for your input Petrus - it is quite helpful to hear calm and sensible advice when things go haywire.

Damn, getting modded Oblivion to near-perfection (for me) took forever, and when everything is going just fine, BAM! :violin:

I'll get the screenshot/paste of the bugdump, and try to reinstall python (just am not sure what happened for it to work fine one day and throw up the other). I guess I can blame those PC gremlins for coming up and peeing on the CPU last night :brokencomputer:

You may want to post this in the Wrye Bash thread instaed. More chance of a high level techno geek spotting it.

I've had Wrye Bash crash like this before - very rare but has happened before. No one able to find a cause, but did notice after heavy defrag more likely.

I learned to back up all my active plugins. Just highlight them and copy them to another folder (where I usually also run BOSS). IF I add a new plugin then put a copy in there too.

Then I can just copy back over what I need. That may be overkill, but I'd at least make a back up of all the offiicial plugins and bsa and music.

I found at times it wanted more than Oblvion.esm back in there though, so maybe try moving out the old bashed patch and put a new one in there.