Skyrim mods not working after an update? SKSE, Address Library and version status

The current Steam build of Skyrim Special Edition and Anniversary Edition is 1.7.104, a hotfix released on 27 August 2026, one week after the larger 1.7.99 update. If your mods stopped working after either one, the usual cause is that the new SkyrimSE.exe broke SKSE and every DLL plugin built for the old executable. The fix is to update SKSE, then Address Library, then each DLL mod. If you can’t wait for mod authors, you can downgrade the game and stop it updating instead.

Quick answer: why your Skyrim mods stopped working (November 2026)

Bethesda Game Studios released update 1.7.99 on Steam on 20 August 2026 and hotfix 1.7.104 on 27 August 2026. Each one replaced SkyrimSE.exe, and SKSE64 plus every SKSE plugin is compiled for one exact executable. Until each of those files is rebuilt for 1.7.104, it either refuses to load or crashes the game.

According to UESP, 1.7.99 added bigger console mod storage, Creation bundles in the Creations menu, localization export in the Creation Kit, and an option for Verified Creators’ Creations to be achievement or trophy friendly. The 1.7.104 hotfix, per UESP, fixed problems on Xbox and PlayStation. On PC it still changed the executable a second time. That is why some players who had fixed everything for 1.7.99 found their setup broken again a week later.

The fix order as of November 2026:

1. Back up your saves and your game folder.
2. Install SKSE64 2.3.1 (SKSE 2.3.0 was the build for 1.7.99 and no longer matches).
3. Install the Address Library for SKSE Plugins file for 1.7.104.
4. Update each DLL mod to a 1.7.104-compatible build, or disable it until one exists.
5. If a mod you can’t play without isn’t updated, downgrade with the Best of Both Worlds Downgrade Patcher and freeze the game.

Step 1: Find out what actually updated

First, confirm that the game really updated. Plenty of “update broke my mods” reports turn out to be a mod manager update, a single mod update or a Creations download, and each of those has a different fix.

Check your SkyrimSE.exe version

The quickest check is in Windows. Go to your Skyrim Special Edition install folder, right-click SkyrimSE.exe, choose Properties, then open the Details tab. The File version line shows the runtime, such as 1.7.104.0 or 1.6.1170.0. The game also prints its version at the bottom of the main menu, but if SKSE crashes the game first you won’t see it, so the file check is more reliable.

That number decides every download you pick. A Steam guide that says “get the AE build” isn’t enough. You need the build whose number matches your exe.

Game update vs mod manager update vs mod update

Each of these three events looks like “everything broke”, but they have different causes:

A GitHub issue opened on 22 May 2026 shows what a manager-side failure looks like. After updating to Vortex 2.02.2, plugins appeared enabled but none of them worked in game. That was three months before any Skyrim update. If your exe version hasn’t changed, go straight to the mod manager section below.

Steam, GOG and Microsoft Store/Game Pass: which ones SKSE supports

SKSE supports the Steam build of the main release, plus a separate GOG build. The official SKSE site at skse.silverlock.org lists the GOG Anniversary Edition build as SKSE 2.2.6 for game version 1.6.1179, not as a current latest release, and lists newer SKSE releases for later game versions. GOG players are not on 1.7.104, so the Steam version numbers in this guide don’t apply to them. The Microsoft Store and Game Pass PC version is not supported by SKSE at all.

What breaks after an update and what doesn’t

Most of your mod list survives an update. ESP, ESM and ESL plugins, meshes, textures, sound files and most Papyrus-only scripts are data the engine reads. A new exe rarely changes how it reads them. What breaks is any compiled DLL that hooks into the engine’s memory. Those DLLs live in Data\SKSE\Plugins.

A DLL plugin works by finding specific functions and values inside SkyrimSE.exe. When Bethesda recompiles the executable, those addresses move. Address Library for SKSE Plugins, created by meh321, gives plugins a lookup table of IDs so they can find the new addresses. That only works if the table matches your exact runtime and the plugin can read the table’s format.

