Sims 3 launcher does not run since being updated a couple of days ago.

silvabrumby​  Origin is dead, which is why you can't submit an error report.  How are you still using it at all?  I guess that doesn't matter except for the question of what kind of install this is, and it sounds like it's an Origin/1.69 install.

Sims 3 was last updated in January, unless there was some update I didn't hear anything about in the last couple days.  So I'm not sure how you're seeing a more recent update, unless you managed to avoid installing January's update until just now.

At any rate, try uninstalling and reinstalling the 2005 VC++ runtime, which Sims 3 uses and which other Windows 7 players had to reinstall after the update.  Here's how:

[Current Issue] Sims 3 doesn't open, Windows 7 | EA Forums - 8323489

For the Windows 10 computer, if it has a newer, high-end Intel processor, that could explain why the game never worked.  But that's exactly what January's update fixed, for EA App installs at least, so it's worth reinstalling the game now to test.  If it doesn't work, and you'd like to troubleshoot further, I'd be happy to try to help.

Amazingly enough that little Origin Box just popped up & I figured EA must have sent it. I logged on, having previously said I was having problems & there it was, the Origin Error Reporter added to my programs in the Start menu.  It's true that the game was originally loaded when when the host was Origin. It's been EA for a while now & it was fine. Maybe I haven't played it since Jan. I've been amusing myself with Sims 2. I'll try it on the Win 10 machine - but I always thought it a **bleep** machine. I couldn't get Outlook to work - & there was the crazy thing where games were unrunnable because they were endlessly loading bits from One Drive. 

And it's slow!

I probably haven't used that computer since Jan either. I like getting my E-mails & things you see! Still I'll give it a try & let you know! 

Well yes, I'm a quaint old fashioned person. But this Win 7 machine is fairly well configured. 

replaying the 2005 VC runtime did fix the problem. Thanks for that. I haven't tried the Win 10 machine again.