Thanks Chain. I haven't switched to Steam. That was more of a nightmare than Origin, for me anyway. I'm easily confused and that really confused me. All my mods are on the 1.67 Patch so I'll check out the 1.69 version.

I just switched out the ET mod for the updated one for 1.69 and I'm still getting the message.

Do you have any other core mods? Are you sure you're on 1.69? What does the launcher say the patch level is?

The launcher says I'm on 1.69. Not sure which ones are core mods. I have most of the NRaas Mods and then I have these ones - just scroll through them http://s1361.photobucket.com/user/besti ... sort=2&o=1

We can't "scroll through" a static screenshot, at least not the one I am seeing in that upload link. There are only five Core Mods for TS3; these are the ones that will kick up the version mismatch error:
NRaas ErrorTrap
NRaas UntranslatedKey (this is really for developers)
CMarNYC's XCAS
Consort's 2X Weight/Fitness
AwesomeMod

If you have the 1.69 version of ErrorTrap and none of the others, and you are getting a core mod version mismatch error but only with ErrorTrap 1.69, then you likely have a broken installation with remnants of Steam or your older 1.67 install still in place somewhere. The mismatch itself in this case is harmless (it would be different if you were trying to use a 1.63 or prior version of a Core Mod). Whether what is broken about the install, if anything, affects anything else is actually difficult to determine.

I'm suspecting one or more Registry entries that weren't cleaned up thoroughly after one of the 1.67 uninstalls as SSG said. Did you use Piriform's CC Cleaner or, if you haven't gotten around to my more recent suggestion, will you be doing so, after the uninstall to remove all traces of TS3? May as well uninstall and take Origin out as well.

If all else fails, this is kind of drastic but you could uninstall (include Origin in this), clean Registry, create a new Windows user login, and try installing by being logged in as that new user. But that's not as drastic as the next possibility, which would be reformatting (erasing) your hard drive completely and doing a fresh install of Windows 7, if you have a way to do that.

Ok, I think I may have one or two of those mods, I'll take a look. After reading your post igazor, I think I may know what's wrong here. After reinstalling my game, one of the problems that popped up was a blank welcome screen in the launcher. I have been calling EA on various problems and to ask if there was a way to go back to patch 1.67. They sent me a link and told me to install this patch 1.67 from 1.66 but after attempting to do so, I wouldn't work. So I may have some residue of botched patching and some steam files somewhere. I did use CCleaner but may have not used it recently. So, later today I plan to uninstall everything and start again, using CCleaner as I go. Probably won't have any results until late tonight but will let you all know. EA did suggest crating an new Admin account on my system, so I'll throw that in as well.

In the meantime, I'm hunting for some sims 3 discs to end this nightmare.

Did you pick up one of those Pre-2012 Base Game discs I linked to much earlier

@sittingbear... sorry, I forgot about that. Will check that out later today, thanks

@igazor.... well, one problem solved, I remove the NRaas UntranslatedKey and the game starts without that notice. I have no idea why I had that mod in there, I don't even know what it does LOL.

Yep, this sound pretty likely. That's why we keep telling players not to try to patch or SuperPatch 1.67 on top of a 1.69 installation. You are not alone, many have not listened to us and tried to do that anyway. It may have worked at one time, before Jan 2016, in fact there was a trick about uninstalling and reinstalling the base game only that used to make one of these work, but now doing that just seems to break everything.

After reinstalling my game, one of the problems that popped up was a blank welcome screen in the launcher. I have been calling EA on various problems and to ask if there was a way to go back to patch 1.67. They sent me a link and told me to install this patch 1.67 from 1.66 but after attempting to do so, I wouldn't work. So I may have some residue of botched patching and some steam files somewhere.