Bethesda said the 1.7.99 update should not affect load orders, as Digital Citizen reported. That’s true. Your plugin order is untouched. It just doesn’t help PC modders, because the damage is in the SKSE layer, which Bethesda doesn’t ship or support. On a big list, that layer includes your UI framework, animation framework, character creator and engine fixes.

Version compatibility table (1.7.104)

Use this table to match your edition to the right SKSE build and Address Library file. The data comes from the official SKSE site and the SKSE and Address Library pages, as of November 2026.

Popular SKSE mods: 1.7.104 status

Fix it: update your mods to 1.7.104

This is the path to take if you want to stay on the current game. Work through it in order, because each step depends on the one before it.

Install SKSE 2.3.1 the right way

SKSE has two parts, and both must be current. The loader and the main DLL (skse64_loader.exe and skse64_1_7_104.dll) go in the game root next to SkyrimSE.exe. The Data folder scripts go through your mod manager or into Data.

Nexus Mods moderators said in a pinned post that when SKSE fails after the update, the loader probably wasn’t replaced. If Windows didn’t confirm an overwrite, or an old skse64_loader.exe is still in the root, your launches still go through the old build. The fix is to delete the old loader and every old skse64_1_*.dll from the root, then copy in the 2.3.1 files.

Then launch through skse64_loader.exe, or the SKSE entry in Mod Organizer 2 or Vortex. One reader complaint is that the only way to get mods working is launching the loader directly. That’s expected. The Steam Play button and SkyrimSE.exe start the game without SKSE, so none of your SKSE plugins load.

Address Library 1.7.104 and the new format

Install the Address Library file labelled for 1.7.104. After install, Data\SKSE\Plugins should contain version-1-7-104-0.bin. meh321’s original is on Nexus Mods. A reupload of the 1.7.104 file dated 27 August 2026 (6.33 MiB) is also hosted on ModPub.

There is a second trap. Starting with 1.7.99, the library uses a new format. Plugins built against older versions of CommonLibSSE-NG can’t read it and fail with “Unsupported address library format: 5”. According to a GitHub issue on the SkyrimNet plugin, CommonLibSSE-NG 12.1.0 supports the new format. Each plugin has to be rebuilt by its author, and nothing you install can make an old DLL read the new file.

Engine Fixes, Papyrus Extender, RaceMenu, Community Shaders

The most-used mods need different handling.

• SSE Engine Fixes. On the mod’s Nexus page, users report that the newer build from the alandtse/EngineFixesSkyrim64 GitHub repository loads all fixes on 1.7.104, while others are still asking for a Nexus update. Follow the install notes for the exact build you download. If it still uses the Part 2 preloader (d3dx9_42.dll, tbb.dll and tbbmalloc.dll), those files go manually into the game root, because mod managers usually don’t place them there.
• powerofthree’s Papyrus Extender and similar script libraries. Open the Files tab and pick the file built for your runtime. Many mods depend on these quietly, so one outdated library can disable a dozen others.
• RaceMenu. The SKSE plugin loader disabled it as “incompatible with current version of the game”, and a Nexus forums thread asked for an update timeline. As of a sticky on the RaceMenu page dated 12 November 2026, the Nexus files are not updated. The page points to a free build on expired6978’s Patreon, and users report the beta working on 1.7.104 with SKSE 2.3.1.
• Community Shaders. See the “Failed to find offset” entry in the error lookup below.

Read the SKSE log to find the plugin that’s holding you back

After a failed or partial launch, open Documents\My Games\Skyrim Special Edition\SKSE\skse64.log. Every DLL in Data\SKSE\Plugins is listed with a result. Plugins that loaded show as loaded, and ones that were refused show as incompatible or disabled, with a reason. Work through that list. Each refused plugin is either updated on its page, needs a rebuild that hasn’t happened yet, or should be disabled for now.

