When you tell MO2 to close, it first needs that external application to release the VFS lock. Otherwise, if MO2 shut down while the other app was still writing to the virtual folder, you could end up with corrupted configs, missing plugin data, or a broken VFS cache.
If you find yourself force-closing MO2 repeatedly, run before launching MO2—this sometimes allows better process tracking. When you tell MO2 to close, it first
If you’ve ever tried to close Mod Organizer (MO2) only to see the status bar frozen on “Waiting on an application to close before exiting,” you’re not alone. This message isn’t a bug—it’s a safety feature. Below, we’ll unpack why it happens, what MO2 is waiting for, and how to resolve it without damaging your mod setup. What’s Actually Happening Under the Hood? Mod Organizer uses a virtual file system (VFS) . When you launch a tool (like LOOT, xEdit, Bodyslide, or the game itself) through MO2, that tool interacts with a “fake” Data folder containing only your enabled mods. MO2 injects a hook into that external process. If you’ve ever tried to close Mod Organizer
You can also manually check which process has a lock using (Sysinternals): Search for modorganizer.exe → Properties → Handles → look for \Device\VFS . Bottom line: Mod Organizer is trying to protect your setup from corruption. When you see that message, 90% of the time a mod tool is still running in the background. Close it properly, and MO2 will exit instantly. What’s Actually Happening Under the Hood