Initialization Error At Startup Sims 4
Jenelle Centeno
Before I updated my game, I was getting a "missing mscvp120.dll" error whenever I tried launching my game. However since yesterday's update, it now launches a black screen before closing out with a "Unable to start: Initialization error at startup [135dec40:3fbbeccd0:00000064:00000000]" message popping up. I've tried re-installing Origin and running CCleaner with no luck (re-installing the whole game will be my last resort). Is there anything else that can solve this?
Some of them you may already have done, but there are others mentioned. And please do try completely disabling your antivirus, if you use something other than Windows Defender, at least long enough to test. It's sometimes not sufficient to set exceptions for Origin and the game.
If that doesn't help either, please try playing while your computer is completely offline. You can sign into Origin and put it in offline mode, then disable wifi and/or disconnect the ethernet cable before trying to launch the game.
I reinstalled and updated windows 10 to version 1709, Installed origin then installed sims 4, error popped up every time. Sometimes it would say Sims 4 already running. turned out to be windows defender. I didn't have a antivirus installed and was just using Windows Defender.
I've actually added the app to my firewall allowance. I've also gone on and added all of Origin wherever I can find an .exe file. And still I have this issue. I've uninstalled and reinstalled Origin countless times, The Sims4 twice and still... same agonizing error message. It seems obscene that people should have to turn off their virus protection to get a game to work. Any other ideas from your end?
When launching from Origin I received this at splash screen: Unable to start: The game has run out of memory 2234...
When launching from Sims 4 shortcut I received this before game loads: Unable to start: Initialization error at start up. 135dec...
Forfeiting my saved game/family, these are the steps I've taken after above troubleshooting:
@jessiepie The initialization/135dec... errors are usually related to the game lacking the proper permissions. Windows 10's Controlled Folder Access is the most likely culprit. You mentioned allowing the game through your antivirus/firewall, but if you didn't specifically adjust the Controlled Folder Access settings, that's the first thing to try.
Other reasons for this error include problems with Origin. The Origin update tool is also throwing errors, although I can't tell from your dxdiag whether that was before or after you uninstalled it. If you want to be thorough, clear Origin's cache, uninstall it "the hard way," and reinstall it to D, again unless you've done it already.
It can also help to run Origin and TS4 as an admin (right-click on the .exes or shortcuts and select "Run as administrator"), and to disable Origin in-game: open Origin, hover over your username, select Application Settings, then More > Origin in-game. You might also need to disable it on Sims 4 specifically: right-click on the TS4 icon, select Game Properties, and uncheck the box.
If none of this helps, there might be an issue with your GPU driver. The TS4 errors listed are probably related, although maybe you've updated the driver since then. Otherwise, there's a slightly newer one available for the 1070.
@jessiepie From your OP, I wasn't sure whether you'd allowed the game though Controlled Folder Access, or just a third-party antivirus/firewall (and whether you'd used TS4_x64 specifically); how you'd uninstalled Origin, and what drive it was installed on now; and whether you were still launching Origin and TS4 as an admin while testing other potential fixes.
The GPU driver is my mistake: I saw that yours was dated and installed in January, and that Nvidia posted the newest one in February, so I didn't check the version number. Still, your dxdiag does list a few likely-GPU-driver-related errors, although it's impossible to tell whether they're from before or after you updated.
A better way to find the most current errors is through the Reliability Monitor. Hit Windows key-R and enter "perfmon /rel" without quotes, then check the entries for the time you've been troubleshooting. The timestamps aren't always completely accurate, so you might have click "View technical details" to get an exact time. Maybe that will give you a better idea of what's causing the current errors. You can copy and paste the info for all the relevant entries into a .txt document and attach it here. If I don't see anything obvious, there are other people around who can take a look.
I've attached 1 of 3 errors I received at 11 am this morning from running the monitor you provided. Because of attachment restraints, I've only added one. Errors and cause are the same, numbers are different. Oddly enough, that is the only errors I have for Sims 4 besides the error I received trying to launch Dungeon Keeper from Origin, but I believe that's a separate issue.(Old game.)
It asks me to check the security and maintenance control panel. And that may have before I disabled Windows Defender. No errors are listed after as such. BUT, since then I have and uninstalled and reinstalled both Origin and Sims 4.
Gee, I guess I have to lean on you guys for some help here. Yesterday I was ading a couple A/C to FS9 and have run into an error called "Aircraft initialization failure." This is a pretty serious error because now FS9 will not start up. Anyone who has a method for troubleshooting this issue would be very welcome!
There is a tool (freeware) here that manages add-ons to Microsoft Flight Simulator. Using this "easy to" Wizard - FSM (FlightSim Manager) can install aircraft, panels, textures and scenery directly from distribution ZIP files you may have downloaded. Also includes an option for proper uninstallation of add-ons.
In addition there is an easy to use Aircraft Editor to add or remove aircraft variants and a comprehensive hangar management option allows you to manage and configure your add-ons for live FS installation.
If anyone is experiencing or unfortunately happens to to incur the 'Aircraft Initialization Failure' error going forward, I have found a solution to it. The cause of this failure remains quite frankly undetermined but having said that there is a simple fix.
If you get this error, it will be necessary to go to the Tool Bar and then to 'documents' and delete 'Flight Simulator Files.' This is where the temp. saved flights are stored and where details of the last flight are stored. Even though 'saved flights' seems to have nothing to do with installation or initialization error, it is still necessary to delete these files. -This action will execute the removal of corrupt files which are the causation.
I have sought and found one more solution to this issue for whomever seeks it. If you should receive the error: 'Aircraft Initialization Failure' the following will provide a more comprehensive fix at the actual root of the trouble.
While FS is not running, the way to launch a flight is to recreate the 'Flight File,' and reset that file in the 'SITUATION' line. Also, there is another flag 'SHOW_OPENING_SCREEN' which is to be set to 0 (Zero). (Ordinarily the 'Fly Now' button sets these two items automatically and then auto launches Flight Simulator.) At this point, you will more than likley get a 'CORRUPT FILE' prompt before accessing the main menu but will be able to fly the simulator. What brings about this error is that the FS9.cfg file is still pointing to a 'SITUATION' FILE that doesn't exist and it will complain (error out) before showing you the main screen. To permanently correct this, locate the FS9.cfg file and edit it in 'NOTEPAD' to correct and end the error. Find the following two lines and set the value as written:
Note: If the aircraft specified in the 'SITUATION' line doesn't 'EXIST,' one reason could be because an attempt is/was being made by the user to fly a mal-created and/or incompatible A/C. If this occurs go to Internet Explorer toolbar and select 'MY DOCUMENTS.' Then delete "FLIGHT SIMULATOR FILES.' This will delete the temporary flight files held in the FS cache. Go back into the FS A/C folder, check for and delete any incompatable A/C.
2- NEVER select 'go fly' from the fly window with the aircraft you have been jacking with (installing, modifying etc.) Allways start the sim in another aircraft and then select the aircraft you have installed from the select aircraft list.
3- With the initialization error, All you have to do is: Click the FS9 icon. AS the sim is starting, hold down the keys control+shift until the first screen comes up. This will restore the FS9 .cfg file. Yeah, you will have to reset your personal preferences, but it works. Then go to explorere and either investigate the aircraft problem, or drag it out of there. (Delete).
Just wanted to say THANK YOU GUYS SO MUCH for this fix. I almost started WEEPING after FULLY REINSTALLING flight sim and I started getting this error (an old plane I had downloaded was no longer part of the default installation, obviously - my "startup" file was pointing to this aircraft")
Thanks for the heads up. I have been trying to educate myself by applying tweeks to various aircraft. Have luckly not ran into this problem yet but feel it was probably only a matter of time until I did experiance it.
I have noticed that I sometimes have a hard time getting the changes I made to surface on fs9. It seems to be reading previous settings and ignoring my new changes. By restart the game and switching back and forth I finally get the changes to surface but have not found a consistant method. I think it probably has to do with a violation of your rule 1 and getting lazy with rule 2
Thanks again ?