Launcher not recognizing Game installed on drive letter: Z

[Kira-sr]

Problem: Launcher says that the executable is not located on Bin folder when it is.

Path:

Z:\SteamLibrary\steamapps\common\The Sims 3\Game\Bin

Game Version:
Steam (v1.67.2)

Things i did:
Clean Install x2
Admin privileges

Note: it is imperative that the game is installed on this driver since it is the only one i got memory remaining.

[marcos4503]

Hi, I apologize for the delay in reply. I'm sorry you're experiencing the issue you reported. The Launcher should work without any problem on any Drive other than "C". I myself use my game on a Drive other than "C".

The path you mentioned above is the expected by the Launcher. If you extracted the Launcher files from the downloaded ZIP and placed them in the path written above, then you are 100% fine.

That said, I need you to perform the following check...

• Verify if the following files are in the path "Z:\SteamLibrary\steamapps\common\The Sims 3\Game\Bin".
  • "TS3.exe"
  • "TS3W.exe"
  • "Sims3Launcher.exe"
  • "Sims3Launcher-backup.exe" (the original EA "Sims3Launcher.exe", but renamed to this)
  • "Sims3LauncherW.exe"
  • "S3Launcher.exe"

If any of the files listed above are not present, this is likely the cause of the problem.

[Kira-sr]

yeah, it was one of the files you mentioned missing. thanks for clarifying everything, now it opens correctly.
sorry for the mixup from my part :)

[marcos4503]

No problem. I'm glad it worked! Would you mind telling me which file was missing?

Just so I know if there's anything I can do on the Launcher side to get around this issue in the future. :)

[Kira-sr]

TS3, and Sims3Launcher.exe (i had renamed it as Sims3Launcher-old.exe to make the original launcher go away before a clean reinstall. it seems steam saves these names and folder structure once you reinstall the game again. so it might be good to keep an eye on folder structure before an install, given it happens what is happening).

problem i'm having now is that the App opens but is now crashing after i made it work for the first time, for some unknown reason... it is returning this error here... (i did a fresh reinstall again of the game, and cloning the folder you provided on the repo. no idea why it is pointing to a kernel DLL in system32 tho...)

also here are the Bin folder structure . this time it has all the files we suspected were missing:

[marcos4503]

Got it! In fact, Steam sometimes keeps some of the game's files installed, even after uninstallation. I don't know why, so I recommend that after uninstalling the game through Steam, go to its folder on your Disk and delete it manually. :)

This error is quite bizarre, I've never seen anything like it before... Unfortunately I can't say exactly what it could be. But do you have all the necessary dependencies installed?

Do you think there's a chance that your Windows system has some corruption in some file?

Also, is your system x64?

[Kira-sr]

yep. x64 WIN10 pro. (22h2)

and yep. all the necessary dependencies are installed. checked twice before going trough the procedure.

i too have zero idea what could this be. if it was really something trough the kernel, i don't think the PC would even boot. i'll run again the diagnostic tool for that DLL. but for what i did, it is just in this program that it is panicking.

(i also checked if Fault Tolerant Heap (FTH) could be on for this, but nothing... the program was not on the list.)

[marcos4503]

Got it.

This error is very strange... The most information I could find so far on the Internet was this GitHub thread, about a similar problem with a WPF program (which is the same technology I used in the Dream Launcher).

dotnet/wpf#7992

In this thread, they mention using the Windows Event Viewer to check if there is a more detailed log of the problem. The Event Viewer can be opened by using "Win + R" and typing "eventvwr".

In the case of the thread's author, analyzing the error log found in the Event Viewer indicated that the most likely cause of the problem was an incorrect .NET Runtime installed on the PC, or the PC's architecture differing from the architecture supported by the author's build.