Launcher crashes on startup if global/local openmw.cfg specifies content file that does not exist in the VFS

I, a fool, thought that surely it would only take a few hours to modify my clean, shiny, OpenMW install. Here I am, three days later, filing an issue report on a crash nobody else is having.

After installing, at the time, the latest dev version of OpenMW and going through MOMW's "Expanded Vanilla" mod list, the launcher began taking an unusually long time to start, and crashing before its window could appear. The config itself is, in theory, without any notable error (though it is quite large).

I'm running Windows 10, using the Windows development build currently available on the website (Today is 7/22/2024, so you don't have to check the date field on this issue, though I initially downloaded it on I think 7/19? Maybe 7/20.) To be blunt, I'm not great at writing up issues, I'm just doing what I was told. Attached are the relevant files. I don't think I need to specify, but the expected launcher behavior was that it would start successfully. To clarify, this is not an issue that I'm having when I try to run the game via the launcher, it's an issue I'm having trying to run the launcher itself.

launcher-crash.7z openmw.cfg launcher.cfg Hell, for good measure, have this, too. CI-ID.txt

Send help.