Error message lookup

Most post-update errors fall into six patterns. Find the text you see, then apply the fix.

“Unsupported address library format: 5”

The library you installed is current, but this plugin is too old to read it. No settings change fixes that. Look for a 1.7.99+ build on the mod’s page. If there isn’t one, disable the DLL or downgrade.

Missing version-1-7-104-0.bin

A common reader complaint is “missing address library version-1-7-104-0.bin but I installed it”. Usually the file isn’t where the game looks for it. Check, in this order:

1. Did the mod manager deploy it? In Vortex, deploy again. In MO2, confirm the mod is enabled in the left pane.
2. Is the file name exact? It should be version-1-7-104-0.bin, not an older versionlib-1-6-*.bin.
3. Is it in Data\SKSE\Plugins and not nested an extra folder deep?

“Failed to find offset for Address Library ID!”

Community Shaders users on 1.7.104 report this error. The mod’s Nexus page recommends using the correct Engine Fixes build, then deleting the ShaderCache folder and the SKSE/Plugins/CommunityShaders overwrite folders so the shaders and settings are rebuilt cleanly. With other mods, the same error means the plugin needs an update.

“Incompatible with current version of the game” (RaceMenu and others)

This message comes from the SKSE plugin loader. It’s a safety check that stops an outdated DLL before it can crash the game. Your game still runs, just without that mod. For a character-creation mod like RaceMenu, that means missing sliders and possibly broken presets on existing characters, so don’t save over an important character while it’s disabled.

SKSE says the runtime is a “newer version”

Your exe is 1.7.104 and your loader is older. Replace skse64_loader.exe and the DLL in the root with the 2.3.1 files. If the message still names the old version, a second copy of the old loader is being launched, often from a stale shortcut or an MO2 executable entry.

Game closes instantly or the SKSE launcher does nothing

Some readers report the game won’t start on 1.7.104 even after installing SKSE 2.3.1. Usually the loader started fine and an SKSE plugin crashed during load. Check the newest skse64.log for the last plugin listed. Then disable DLL mods in batches until the game reaches the main menu, and add them back one at a time.

Or roll back: downgrade to 1.6.1170 or 1.5.97

Downgrading makes sense when a DLL mod your playthrough depends on hasn’t been updated, or when you’re deep into a long save and don’t want to risk it. If everything you use has a 1.7.104 build, stay current.

There’s also a fair counter-argument to downgrading. Mod authors are moving to the new runtime. USSEP 4.3.9c already requires game version 1.7.99 or newer, so a downgraded game has to keep the older USSEP file that matched it. Its companion, Unofficial Skyrim Creation Club Content Patches, now lists the same requirement. The longer you stay on 1.6.1170, the more of your mods stay on older versions.

Best of Both Worlds Downgrade Patcher

According to its Nexus Mods page, the Best of Both Worlds Downgrade Patcher supports Steam 1.7.104 to 1.6.1170, and 1.6.1170 to 1.5.97. It patches your installed files instead of making you download old builds yourself.

1. Back up saves and the game folder.
2. Make sure Steam has finished updating to 1.7.104. The patcher expects that starting version.
3. Run the patcher on your game folder and choose 1.6.1170 or 1.5.97.
4. Check the version on SkyrimSE.exe under Properties > Details.
5. Install the matching SKSE and Address Library from the table above, plus older files of any mod that has moved to 1.7.x.
6. Lock updates (next section) before you open Steam again.

Manual Steam depot download

The other route is Steam’s download_depot console command. It uses app ID 489830 plus the depot and manifest IDs of the build you want, and it downloads old files you then copy over your install manually. It works, but it’s slower and easier to get wrong than the patcher. You also have to find the correct manifest IDs from a source you trust.

Anniversary Edition content and Creations after a downgrade

