I first encountered this when I tried to convert specifically "Enchanting Freedom" off Nexus, the SE version. Previously I was able to convert mods just fine from LE to SE. FYI, my system and my installation are both healthy and I've found no problems, down to checking for temperatures or even script lag- You name it, I've checked it. So this strange error in CK when converting that specific mod, is either the CK or the mod going a bit crazy. Obviously, I've updated my CK and included all fixes and bells and whistles, properly installed. As far as I can tell after looking into it more extensively, this book seems to have been included in the game by Bethesda as a guide or translation manual for fonts, font effects, font size and so on. I personally use no fonts mod except one that replaces default fonts for Diablo fonts. I do not use book mods, I do not use other font mods, no font effects, nothing at all. Now, why the CK detects problems with that book when trying to convert Enchanting Freedom is 100% beyond me. So is the reason behind Enchanting Freedom not being properly converted BUT STILL BEING ON SE NEXUS- The author puts a file on the SE side of Nexus and disappears, then people have to find what's wrong and fix it... 10/10. There's even a guy there who low key tells people it's their fault and they should learn to use the CK, condescending AF while at it, so it's a damned circus, plus that guy also insists other similar mods are trash because they CTD for him- So... He better follow his own damned advice right there... SMH... Any way back to the point; I'm dropping Enchanting Freedom and finding another mod to do what that does. The book is vanilla, normally inaccessible, its title is indeed just letters and numbers as PeterMartyr mentions. That's all. Now specifically to PeterMartyr- Look, this has nothing to do with loose strings, or language strings, or the game's cache, or other crap in the Data Folder. And I have no idea what you're on about, when you talk about "Purging" or "Much To About Nothing + Safe to Ignore" because that's barely English at this point, no offense, you're trying to help but your words are confusing my friend xD As for your advice to read warnings and try to understand crap, this is all EXACTLY ABOUT THAT, the OP started the thread because he saw the error and is trying to comprehend what went wrong. And in the end you just conclude with "Ignore Beth problems" which is contradictory to what you've been saying... Those of us with the same issue, can't ignore it because it doesn't feel like we should risk losing a 100% working installation because we decided to convert and ignore that error. As you say, we just want to find out what's wrong and fix it. Seriously... Sigh...