Game Pass discussion is off topic and will be removed. As usual, beta updates are not supported.
Status updates: 2024-10-19: I have purchased a code signing certificate in order to hopefully reduce virus scanner false positives. This largely seems to be a racket where you pay them $657 every three years, and then virus scanners are happier with your products, but that's the world we live in. Thanks to Magicockerel for generously donating to cover part of the cost (unprompted!). Please let me know if this breaks anything or you still get virus scanner issues. 2024-10-20: An update is out (0.2.15) that should fix issues with signing verification on different operating system versions. 2024-11-19: Bethesda has moved the beta runtime to release (1.14.74). SFSE has been updated for this version.
Older updates:
Spoiler:
Show
2024-05-15: The beta runtime has been released, and as usual is different from the version that was out weeks ago. An update is available adding compatibility with 1.11.36. Let's see if the changes to the loader help with virus scanners. 2024-06-09: Game update 1.12.30 has been released, and is being analyzed. This takes many hours and may not finish until late tonight. To be clear: I will probably need to sleep before the whole thing finishes. 2024-06-10: An update is available adding compatibility with 1.12.30. 2024-06-14: Game update 1.12.32 has been released, and is being analyzed. SFSE has been updated for this version. 2024-07-03: Game update 1.12.36 and an update for SFSE has been released. Imagine releasing a patch before a holiday weekend. 2024-08-20: Game update 1.13.61 has been released very late in the day, and is being analyzed. There is a very good chance that I will need to sleep before the automated steps finish. 2024-08-21: The automated part of the analysis completed, but took a very long time due to changes in the large game executable (made worse by the release time of the patch). An update for SFSE has been released. 2024-08-23: Some new preliminary serialization code appears to be causing problems. Sorry for any trouble. Please download version 0.2.12 to resolve the issues. 2024-09-30: A game update has been released that requires an update to SFSE. 1.14.70 is currently being analyzed. Bethesda has made a major change to the base form type in 1.14.70, so all gameplay plugins will need to be recompiled. Expect some plugin developers to have not marked up their compatibility data correctly and for some plugins to crash. An update for SFSE has been released.
Crashing on startup? Remove everything from Data/SFSE/Plugins. Empty halted loader window? Remove VCRUNTIME140_1.dll from the game folder, and don't install BetterConsole that way. Interact key (E) not working? Check your UI mods.
We are getting frequent reports via the "Report Abuse" button that this mod contains malware/viruses/other malicious files. I would like to reassure any users seeing these messages that it is a false positive and that you should add an exception for SFSE to your virus scanner. You should also report this false positive to your virus scan provider so they can correct their detection.
All files shared on Nexus Mods are scanned for viruses before being made available and you can see the "Virus Scan" result just below the image at the top of the page. The Virus Total report can be viewed by clicking the green checkmark in the Files tab, here's an example of the scan result for 0.1.3.
Please do not file reports stating this mod contains a virus as it has been fully verified by our team at Nexus Mods.
Question: Why are the Script Extender version different between the one uploaded here, on NexusMods, and on the official site? The one on https://sfse.silverlock.org/ is 2.15, but the one here is 2.16.
When transfering from Vortex to MO2, I spent over a week trying to figure out why the .silverlock version wouldn't load, going so far as to reinstall my game and modlist, one mod at a time. Even went to the official github, and combed through its reported bugs. Come to find out... mismatched versions between sites. Dunno which is the "official" version, now.
i need advice. been playing since launch.but i recently formatted laptop ive installed SFSE correctly and using mod manager but now when i launch, it says cant load arguments. HOW do i argue wwith my laptop .
You have set additional "launch options" in Steam, and have screwed it up. RIght-click on the game in Steam, go to Properties, the General tab, and then clear our the Launch Options box.
I did copy "sfse_1_14_74.dll" and "sfse_loader.exe" into starfield folder. Discription says dont touch "src"folder, besides that its only 2 txt readme files. And how I suppose to update sfse_<game version>.dll?
The certificate database on your computer is out of date or broken, or you've done something to break signature verification. You will need to fix that to continue.
All files in the src (sfse-0.2.16.tar.gz) get corrupted after a game crash and only way to fix SFSE is to delete src folder and copy the archive files into the data folder. Then SFSE will run correctly again.
I had no intention to make mods with SFSE, so i did not copy src folder to game data, only "sfse_loader.exe" and "sfse_1_14_74.dll". Maybe mod requires specific runtime to run?
The src folder is not needed to run SFSE. If it's launching at all (which it is) then you have the runtime you need.
Again, the certificate database on your computer is out of date or broken, or you've done something to break signature verification. This is what "WinVerifyTrust failed: 800B010A 800B010A" means.
Hi, just a quick question. I haven't played Starfield in about a year. But I'm currently in the middle of a save that I never finished and don't really want to update the game so that my existing mods don't break.
Can the latest version of SFSE work on an older version of the game? (mine is before the Shattered Star update)
Not sure why, but I have to click on SFSE on Vortex before booting up the game each time now and click Reinstall, and if I don't no SFSE mods work in the game like SFSE keeps disabling itself. Any ideas?
Having a problem here. I've tried pasting the Starfield mod shortcut and the .dll file into the Starfield file directory, but it keeps saying that 'starfield.exe' can not be found. Also, I didn't initially do the steps listed at the bottom of the Vortex mod page, so that might've contributed to the problem. All I want is the BAKA achievement enabler, since my achievements were disabled simply for using the commands to fix a broken quest. Any assistance is appreciated.
If you are talking about the sfse_loader.exe not being in the download here then you have a major computer problem which is corrupting the download and you may have to wipe your PC and reinstall Windows from scratch. I have downloaded this file several times with no issues and if installed correctly the SFSE works flawlessly with the latest Starfield version and I don't use mods that are not updated for it.
If Starfield.exe is not there then somehow it got deleted or you did not install the SFSE to the right directory and you will get the error message. I once installed the SFSE to Skyrim SE directory by mistake and it took me a while to figure out what had happened. Ugh - Yeah that one was on me. The Starfield.exe should have the Starfield icon beside the name and the type should be application. If you have Windows Explorer show extensions the .exe will show on it. If you do not have this at all then Starfield won't even launch and you need to have Steam verify the game files and it will add the Starfield.exe.
same No use of SFSE - I can load any save I got, ignoring the mods save uses. But if SFSE loader was used - even clear game (without active mods) can't be load and crashing (with GPU driver + Steam crash as well o_O)
I'm having a similar problem. I uninstalled all mods, deleted the plugins folder under sfse, reinstalled sfse, and when I try to launch with it, I get a few moments of spinny-spinny in Vortex, then nothing. Trainwreck is utterly useless, as all it records for the crash is: Starfield v1.14.74 trainwreck v1.1.0
Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x000000000000
SYSTEM SPECS: OS: Windows 10 Pro 23H2 22631.5039 CPU: AuthenticAMD AMD Ryzen Threadripper PRO 3955WX 16-Cores The game launches normally through Steam, but I don't have any sfse, of course. I hate Starfield. I hate Bugthesda.
It won't even load. If I use the SFSE launcher, separately or from Vortex, I get a spinny thing for a few moments, then nothing. I get that crash "report". If I load the game without using the SFSE launcher, I don't have SFSE. None of the mods it depends upon function. The tilde key does nothing. I've got 2854 mods in Skyrim SE, which includes over 300 that have dlls dependent upon SKSE64. It works flawlessly, every time. I have 678 mods in Fallout 4. F4SE works fine. I used to have SFSE working in late 2023, but when I decided to come back to Starfield and update everything, SFSE no longer loads Starfield. It hooks, then the game crashes before even visibly loading. SFSE.txt lists all the plugins as having loaded successfully. I verified the installation on Steam. I think something in the Starfield exe is broken, at least for me. That memory error is so vague that I have no idea what it is referencing. Good God. I still had an old dll from an older version of SFSE. I deleted that, and now it works. My apologies for bitching.
Guys, on your website you still have build 0215 as the most current one. I downloaded the 7z archive from there and was astounded when the script extender said I'm on the wrong version.
Had to come to the Nexus to get the right version.
6632 comments
Status updates:
2024-10-19: I have purchased a code signing certificate in order to hopefully reduce virus scanner false positives. This largely seems to be a racket where you pay them $657 every three years, and then virus scanners are happier with your products, but that's the world we live in. Thanks to Magicockerel for generously donating to cover part of the cost (unprompted!). Please let me know if this breaks anything or you still get virus scanner issues.
2024-10-20: An update is out (0.2.15) that should fix issues with signing verification on different operating system versions.
2024-11-19: Bethesda has moved the beta runtime to release (1.14.74). SFSE has been updated for this version.
Older updates:
2024-06-09: Game update 1.12.30 has been released, and is being analyzed. This takes many hours and may not finish until late tonight. To be clear: I will probably need to sleep before the whole thing finishes.
2024-06-10: An update is available adding compatibility with 1.12.30.
2024-06-14: Game update 1.12.32 has been released, and is being analyzed. SFSE has been updated for this version.
2024-07-03: Game update 1.12.36 and an update for SFSE has been released. Imagine releasing a patch before a holiday weekend.
2024-08-20: Game update 1.13.61 has been released very late in the day, and is being analyzed. There is a very good chance that I will need to sleep before the automated steps finish.
2024-08-21: The automated part of the analysis completed, but took a very long time due to changes in the large game executable (made worse by the release time of the patch). An update for SFSE has been released.
2024-08-23: Some new preliminary serialization code appears to be causing problems. Sorry for any trouble. Please download version 0.2.12 to resolve the issues.
2024-09-30: A game update has been released that requires an update to SFSE. 1.14.70 is currently being analyzed. Bethesda has made a major change to the base form type in 1.14.70, so all gameplay plugins will need to be recompiled. Expect some plugin developers to have not marked up their compatibility data correctly and for some plugins to crash. An update for SFSE has been released.
Crashing on startup? Remove everything from Data/SFSE/Plugins.
Empty halted loader window? Remove VCRUNTIME140_1.dll from the game folder, and don't install BetterConsole that way.
Interact key (E) not working? Check your UI mods.
We are getting frequent reports via the "Report Abuse" button that this mod contains malware/viruses/other malicious files. I would like to reassure any users seeing these messages that it is a false positive and that you should add an exception for SFSE to your virus scanner. You should also report this false positive to your virus scan provider so they can correct their detection.
All files shared on Nexus Mods are scanned for viruses before being made available and you can see the "Virus Scan" result just below the image at the top of the page. The Virus Total report can be viewed by clicking the green checkmark in the Files tab, here's an example of the scan result for 0.1.3.
Please do not file reports stating this mod contains a virus as it has been fully verified by our team at Nexus Mods.
Thanks!
When transfering from Vortex to MO2, I spent over a week trying to figure out why the .silverlock version wouldn't load, going so far as to reinstall my game and modlist, one mod at a time. Even went to the official github, and combed through its reported bugs. Come to find out... mismatched versions between sites. Dunno which is the "official" version, now.
If you are still having problems after that, paste the contents of Documents\My Games\Starfield\SFSE\Logs\sfse_loader.txt here inside spoiler tags.
SFSE loader: initialize (version = 0.2.15 01010010 2025-04-17 12:39:25, os = 6.2 (9200))
config path = C:\GAMES\Starfield\Data\SFSE\sfse.ini
procPath = C:\GAMES\Starfield\Starfield.exe
launching: Starfield.exe (C:\GAMES\Starfield\Starfield.exe)
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 0001000E
dwFileVersionLS = 004A0000
dwProductVersionMS = 0001000E
dwProductVersionLS = 004A0000
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
productVersionStr = 1.14.74.0
version = 0001000E004A0000
product name = Starfield
steam exe
dll = C:\GAMES\Starfield\sfse_1_14_74.dll
WinVerifyTrust: 800B010A 800B010A C:\GAMES\Starfield\sfse_loader.exe
WinVerifyTrust failed: 800B010A 800B010A
exe failed validation
SFSE DLL version
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 00000000
dwFileVersionLS = 00020010
dwProductVersionMS = 00000000
dwProductVersionLS = 00020010
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
productName = SFSE
productVersion = 0, 0, 2, 16
Bad SFSE DLL (C:\GAMES\Starfield\sfse_1_14_74.dll).
Do not rename files; it will not magically make anything work.
010E04A0 010E04A0
Again, the certificate database on your computer is out of date or broken, or you've done something to break signature verification. This is what "WinVerifyTrust failed: 800B010A 800B010A" means.
I haven't played Starfield in about a year. But I'm currently in the middle of a save that I never finished and don't really want to update the game so that my existing mods don't break.
Can the latest version of SFSE work on an older version of the game? (mine is before the Shattered Star update)
If Starfield.exe is not there then somehow it got deleted or you did not install the SFSE to the right directory and you will get the error message. I once installed the SFSE to Skyrim SE directory by mistake and it took me a while to figure out what had happened. Ugh - Yeah that one was on me. The Starfield.exe should have the Starfield icon beside the name and the type should be application. If you have Windows Explorer show extensions the .exe will show on it. If you do not have this at all then Starfield won't even launch and you need to have Steam verify the game files and it will add the Starfield.exe.
edit: locked because OP comment is totally incorrect and Frazzlesnap's issue is solved
No use of SFSE - I can load any save I got, ignoring the mods save uses.
But if SFSE loader was used - even clear game (without active mods) can't be load and crashing (with GPU driver + Steam crash as well o_O)
Starfield v1.14.74
trainwreck v1.1.0
Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x000000000000
SYSTEM SPECS:
OS: Windows 10 Pro 23H2 22631.5039
CPU: AuthenticAMD AMD Ryzen Threadripper PRO 3955WX 16-Cores
The game launches normally through Steam, but I don't have any sfse, of course. I hate Starfield. I hate Bugthesda.
I've got 2854 mods in Skyrim SE, which includes over 300 that have dlls dependent upon SKSE64. It works flawlessly, every time. I have 678 mods in Fallout 4. F4SE works fine. I used to have SFSE working in late 2023, but when I decided to come back to Starfield and update everything, SFSE no longer loads Starfield. It hooks, then the game crashes before even visibly loading. SFSE.txt lists all the plugins as having loaded successfully. I verified the installation on Steam. I think something in the Starfield exe is broken, at least for me. That memory error is so vague that I have no idea what it is referencing.
Good God. I still had an old dll from an older version of SFSE. I deleted that, and now it works. My apologies for bitching.
Had to come to the Nexus to get the right version.