On a downgraded exe, your plugin files still load. But Creations features added in 1.7.99, such as Creation bundles in the menu, belong to the new runtime. Plan on managing AE content through your mod manager and treating the in-game Creations menu as off limits until you update again.

Stop the next update from breaking everything

On Steam, the reliable way to freeze the game is to make the app manifest read-only. Steam settings alone don’t fully stop updates.

1. Close Steam completely.
2. Open your steamapps folder (inside the Steam library that holds Skyrim).
3. Right-click appmanifest_489830.acf, choose Properties, tick Read-only, and apply. Digital Citizen covered this method during the 1.7.99 update.
4. In Steam, set Skyrim’s update option to “Only update this game when I launch it” as a second layer.
5. Launch through skse64_loader.exe or your mod manager, not the Steam Play button.
6. Keep a zipped backup of the game folder and your saves.

Keep the game, Mod Organizer 2 and Vortex outside OneDrive-synced folders such as Documents and Desktop. OneDrive file locking and cloud-only placeholders cause deployment failures that look a lot like update breakage. GOG Galaxy users can turn off automatic updates in the game’s settings.

To update later on purpose, untick Read-only, let Steam update, then repeat the SKSE and Address Library steps. Do this only once your DLL mods have builds ready.

Mods still broken after updating? Mod manager checks

If SKSE loads cleanly and the log shows your plugins as loaded but the game still looks unmodded, the problem is almost always deployment.

Vortex: plugins enabled but nothing loads (the Helgen cart test)

The classic symptom is “plugins show enabled in Vortex but I just ride the cart into Helgen again”. A full list usually changes the opening scene or adds start options, so a vanilla cart ride means nothing deployed. Click Deploy Mods, check the Plugins tab, and run LOOT sorting. If Vortex itself recently updated, re-check its game folder path and staging folder. That’s what went wrong in the Vortex 2.02.2 GitHub report.

Mod Organizer 2: executable paths after an update

MO2 stores executable paths per profile. After you reinstall SKSE, open the Executables menu and confirm the SKSE entry points at the skse64_loader.exe in your game root. An old entry left over from a previous install starts the wrong loader. Plugins with greyed-out or missing masters in the right pane show what is actually loading.

Testing on a new save vs your existing save

Test on a new character first, using a start-alternative mod or the coc console command to skip the intro. If a new game works and your old save crashes, the save has data from a mod that’s now missing or changed. Re-enable the same versions, or roll back to a backup.

Xbox and PlayStation: mods not working after the update

Consoles have no SKSE or DLL plugins, so the console problems are about Creations: load order, downloads and storage.

Xbox One and Xbox Series X|S

According to Notebookcheck, 1.7.99 raised Creation mod storage on Xbox and PlayStation 5 to 15 GB, up from the old 5 GB cap. The 1.7.104 hotfix, per UESP, then fixed Xbox and PlayStation issues. Before you change anything, let the update finish, fully restart the console and reopen Creations. A broken load order right after the update is often a sync that hasn’t finished yet.

PS4 vs PS5 storage differences

PS4 storage went up to about 16 GB. Bethesda warned that download size and installed size can differ and that storage partitioning may limit how many large Creations you can install at once, even when the total isn’t used up. On PS4, a large mod that fails to install with space left over is usually hitting that partition limit. Remove another large Creation to make room.

Rebuilding your load order after an update

1. Open Creations, then Load Order, and note which entries are missing or show errors.
2. Re-download any Creation flagged as missing.
3. Put master and patch mods first, overhauls next and small tweaks last.
4. If the game crashes, disable mods in halves until it stops, then re-enable one by one.
5. Exit to the main menu and reopen Load Order to confirm the change stuck.

If your load order keeps reverting every time you leave the menu, a Creation is usually still downloading or failing in the background. Let all downloads finish, restart, then reorder.

Once your game reaches the main menu, the update itself is behind you. Lock it with the read-only manifest so the next patch doesn’t catch you mid-playthrough. Then update your DLL mods only when their authors release new builds, not when Steam pushes a patch. The same framework-first order also works for Cyberpunk 2077 mods not working after a patch.

