[MODS] I have a dirty mod problem and TES5Edit is not working.

[Lysergamide]

I figured I would post here because I've been trying to work on this for about half a day now, and it's the end of my Friday night. Thought I might get an expedient response here.

I ♥♥♥♥♥♥ up my game (I haven't even played yet) by installing SKSE64 in two different ways. I thought I had removed the first, but the second, more recommended way made my LOOT tell me every official DLC required cleaning.

I have tried uninstalling and reinstalling the game to remove conflicts, but they are still present. I have checked the integrity of the game files multiple times in the correct order I have seen from other posts.

I have tried to use TES5Edit to clean it all up, but it keeps telling me:
"Fatal: Could not open registry key: \SOFTWARE\Bethesda\Software\Skyrim"

This reults in a failure to find the .ini file even though I have checked to see if there is one. There is one. I have my game on a different drive than the save-game storage drive, but I tried switching it to the same drive. Same error.

I should have gone without the SKSE64 for my first modded playthrough, but I didn't. I just need help to get out of this hole.

I am using the Curse client for mod management, so I don't end up screwing with the files too much. I originally used it in an interesting way to install SKSE64, which didn't seem to cause conflicts, but didn't allow me to launch it from the correct launcher. I have tried so many of the solutions provided from multiple sources for this specific error, so I don't want to sound like I'm reposting. I'm just about to rip my hair out, and it takes a lot of effort for me to make a post about something like this.

Please send help.

[DrNewcenstein]

1. Uninstall any mod manager you have.
2. Follow the directions that came with SKSE64 to install it.
3. Do not use LOOT. It's poking through your system registry. It has no business looking through your operating system's central nervous system, and one wrong move could completely cripple your computer, and you end up formatting and starting over installing Windows. You lose your Documents, your Pictures, you Music, and everything on C:\ drive.

"Cleaning" vanilla files is not something that is accomplished by verifying game files or re-downloading them. This is a wildly inappropriate term for correcting various typos in the original files that have the potential to cause everything from wolves not having an audible howl to the dead guy in Volunruud's entrance not displaying, to animals falling from the sky to their deaths, to quests failing to update properly, forcing you to start the game all over from the wagon in Helgen.

Except that "cleaning" them doesn't always fix the problem, and some mods rely on those "dirty" vanilla files to function, and cleaning either one breaks both.

I'm running vanilla "dirty" DLCs along with several mods I've butchered myself, and the sky is not falling.

[Kevin Flemming]

Nothing wrong with LOOT. Stop spreading nonsense.

[smr1957]

Disregard what DrNewcenstein said with regard to LOOT. It is completely and totally wrong.

For proper and accurate modding information, see:
Skyrim SE: Guides and Resources by Ilja
http://steamcommunity.com/app/489830/discussions/0/340412122413706606/
VERY IMPORTANT if you wish to successfully mod your game

You may also need this:
Resetting SkyrimSE to Vanilla or A Clean Reinstall by grimus -
http://steamcommunity.com/app/489830/discussions/0/312265589446940121/

Ninja'd by HΛɌÐCΘɌΞVIBΞƵ™

[Lysergamide]

Thank you so much for taking the time to answer my question. I read a lot of opinions saying that cleaning the dirty files was necessary, but I have no saved games currently. All of those are on my old, dirty PS3 that I don't think anyone will ever use again. I'll get SKSE64 back on there and ignore the dirty file warnings that seemed to have no actual impact. I kind of expected as much when I saw what caused the warnings. I am starting a new game anyway, and I tried desperately to properly follow proper procedures.

But anyway, all I care about on my C:\ drive is my operating system, which I could replace. Everything else is stored somewhere else because I understand the importance of the distinction.

Your insight has kind of inspired me more to start modding this game myself (I'm a computer programmer).

Thank you again!

[Lysergamide]

Now I'm overloaded with information at 3:30 in the morning, but thank you guys for helping. I'll look into it all.

[Void#151625]

btw you use the wrong program Tes5edit is for the 32 bit version
what you need is SSEedit what is for the Special Edition 64 bit version!
main cause TES5edit uses bsa archive system of old 32 bit
SSEedit uses archive of the new archive version used in Special edition in 64bit.
google SSEedit you should find it on nexusmod

[MysticMalevolence]

SSEEdit and Tes5Edit are the same program; you must rename the .exe appropriately to use it for SSE, as (mostly) detailed in the readme.

[Mringasa]

Quick question. When you uninstalled/reinstalled, did you start the game up from the Skyrim launcher? If you don't, it won't have a generated .ini file to recognize. Every official DLC does need cleaning, btw. They all have a bunch of ITMs and such. Avrie wrote a badass cleaning guide for it though here on Steam.