SMM installed drive died, can't change location.

I removed the %AppData for satisfactory and SMM and reinstalled Satisfactory. Still the .exe remembers last install location and won't continue past the point of pictured error. Any help? Thanks all.
No description
Solution:
This issue can also occur due to an old SMM install in a location that no longer exists. When this happens, any new SMM install attempts will attempt to update that install. To solve this, you will have to clear the SMM install registry keys. Just to be sure, check both the SMM2 and SMM3 registry keys, but note that some may already not exist. SMM2 registry keys: * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\05aa181a-e2c4-5231-ae02-02af49144086 * HKEY_CURRENT_USER\Software\05aa181a-e2c4-5231-ae02-02af49144086...
Jump to solution
1 Reply
Solution
FICSIT-Fred
FICSIT-Fred2mo ago
This issue can also occur due to an old SMM install in a location that no longer exists. When this happens, any new SMM install attempts will attempt to update that install. To solve this, you will have to clear the SMM install registry keys. Just to be sure, check both the SMM2 and SMM3 registry keys, but note that some may already not exist. SMM2 registry keys: * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\05aa181a-e2c4-5231-ae02-02af49144086 * HKEY_CURRENT_USER\Software\05aa181a-e2c4-5231-ae02-02af49144086 * HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\05aa181a-e2c4-5231-ae02-02af49144086 * HKEY_LOCAL_MACHINE\Software\05aa181a-e2c4-5231-ae02-02af49144086 SMM3 registry keys: * HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Satisfactory Mod Manager * HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Satisfactory Mod Manager (current user) * HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Satisfactory Mod Manager * HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Satisfactory Mod Manager (current user) -# Responding to smm3badregistry triggered by @Dreadsome

Did you find this page helpful?