FAQ

How do I fix Skyrim mods after an update?

Check your SkyrimSE.exe version first. On Steam 1.7.104, install SKSE64 2.3.1 (loader and DLL in the game root), then the 1.7.104 Address Library file, then 1.7.104 builds of each DLL mod. Launch through skse64_loader.exe and read skse64.log for any plugin still refused.

Did the new Skyrim update break mods?

Yes, on PC it broke SKSE-based mods. Updates 1.7.99 (20 August 2026) and 1.7.104 (27 August 2026) changed the executable, which breaks SKSE and DLL plugins until they’re rebuilt. Plugin-only, texture and mesh mods mostly kept working, and Bethesda said load orders shouldn’t be affected.

Why are my Skyrim mods not launching?

Most often the game is being launched without SKSE, or the old SKSE loader is still in the game root. Start through skse64_loader.exe or your manager’s SKSE entry, and make sure the 2.3.1 loader overwrote the old one.

Why aren’t my mods working in Skyrim?

If the game starts but looks vanilla, your mod manager probably didn’t deploy. Redeploy in Vortex or check that mods are enabled in MO2, sort with LOOT, and test on a new save.

What version of SKSE do I need for Skyrim 1.7.104?

You need SKSE64 2.3.1, from skse.silverlock.org or the SKSE Nexus Mods page. SKSE 2.3.0 matched 1.7.99 only. GOG players on 1.6.1179 need the 2.2.6 GOG build.

Which Address Library do I need for 1.7.104?

You need the Address Library for SKSE Plugins file for 1.7.104, which installs version-1-7-104-0.bin into Data\SKSE\Plugins. Plugins that report “format: 5” need their own update on top of that.

How do I downgrade Skyrim to 1.6.1170?

Back up first, then use the Best of Both Worlds Downgrade Patcher, which supports Steam 1.7.104 to 1.6.1170 (and on to 1.5.97). Install the matching older SKSE and Address Library files, then make appmanifest_489830.acf read-only.

How do I stop Steam from updating Skyrim?

Close Steam, go to steamapps, and set appmanifest_489830.acf to read-only. Set the game to update only on launch as a backup, and launch through SKSE.

Why are my mods not working on Xbox after the Skyrim update?

Usually Creations are still syncing or re-downloading, or the load order shifted. Let downloads finish, restart, check Creations > Load Order, re-download missing mods and re-sort.

Why are my Skyrim mods not working on PS4 or PS5?

On PS5 it’s usually the same load order or download issue as on Xbox, now with a 15 GB limit. On PS4, storage partitioning can block large Creations even when the roughly 16 GB total isn’t full, so remove a large mod to make room.

What changed

• Nov 13, 2026 First published.

About the article

NA

Written by Nico Albrecht

Nico covers RPG and action game mods, Bethesda games and the weekly trending mod roundups. He pays close attention to requirements and load order, so a mod list is something you can install without breaking your save.

• Fact-checked by Hollis Tremaine against the sources listed below before publication.
• Published November 13, 2026

Sources (8)

1. SKSE64 official site (skse.silverlock.org) (skse.silverlock.org)
2. Skyrim Script Extender (SKSE64) at Skyrim Special Edition Nexus (nexusmods.com)
3. SKSE64 Nexus posts tab (pinned Address Library note) (nexusmods.com)
4. ianpatt/skse64 releases on GitHub (github.com)
5. Skyrim:Special Edition Patch – UESP Wiki (en.uesp.net)
6. Skyrim Special Edition August 20 update patch notes – DSOGaming (dsogaming.com)
7. SkyrimNet-GamePlugin issue 577: Unsupported address library format 5 (github.com)
8. Address Library for SKSE Plugins files – ModPub (mod.pub)

Spotted an error? Tell us