The Sims Medieval problems on Windows 11
Stress. I've owned my new gaming laptop for almost 2 days and all I have is stress. I finally upgraded laptops, my old one had lasted 6 years, and it was time to retire her while I could. And I bought one from that fancy smamcy company. And it came with windows 11.
I downloaded origin and the Sims games I felt like playing. Including medieval. And only medieval won't work. 2 days of support and now it's being escalated, and I was told to make a thread.
Here are the particulars:
- I had an error message at first bc I didn't have direct x. Once downloaded we realized I needed the 32bit version and got that too, no dice.
- No more error message after getting this
- Already got the .NET framework downloaded for Sims 3
- Compatability mode doesn't work
- Microsoft checked all my drivers etc remotely and I'd had everything already
- Fixing the .vc folder doesn't work
- It just opens origin if you click the shortcut. If you click from origin, you get an hourglass ⌛️ by the cursor and then it clears and that's it.
Think that's everything.
Hey friend!,
Good news. I figured it out. And it was all thanks to you for raising your issue, thanks to dear @mate54 for linking the TS3 solution and thanks to person sharing the fix of course. I am sharing the solution right away with instructions.
So the code we will be using is:
echo "Launch The Sims Medieval..." do{ $TSM = Get-Process TSM, SimsMedievalLauncher -ErrorAction SilentlyContinue }until($TSM) $Affinity=$TSM.ProcessorAffinity $TSM.ProcessorAffinity=1 Start-Sleep -s 5 $TSM.ProcessorAffinity=$AffinityInstructions:
0 - Open origin, get ready to click on "Play" button for your The Sims Medieval. Now minimize your Origin. We will use it later.
1 - Open your Windows' Notepad application. Regular notepad, nothing fancy. Copy and paste the code. In your notepad window, click on File from menu and select "Save As". When new window pops up for you to save the file, select "All Files" as Save As Type. Also give a name to your file (any name, just pick one). At the end of the name you have given to your file, add ".ps1"
(Adding the ".ps1" extension at the end of your file name, makes it a powershell file)
2 - Save your newly created powershell file to your game directory (wherever the TSM.exe is located). Mine was in C:\Program Files (x86)\Origin Games\The Sims Medieval\Game\Bin
3 - Make sure compatability setting and run as administrator is off for your original TSM.exe file (since you mentioned that you tried those)
4 - Right click on your .ps1 (powershell) file which is now located in your game folder. Select "Run with Powershell". Now a powershell window will pop up and nothing will happen
5 - Open your Origin app window and click on "Play" button for your The Sims Medieval. It's play time!
Whenever you want to open your The Sims Medieval again, you just need to do the steps 0, 4 and 5.
SOLUTION UPDATE : Omg. I didn't even realize that Origin is no longer with us. When did that happen? Anyways. So my powershell file also didn't work and game didn't open.
That's why I searched: can't run ps1 file with powershell.
Then I learned that windows changed a powershell security setting to block you from running your own scripts. Aha! I found the solution and voila! my beloved Sims Medieval is working again. Here is the solution: (Yes, not for Origin but for the "EA App")
Go to your start menu on Windows. Type "Powershell". When it appears, right click on it and say "Run as administrator" After your powershell window opens, type: set-executionpolicy remotesigned after you do that, windows will ask you if you are ok or not since this is a security setting. You should type the letter Y at this point and hit your "Enter" button. Then the powershell will be working again. You can use my solution I provided in my original response and go into your game. (I did it)
Again, for my solution to work you need to be using gen12 intel CPU for some reason. Again, remember to keep your powershell window open in the background while you are clicking on "Play" button. As it seems, problem wasn't with the EA App but rather with Windows Powershell Security updates.
Defeat an evil wizard for me @LBonne24 !
