DoubleYou

Probably a leftover from previous versions of Mod Organizer. If so, I think clicking Reset Dialogs in Settings should fix it.

Is MO managing BSAs or not?

It appears something is wrong with how your BSAs are set up. Have you unticked all the BSAs or something? What does the Archives.txt look like?

Well, I'm stumped. Post on the bug tracker and see if Tannin can figure it out. https://issue.tannin.eu/tbg/modorganizer/issues/open

Actually, all you need to do to accomplish this is deactivate the three esps and uncheck the three BSAs. No need to delete the files. Unless, of course, you don't want to see it period. Then deletion is better for your OCD.

Did you start the Skyrim game prior to launching Mod Organizer?

Post the mod organizer log for loading the profile.

In Wrye Bash, is the Bashed Patch green or orange?

I'm guessing you failed to run LOOT first.

Question: Have you ever at any time ticked the Hide Inactive ESPs option in Workarounds?

TES5Edit also has a Bash tags autodetection script. Not sure how well it works, but I've used it before, and it's been useful. Haven't used it in awhile, however.

Correct.

Thanks. All the free games through Steam to up my XP

I have 2.3.0 core installed... it's currently the same as 2.2.9 core LOL

That's a rather complicated fix, and the problem I would see is, what if a user decides to use the mod with the hidden file independent of the one we use for the file? And also, most of the time, you can't do that, as there are actually no conflicting files at all. The MO detection merely looks for a scripts folder, not an actual script file.

What you want is in the Data tab in the Right Pane.

Probably an issue with LOOT's masterlist needing an update.

Looks like a fancy disk defragmenter in real-time. Can't imagine something like that could even help a modern pc.

Nothing on your end, if what I presume is the case.

Try this: 1. Open Wrye Bash through MO 2. Scroll down to the very bottom 3. Right-click in the white space below the last plugin 4. Choose File, New Bashed Patch... 5. Right-click on the new Bashed Patch added to the bottom of your plugins 6. Choose Rebuild Patch, and continue

You need to right click on the bashed patch esp.

Probably outdated cleaning note without CRC check.

It's on my tracking list

I'm guessing Chrome botched something again, sort of like how they botched the Download with Manager feature.