SSE Edit (XEdit) - Fatal Error [SOLVED]

[Lady Aeleanor]

I get the message:

"Fatal Error - Could not open Registry Key 'Software/Bethesda Softworks/Skyrim Special Edition. This can happen after Steam Updates, run the game's launcher to restore registry settings"

The puzzling thing is, that I installed the game before the SSE 1.6.635 update was launched, and SS Edit was working at that time under my present game version, with no issues. I don't know what changed. I haven't had the game update to the most current SSE version.

Trouble is, I'm still running SSE v. 1.6.356. If I run the Steam launcher, it will trigger a game update - which I'm not ready to do. I have an extremely stable mod list that has no issues, no crashes, no conflicts. I will eventually update, but I'm not willing to do so right now.

I suppose I've answered my own question. I'll just won't be able to use SSE Edit until I update the game to its current version.

[bLaCkShAd0w]

Do you mean 1.6.353 (not 1.6.356)

You can manually repair the registry entry. Not sure if that will satisy xEdit or not but may be worth a shot.

https://www.regfiles.net/registry/skyrim-special-edition-registry

This is the reg entry but do not download and install edits for security reasons just enter it manually. You should already have an entry though and it doesn't contain version info so not sure why xEdit is complaining.

Unless ofcoarse xEdit is correct and there is a problem with the reg entry.

[xybolt]

Did you have consulted the log file? It is possible that you have to clear its content first to have a clear picture of the problem (log entries are appended all the time). Does it say the same thing or something else?

[Lady Aeleanor]

Here's the last entry in the log file:

SSEEdit 4.0.4 (103758D4) starting session 2022-12-19 20:35:38
Using Skyrim Special Edition Data Path:
Using Scripts Path: C:\Users\Owner\Downloads\Downloads August 2022\New Skyrim SE Mods\SSEEdit 4.0.4-164-4-0-4-1636548642\SSEEdit 4.0.4\Edit Scripts\
Using Cache Path:
Using ini:
Fatal: Could not find ini

UPDATE: Like a dumb-belle I had the pathing incorrect. After I looked at the log, I realized I had moved the folder out (or it was gone, for some reason) of the SSE folder. I put it back in and ran the executable from there, and it's working fine now. That's why it wasn't finding the .ini.

I appreciate all the replies! I'll mark the post as [solved]

[xybolt]

Aha, the error is misleading ;)

Glad you have managed to sort it out.

[Lady Aeleanor]

Автор сообщения: xybolt

Aha, the error is misleading ;)

Glad you have managed to sort it out.

Thank you. Merry Christmas!