Colban

I'm having a similar problem. Luckily like Vulgar, I have a 254 build I can fall back on, but any attempt to launch Skyrim with version 262 in my directory ends in a "Skyrim has stopped working" prompt before the game even launches; whether I use SKSE or just the vanilla launcher, it crashes. Only removing the ENB files or replacing them with the older 254 version's fixes the issue for me.It should be noted that I'm not even utilizing an ENB and this is happening, just ENBoost. No extra fluff. UsePatchSpeedhackWithoutGraphics can be set to either true or false, both crash on me.MINI-UPDATE: I'm thinking the 262 version of d3d9.dll might be the issue, as I can swap out the enbhost file and it'll run (Although it'll still be recognized as 254), but the second the new d3d9 gets in, it stops working.

After seeing Neovalen mention it and browsing the forum a bit, I installed the Fomod plugin update from the MO page and Immersive Armors proceeded to install completely and gracefully.I'll do a little more testing with some of the other problem mods and speak up if I have any more issues, but hopefully that fixed it for me.

I've been having this issue myself, most notably with Immersive Armors v7 and Winter is Coming. For IA7, all it unpacks is the ESP, no matching BSA or anything. For WiC it extracts everything but the textures, only meshes and the ESP, so I end up having a Skyrim full of people wearing big, shiny purple capes.I've manually solved both problems by extracting the files by hand, but it's still a hassle. MO didn't used to do this, as the first time I installed WiC it worked fine.I haven't changed any Extractor settings, either.