LostDragonist

Sorry about that. I didn't mean to imply it was the user's fault. I'm sorry my prescription sleep drug ramblings came off as arrogance. It is a problem with MO2. We're looking into getting it fixed. Literally the only reason I even do anything with MO2 is to make it better for people trying to use it. I really hope I'm not secretly hating everyone.

What do you mean "pull out of the data tab"? I suspect you mean the context menu option "Write to file..." which doesn't do what you might assume it does. If you open one of the files in a text editor, you'll see that it's actually a list of the files in the data tab and which mods they originate from. You'd want to access the files directly in the MO2 mods folder. You can right-click the mod you're interested in and choose Open in Explorer to go straight there.

If you can manage to make MO2 crash, it should generate a crash dump file that can usually tell the MO2 team exactly what caused the crash. If using global instances, the file would be in C:\Users\<user>\AppData\Local\ModOrganizer\<instance>\crashDumps. If using a portable instace, the file would be in \crashDumps in the MO2 install folder. Reporting crashes on Github or Discord, with the appropriate logs and this crash dump file, would help fix it.

Double-click the mod to open the mod info dialog. Go to the filetree tab. Find the file you hid. It'll have ".mohidden" appended to the name have a type of "mohidden File". Right-click the file and select Unhide.