Games › Skyrim Special Edition
Is it safe to update Skyrim Special Edition?
Likely safe for 1.7.99
Every runtime bump breaks SKSE64 and native SKSE plugins (DLLs) until SKSE, Address Library and plugin authors catch up.
Verdict for 1.7.99
Likely safe
No breakage evidence for 1.7.99: Engine Fixes, PapyrusExt have no release that names the patch, but there are post-patch releases or no breakage reports since. Probably fine; skim the notes. Also check Address Lib manually (Nexus-only, not counted).
- Latest patch
- 1.7.99
- Released
- 2026-08-20
- Source
- The Elder Scrolls V: Skyrim Anniversary Edition - Update 1.7.99 (Updated Aug 27)
- Data refreshed
- 2026-10-15 (UTC)
Core frameworks & loaders
Why these statuses?
- SKSE64: Official page (https://skse.silverlock.org/) lists build 2.3.1 for runtime 1.7.104, matching the latest tag (Bethesda often ships updates to a beta branch first). Latest release is newer than patch 1.7.99, but notes do not explicitly mention that version. (Date is the tagged commit on GitHub; builds are published on the official site.)
- Engine Fixes: Latest release is newer than patch 1.7.99, but notes do not explicitly mention that version.
- PapyrusExt: Latest release is newer than patch 1.7.99, but notes do not explicitly mention that version.
- CrashLogger: Latest release notes mention patch 1.7.99 and the release is on/after the patch date.
- Address Lib: Distributed on Nexus Mods only; ModSafe does not scrape Nexus. Check the mod page.
Statuses are inferred from public release data (Steam news, GitHub, Thunderstore, Mojang/Fabric/Forge/NeoForge/Modrinth APIs). They are not guarantees — verify on each project's page before updating. Items marked “Check manually” are not counted in the verdict.
Patch-day alerts
Get patch-day alerts: know if your mods survived before you update.
Form not loading? Subscribe on beehiiv →
Skyrim Special Edition modding FAQ
Is it safe to update Skyrim Special Edition with mods?
Current verdict: Likely safe. No breakage evidence for 1.7.99: Engine Fixes, PapyrusExt have no release that names the patch, but there are post-patch releases or no breakage reports since. Probably fine; skim the notes. Also check Address Lib manually (Nexus-only, not counted). Latest patch tracked: 1.7.99 (2026-08-20).
Why do Skyrim Special Edition mods break after a patch?
Every runtime bump breaks SKSE64 and native SKSE plugins (DLLs) until SKSE, Address Library and plugin authors catch up.
Which Skyrim Special Edition frameworks does ModSafe track?
Automatically: Skyrim Script Extender (SKSE64), SSE Engine Fixes, powerofthree's Papyrus Extender, Crash Logger SSE AE VR. Linked for manual checks (no public release API): Address Library for SKSE Plugins.
What do the status labels mean?
Safe: a release explicitly supports the current patch (release notes, the maintainer's official page, or a stable build for that game version). Likely safe: a release is dated after the patch but doesn't name it, or the patch is over a week old with no breakage reports on the project's issue tracker. Just patched, wait: the patch is under 7 days old and the framework hasn't updated. Breakage reported: open issues report the framework broke after the patch. Not ported yet (Minecraft): no build exists for that version. Not affected by patches: version-agnostic tools such as mod managers or generic loaders; they don't count toward the verdict.
Where does the data come from?
Game patches come from official Steam announcements (app 489830). Framework data comes from public release APIs (GitHub, Thunderstore, Fabric/Forge/NeoForge meta, Modrinth). ModSafe does not scrape Nexus Mods or SteamDB.