Galrick12

Thanks for the help. I was afraid of that. I may give tech support a shot, but is there any way to identify which files or memory locations MO affects in this manner in order to narrow it down? Unfortunatly, the on-access and on-demand exclusions do not seem to resolve this issue. I have added the entire Mod Organizer folder as well as the individual executables and dlls with no change. I didn't have this problem until recently, and I think it has to do with my update to the 2015 version of Bitdefender Total Security from 2014. Edit: I was eventually able to resolve this issue. Just adding the MO folder to the exclusion ruels is not enough. I also had to add all relevant executables, MO, LOOT, SKSE_loader, etc. to the excluded processes. Thank you everyone for your help.

Tannin, I believe the problem here is related to the BitDefender security software as you suspected. I had the same problem after updating Bitdefender Total security to 2015 (it seemed fine before this for a long time for some reason). After I uninstalled Bitdefender I was able to properly run LOOT and Skyrim, but the problem returns upon reinstalling Bitdefender. I still have no idea which aspect of Bitdefender might be blocking MO or how that might be corrected. Is there any help you can offer to narrow this down?