Community ManagerHey @sharonguidry this is most likely a permissions issue.
Can you run Origin by right-clicking on the launcher and select Run as Administrator to see if that helps.
If not, can you create a new Windows admin account and try the game there.
Darko
It didnt work
@sharonguidry , what expansion packs do you have for Sims 2? There is a certain order to install the packs in. Let me know what you have before you take any further steps. 🙂
@Tremayne4260 I don't think the installation order is a problem here, installers for Sims 2 FreeTime and later packs (including Apartment Life) have issues with permissions on Windows 10. I don't think the order matters as long as the packs are patched properly after installing. I think that was only a Sims 1 thing.
@sharonguidry As for your issue with Apartment Life, here's how you can install it.
1. Open Command Prompt (as Administrator).
2. When Command Prompt opens, it should say C:\WINDOWS\system32>. Type in the drive name for the drive your disk is in (for example, D:, E:, or whatever else it is). That should switch it to use the specified drive. After you press Enter, it should say [drive letter]:> in the next line (for example D:>, E:> or whatever).
3. Type in AutoRun.exe, press Enter, and the installer should open. After that, you can close the Command Prompt.
@mate54, actually it does. If you read one of the earlier posts in this forum it does state that installation order does matter due to the age of the game. In Sims 3 and 4, it doesn’t matter. But in Sims 2 it does.
For example, if you had everything but say Free Time installed and later got Free Time and installed it, the game would only recognize Free Time, but not Apartment Life or Mansion and Garden.
@Tremayne4260 From what I've been able to test, it works either way and all packs work properly. The issues with patches and permissions will happen regardless of the installation order. Maybe it was different for other players, but I found no reason to believe that the installation order matters any more than it mattered on older versions of Windows, as long as the packs are patched when installed. But that's probably a discussion for another time.
Hopefully the OP can sort out the Administrator error using Command Prompt, I wonder why that error even happens (and only with packs released in 2008).
