DoubleYou

You shouldn't need to Revo Uninstall. The only registry keys made by Fallout NV wouldn't cause this (indeed there is very little other than the game files that it installs). From what you have said, it simply has to do with the 4GB patch not working or something. There has to be a reason, and I'm very sure a Revo uninstall isn't going to fix it.

If you load up Wrye Bash, do any of the esps (Requiem - Dragonborn, Requiem - Sic Patch...., RequiemDB - Sic patch) appear as being any color other than green? Are any of the masters out of order?

Nvm on the FalloutNV.exe. I just realized that unless you modified those, they never are put in the ini, and are just detected upon startup. Nothing wrong there. I think the problem lies somehow with the interaction between MO and the modified executable. I'll have to research this a bit more.

This normally happens to me when Wrye Bash decides that I don't need any esps activated except its own. I've learned to backup the loadorder.txt and the plugins.txt. Thankfully, I use BUM so putting it all back in the correct order isn't hard. It's putting all the esps active that I was using that is most difficult.

Python should be installed to default location, not ModOrganizer folder. While theoretically the 2.7.6 release candidate version should work, I'd personally wait until it is complete to update, or simply stay with 2.7.5 as it isn't broken.

Neovalen has stopped his previous method of altering the conflicting esp directly to a method where we create a single patch for the whole guide. Basically, load up your entire load order in TES5Edit and follow conflict resolution guide into create one big patch.

I'm going to have to attempt to reproduce the problem probably to be able to solve it. Perhaps the 4GB thing messes with the SteamAppID? What I'm wondering though, is why in your custom executables, you do not have FalloutNV.exe, and the script extender is marked as custom. They are supposed to be detected automatically and nonremovable. Try this: 1. Make a backup of ModOrganizer.ini onto your desktop or somewhere else safe. 2. Delete ModOrganizer.ini 3. Now load up Mod Organizer and see if you can't run the game.

You need to run Boss and Wrye Bash through Mod Organizer. See https://wiki.step-project.com/Guide:Mod_Organizer#tab=Third_Party_Programs

I use Apocalypse with no regrets.

I personally prefer this one... https://lmgtfy.com/?q=Skyrim+Realistic+Overhaul

Will have to be more specific on the wiki I reckon.

Actually, the only patches I have created for AOS that aren't covered in Michael's patches were for Civil War Overhaul and Thunderchild Shout Package. Everything else was right as rain compatible, albeit the author just uploaded a new version so I may have to recheck.

What would be awesome would be to take the unfinished work that this is and make another unfinished work. Gopher has been doing some videos reading some of the books he finds. We could, with his permission of course, take the audio from those reading and apply it to all the books he has read so far.

Actually, I'm using Intel HD Graphics on my Windows 8.1 and my graphics driver keeps crashing too, so I think that is a OS problem. I dual-boot, so that solves a multitude of problems.

Try looking in the data tab to see if you can't find them in there. I've never had files disappear from the Overwrite directory, although I'm sure it's possible.

That's why I dual boot windows 7 and 8.1. Windows 8.1 currently doesn't quite cut it on everything, and actually has some nasty bugs.

This isn't a problem with Windows 8.1 as I use it successfully with Mod Organizer. I've experienced this before, but I forget the steps to reproduce. This should not be normal behavior. If this occurs for every mod you attempt to download, that would be abnormal behavior, which should be reported to the issue tracker.

Wrye Flash and Wrye Bash are different. Wrye Bash only works on Oblivion and Skyrim. Wrye Flash comes in two versions: a Fallout 3 version and a Fallout New Vegas version. I have personally used Wrye Flash in conjunction with Fallout 3 in Mod Organizer with minimal problems (it complains at times because I have Mod Organizer move the bashed patch out of the overwrite folder).

I know that I have been able to use Wrye Flash + Fallout 3 with Mod Organizer with little trouble, but have yet to try it with New Vegas.

I was referring to the interactive tutorials MO has integrated in itself. For example, last I checked, it still talked about being able to see files available on the Nexus in the mod Information window on the Nexus tab.

Dragon Combat Overhaul patch is available. Yes, it requires a lot of patches, and Michaelw has a whole mod page full of them. While the incompatibilities with this mod are numerous, ELFX is worse. I have made 15 patch esp files to make ELFX compatible with my load order, and I only have half that amount installed for AOS. And none of my ELFX patches are even out in the wild, and this still hasn't dimmed the amount of crazy fans for that mod. Most people don't even realize the conflicts exist.

I think we might now know the problem. According to https://skse.silverlock.org/ You say the last creation time was on Oct 23, and Avast decided to start calling SKSE a virus on Oct 23. You might want to make sure SKSE is still installed, as Avast might have removed it, or even be periodically removing it, causing this exact issue.

It might be better to test on a new save.

It sounds like something is deleting the ModOrganizer.ini periodically. That's what triggers the tutorial message and the custom executables. Perhaps your antivirus?

Interesting concept. This makes storing your hard-earned money in a safe inside your home actually useful.