skse64 is UPDATED

[Chef]

As of 17 Sept 2022 skse64 is up to date for SSE.


SSE
skse64 ver 2.2.0
Game ver 1.6.629

ATTENTION RE Game Pass version of SSE: From what I have been reading, it will not be possible to use skse64 with the Game Pass version of the game. As a side note other things like xEdit, MO2, ENB, and possibly Vortex, and a bunch of other tools will not work with the Game Pass version.

https://skse.silverlock.org/

https://steamcommunity.com/sharedfiles/filedetails/?id=1197413219


The following only pertains if the title of the thread is "skse64 is OUTDATED": There was an update to the SSE exe today. That means that skse64 will not work.

Just to be clear. The version check in skse64 is there for a reason. Basically, anytime they change the exe version the address's that skse64 hooks into change. If the version check were not there any save made after the exe update would be corrupt. Period.

There are ways to avoid updates in this thread:
https://steamcommunity.com/app/377160/discussions/0/364039785169337238/

Video by Gamerpoets regarding this subject:
https://www.youtube.com/watch?v=3gAiLABNoIA&t=1s

The Script Extender team is usually on top of things. The time it takes to update relies on many things. One of the biggest is how much the exe actually changes. Also, please be aware that these folks work on this in their spare time, and for free, so please be understanding.

Please be aware that there is a good chance that mods that rely on skse64 may not function.

I will update this thread when things change.

[Arrowspieler]

Thanks so much for replying! I actually did a system restore to yesterday a.m., went to Steam, game properties and selected do not update unless the game is opened from Steam, and now I can start my game at the same point where it was. There was a message that popped up that AE is available so I did not opt for that because there is a Silverlock.org message that my SSE version is for a newer game than my SKSE64 supports, so I know that Steam pushed out AE before SKSE64 was updated to work with it. I do see a newer (AE) version of SKSE64 on the Silverlock site, but until I hear how well it works, don't want to take a chance and download it or the AE of Skyrim. Thanks again for your thoughts.

[Chef]

You can go into your Skyrim Special Edition folder in the Steam directory, right click on SkyrimSE.exe and go to the Properties tab. Look at the "Product Version" number. If its 1.6.318.0 that is the new version. If its 1.5.97 that is the pre update version.

[taochaitsung]

I keep doing a system reset to reverse the update and the sneaky bastards keep forcing it. I don't know how to disable updates.

[Meowster78]

taochaitsung님이 먼저 게시:

I keep doing a system reset to reverse the update and the sneaky bastards keep forcing it. I don't know how to disable updates.

Found this post that shows a way to trick steam into thinking Skyrim is updated:
https://steamcommunity.com/sharedfiles/filedetails/?id=1916008329

Go to your game's installation area, look for the game's folder and go to the steamapps folder, open the file titled "appmanifest_489830" and paste the numbers to the corresponding line:

For buildid: "7694678"

For manifest 489831: "1985552842565684891"

For manifest 489832: "5260954425794414274"

For manifest 489833: "6964426252826681862"

This'll work until they do another update in which case gotta look for the id's again on Steam DB. https://steamdb.info/app/489830/history/

[taochaitsung]

Meowster78님이 먼저 게시:

Found this post that shows a way to trick steam into thinking Skyrim is updated:
https://steamcommunity.com/sharedfiles/filedetails/?id=1916008329

Go to your game's installation area, look for the game's folder and go to the steamapps folder, open the file titled "appmanifest_489830" and paste the numbers to the corresponding line:

For buildid: "7694678"

For manifest 489831: "1985552842565684891"

For manifest 489832: "5260954425794414274"

For manifest 489833: "6964426252826681862"

This'll work until they do another update in which case gotta look for the id's again on Steam DB. https://steamdb.info/app/489830/history/

To be done in notepad, correct?

[Meowster78]

taochaitsung님이 먼저 게시:

Meowster78님이 먼저 게시:

Found this post that shows a way to trick steam into thinking Skyrim is updated:
https://steamcommunity.com/sharedfiles/filedetails/?id=1916008329

Go to your game's installation area, look for the game's folder and go to the steamapps folder, open the file titled "appmanifest_489830" and paste the numbers to the corresponding line:

For buildid: "7694678"

For manifest 489831: "1985552842565684891"

For manifest 489832: "5260954425794414274"

For manifest 489833: "6964426252826681862"

This'll work until they do another update in which case gotta look for the id's again on Steam DB. https://steamdb.info/app/489830/history/

To be done in notepad, correct?

Yep, I did it on notepad++

[taochaitsung]

Meowster78님이 먼저 게시:

Yep, I did it on notepad++

Interesting, since that's what the file read already.

[HazakTheMad]

In case any of you need it, my roll back guide,
https://steamcommunity.com/sharedfiles/filedetails/?id=2641648930

[taochaitsung]

HazakTheMad님이 먼저 게시:

In case any of you need it, my roll back guide,
https://steamcommunity.com/sharedfiles/filedetails/?id=2641648930

Not familiar with all the processes needed in the youtube video guide. Should I just be able to do it with the NMM mod you have up?

[taochaitsung]

HazakTheMad님이 먼저 게시:

In case any of you need it, my roll back guide,
https://steamcommunity.com/sharedfiles/filedetails/?id=2641648930

Okay, just checking in to let you know the NMM mod worked. I copied the original exe file just to be on the safe side [extr 35Mb taking up space] but it's all running smoothly.

Thanks for this and jumping in to let me know. Hate when Bethseda jacks with my game.

[Squall Leonhart]

its now at 2.1.2

[Bad Distraction Carnifex]

❄️TehSpoopyXmasKitteh🎄님이 먼저 게시:

Can we also please avoid reviewbombing Skyrim SE over these updates? It’s not their responsibility to keep an external mod script extender up to date. I’ve had to report two rants already, and I don’t want to report any more.

I recommend keeping the rant to the forums rather than writing a negative review that does nothing but rant about how broken a mod is.

With how badly this was handled; the review bomb is absolutely deserved. Bethesda chose the absolute most intrusive way to implement AE. They knew it would be bad and they knew there were better ways of handling everything but the compiler issue.

I'd give a negative review to AE itself but because Bethesda released AE as an update; now they get a bad review on SE.

[HazakTheMad]

And the review bombing will not change or effect anything.

[Arrowspieler]

In case it helps anyone, even after changing settings to not update on Steam, it was somehow pushing something out so that every single day, sometimes more than once in a day, I was having to do a system restore. I resolved the problem by updating the Skyrim AE version of SKSE64 even though I am running Skyrim SE and I have not had any issues at all since then.

[Vlad 254]

Arrowspieler님이 먼저 게시:

In case it helps anyone, even after changing settings to not update on Steam, it was somehow pushing something out so that every single day, sometimes more than once in a day, I was having to do a system restore. I resolved the problem by updating the Skyrim AE version of SKSE64 even though I am running Skyrim SE and I have not had any issues at all since then.

You missed a step somewhere. No updates on my end at all and I've been playing each day since since the Bethesda Update.