SMM Update v3.0.3 Updates then Updates again on restart
SMM Update v3.0.3 Updates then Updates again on restart, re downloads the update, then when i re open the mod manager it hangs to the point that i need to restart the manager again then force close the service in services.
Solution:Jump to solution
Uninstall SMM, delete the
Programs\Satisfactory Mod Manager dir, then install it again, and everything will be back to normal54 Replies
-# Responding to
Key Details for SMMDebug-2024-10-21-20-18-15.zip triggered by @ThomasTwoFaceIts just done it again
You might have 2 SMMs installed, because the log shows that SMM 3.0.3 opens, then 3.0.0, then 3.0.3 and so on
Its constantly updating
After it updates and restarts, does it say SMM 3.0.3 in the top bar or 3.0.0?
-# Responding to
Key Details for SMMDebug-2024-10-21-20-23-54.zip triggered by @ThomasTwoFace
V3.0.0
This is after the update, when i close it then re open the SMM it auto updates again
I can record it if that helps
So you're launching a different SMM than the installed one
No same one
It's clearly not the same one if when it updates it says 3.0.3
I only have the one installed
It can't magically roll itself back to 3.0.0
Clearly it is
With the 3.0.3 open, check the exe properties in task manager
Then check the target of the shortcut you're using
Rightclick -> Properties -> Location
"C:\Users\Thomas\AppData\Local\Programs\Satisfactory Mod Manager\Satisfactory Mod Manager.exe"
"C:\Users\Thomas\AppData\Local\Programs\Satisfactory Mod Manager\Satisfactory Mod Manager\Satisfactory Mod Manager.exe"
This has only been since the update
As per this screenshot, i only have the one instance installed
Which is the latest one 3.0.3
Which one is the updated one?
The updated one? v3.0.3
This is from the folder where its installed in
The updated one s 21/10/2024
The date modified of that folder is 15/10, so the folder wasn't created in this update
So the last update, 3.0.2
I just checked now on the releases of SMM
15th was 3.0.1
Which was not updating properly because of the ghost process
So maybe somehow for you it didn't fail to update because it created a new folder
No? I did the update as the discord said there was one, started SMM and the update downloaded as in the screenshots
But that could have only happened if the installer couldn't actually find the existing install
Which would make sense given the missing uninstall.exe
I can send over the files in a zip file if that helps
I'm having a weirdly similar issue. I open SMM, it closes, then reopens. The SMM exe in C:\Users-\AppData\Local\Programs\Satisfactory Mod Manager shows version 3.0.0, but the exe inside C:\Users-\AppData\Local\Programs\Satisfactory Mod Manager\Satisfactory Mod Manager shows 3.0.3
So its not just a me issue
Is the modified date for the nested folder also 15th?
I just uinstalled and reinstalled a moment ago. And the issue replicates.
Oh, when 3.0.1 was released and had issues, did you uninstall SMM and then reinstall it?
Or, in general, did you uninstall SMM while it had ghost processes?
I did, yeah. So I'm guessing there's a hang up somewhere?
I uninstalled SMM , then installed it fresh as i was having issues
That i reported
Yeah, before 3.0.2 the uninstaller didn't error if the process was still running
So it failed to remove the file
And then when installing it again, it found that the folder was not empty, so it created a subdir for safety
I'm assuming the resolution is delete the out of date version, and move the exe out of the subdir.
Solution
Uninstall SMM, delete the
Programs\Satisfactory Mod Manager dir, then install it again, and everything will be back to normalId suggest raising this with the team that handles the SMM
Just as a heads up
I am the team that handles SMM
That there might be an issue
You're literally talking to them lol
I am the senate moment
Thanks for the help! I think I'm all set now.
I deleted the other .exe file in the folder, launched normally and everythig is running normally now
Dont close the thread just in case you need the screenshots / debug reports
None will close it but mark the question as resolved