Newest Skyrim Update Has Completely Broken My Game

[AndrewFaulkner]

So thanks to Bethesda's recent (and completely pointless update) for Skyrim AE my game has completely broke. I get a crash before the main menu even loads & my crash logger is not logging what the cause is. I have the SE version but it has the AE version of skse & any mods that have an AE version I have that version installed (and it was working perfectly fine before the recent update, a few crashes but my crash logger actually logged the cause for those so I was able to figure it out) I updated all the mods I could to their most recent versions. I am at a complete loss. If anyone can help me I'd much appreciate it. 

[dibble201bty]

I have had my game wrecked by this update too. My SKY.UI isn't recognised anymore as well.  

[7531Leonidas]

Go to (and join, so you can post) the Skyrim SE group on the game forums ( https://forums.nexusmods.com/forum/8877-skyrim-se/ ), look around there, several have posted and solved problems with the update and SkyUI.  Most of the mods that are SKSE64 based are not updated yet, you can try the Nexus modding.wiki page that tracks updates at ( https://modding.wiki/en/skyrim/users/skse-plugins ).  There are also a couple of 'downgrader' mods available to help you restore your game to whatever version was working before the update.  I don't know how easy/difficult/involved the processes are, however.  I have managed to stay on 1.6.640 with my setup, so far.

[Pickysaurus]

Moved to the correct forum

[zixi]

@AndrewFaulkner - The SKSE team have updated SKSE - they did that on 7th December. I guess everyone else will gradually check and amend. Anyway, welcome to the SkyrimSE Club recognizable at the moment by the wailing and gnashing of teefs. 

As an aside, I wish software houses would refrain from doing stuff like this just before a big holiday... and yes, I can guess what might motivate them but it doesn't make me happy... 

[Daelyn]

7531Leonidas - "I don't know how easy/difficult/involved the processes are, however.  I have managed to stay on 1.6.640 with my setup, so far."

What did you do to keep your game running? Many people are still experiencing issues getting 1.6.640 running. Mine just crashes on the logo screen, despite doing a lot of things to try and get it working. Nothing works so far. 

[7531Leonidas]

@Daelyn - Re:  1.6.640 - my game never got "upgraded", so I haven't needed a downgrader - I just have been very careful about installing updated files for my mods.  If you are running SKSE-based stuff, I suggest that you check the logs for SKSE in your My Games folder and the logs found in the Data folder of your game installation.  Those logs should be showing you what is not booting properly.

A second problem, where the expanded header information introduced in the CK for 1.6.1130 can cause crashes for lower versions running mods built with the kit, is supposed to be cured by this mod - Backported Extended ESL Support ( https://www.nexusmods.com/skyrimspecialedition/mods/106441 ).  Which, if I am correct, also expands the ESP-FE limit to twice the original.

[Daelyn]

7531Leonidas - Alright thank you. I will go and see about those logs. 

[Daelyn]

On 12/18/2023 at 11:45 PM, 7531Leonidas said:

@Daelyn - Re:  1.6.640 - my game never got "upgraded", so I haven't needed a downgrader - I just have been very careful about installing updated files for my mods.  If you are running SKSE-based stuff, I suggest that you check the logs for SKSE in your My Games folder and the logs found in the Data folder of your game installation.  Those logs should be showing you what is not booting properly.

A second problem, where the expanded header information introduced in the CK for 1.6.1130 can cause crashes for lower versions running mods built with the kit, is supposed to be cured by this mod - Backported Extended ESL Support ( https://www.nexusmods.com/skyrimspecialedition/mods/106441 ).  Which, if I am correct, also expands the ESP-FE limit to twice the original.

Okay, I have no idea what the log files are after looking in both sections. From what I have looked through, the loader file in SKSE in the my games folder this is what it says:

skse64 loader 02020030 01DA3DD9DB677567 6.2 (9200)
config path = c:\program files (x86)\steam\steamapps\common\Skyrim Special Edition\Data\SKSE\skse.ini
procPath = c:\program files (x86)\steam\steamapps\common\Skyrim Special Edition\\SkyrimSE.exe
launching: SkyrimSE.exe (c:\program files (x86)\steam\steamapps\common\Skyrim Special Edition\\SkyrimSE.exe)
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 00010006
dwFileVersionLS = 02800000
dwProductVersionMS = 00010006
dwProductVersionLS = 02800000
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
productVersionStr = 1.6.640.0
version = 0001000602800000
product name = TESV: Skyrim
steam exe
dll = c:\program files (x86)\steam\steamapps\common\Skyrim Special Edition\\skse64_1_6_640.dll
main thread id = 46448
hookBase = 000002F766620000
loadLibraryAAddr = 00007FFE824F0800
getProcAddressAddr = 00007FFE824EB1D0
hook thread complete
launching
 

But none of this helps me. Is there specific file names I am supposed to be looking up?

[7531Leonidas]

Documents/My Games/Skyrim Special Edition/SKSE

Look at SKSE64.log - check the SKSE version that is running, below that are listings for every skse plugin loaded.  You can look for ones that did not load properly.  I think that it states 'did not load', so you could use a text string search "not load" while in the log file to spot problems faster.

In this same folder, are logs created for every .dll that runs.  You could view the folder using the 'Details' setting, then listing by 'Date Modified'.  This will give you a list of those reports, pushing the ones that did not respond farther down.  The ones that did not load should be farther down the list, allowing you to identify the bad ones more quickly.