Securom Launcher Has Stopped Wor
Stephanie Dejoode
( BTW: After I re-installed my game, I was able run the game with GTAIV.exe and if I update my game to patch 1.0.7.0 and launch the game with LaunchGTAIV.exe as an administrator or just normal it gives me the ''SecuROM Launcher has stopped working'' error.
Well after I downloaded the game it goes to update the launcher, it does each part but then the launcher closes itself; I go back on it and it reads as Version 0.0.0.0. Of course I didn't notice this till I went to get my Sims 3 Store content for my game; Any content I try to download will not, I also get no prompts in the download window, but if I try a group download it instead opens a tab that has a bunch of random text in the URL here is an example :
@Craegon If your having a problem with Steam your goimg to have to take that up with Steam because they run their own authentication servers. There could be a couple of problems. I'm guessing you have Windows 10. Open control panel - programs and features - turn windows features on or off - check .net framework 3.5. the launcher needs this and Windows 10 does no turn this on by default.
because even when I got the version number to show (by setting windows 10 compatibility to windows 7) the version it shows is 1.67 but the Origin version is 1.69, and the launcher on the Origin version looks nicer and new
I feel like EA is just forcing me to use Origin, so if it makes you feel better, your CD codes will get you the game and expansions you have on Origin for free and you can add a non steam game to your library, you could even use this to skip the launcher if you want to
Error Reports: IF YOUR GAME CRASHES and Windows has the "Game.exe has stopped working" message appear, DO NOT CANCEL OR CLOSE IT UNTIL IT HAS FINISHED THE PROGRESS BAR. If it does occur, your crash logs may become valuable pieces of information. To retrieve them for us, do the following:
In case you are encountering the SecuLauncher failed to start application [2000] error with GTA IV after you installed it from a traditional media (not via Steam or a different Game launcher), this problem can also occur due to insufficient permissions.
So what did I do next? I went off and started reinstalling all my old programs. Everything worked fine until I installed Nero. At that point, my stopped loading. No errors, no messages, just nothing. So I started doing some research and found out that CoD4 has SecuROM with it. SecuROM has a thing for burning and/or emulating software. So, I figured, "okay...I'll just remove Nero." No good. Still nothing. So I bit the bullet and reformatted again. Now the game works fine.
Although, with this crack, the launcher for The Sims does not come up. As such, the glorious launcher tune will forever be missed (plus I had to manually edit the .exe with a hex editor to make it run at the right resolution as a result of the lack of launcher).
There is no patch for DLC2 v034, which is needed for TDU World to run. Replacing the old TestDrive2.exe with the patched one will result into problems in the launcher, so I used the Universal Launcher with it. Still freezing.
I had this problem when I started it with non-administrator privileges or I had a vga driver problem. only the universal launcher is willing to work in the game, but I turn it off before starting the windows defender.
The game uses SecuROM, a formerly popular DRM (digital rights management) system implemented by developers and publishers during the 2000s. Apparently, Disney has stopped providing authentication for SecuROM, as they revoked their subscription service. This means anyone reinstalling the game in the year 2019 or later is basically screwed.
Been testing out Crysis on Vista 64-bit. Ran into some strange behavior that doesn't appear to have been discussed online. Thought I'd document it here for reference:
- Launching the game using the 'Games Explorer' Crysis icon will launch the 64-bit exe.
- Launching the game by clicking 'Play' on the DVD launcher menu will launch the 32-bit exe (not sure if this can be corrected).
- With patch 1.2 installed (latest patch), the game refuses to launch fullscreen in Dx10 mode; it will always boot windowed. This issue does not occur in Dx9 mode and was introduced with patch 1.2; base 1.0 and patch 1.1 are unaffected and will launch properly in fullscreen in Dx10. The workaround for this on Nvidia hardware is to force vsync through the control panel. With vsync forced, the game will launch fullscreen in Dx10 mode on patch 1.2.
- Installing patch 1.2 breaks the graphical effect in which oil pools on the ground after an oil drum is pierced by a bullet. On base 1.0 and patch 1.1, the oil pools as you would expect but with patch 1.2, the oil pool decals are not aligned properly and appear to clip through the ground. I always loved this feature of the game, how the oil drains realistically, so it's a shame the latest patch breaks this.
- Helicopter rotors don't spin properly when using the 64-bit exe; the rotor blades appear to slow down intermittently rather than spin at a consistent speed. This issue does not affect the 32-bit exe.
- Anti-Aliasing causes artifacting in vegetation; with AA enabled, as you move through areas of vegetation, there are these little white specks of light that appear briefly on foliage. On occasion, the white spots are so big and bright that they look like muzzle flash from enemy weapons. This artifacting does not occur with AA disabled. It's also worth noting that the game readme mentions that AA can cause atmospheric effects to display incorrectly. The readme doesn't go into detail as to which effects are affected, but it seems like AA does not play nice with Cryengine 2.
- Texture streaming is disabled when using the 64-bit exe. MASSIVE improvement in texture quality as a result. This is mentioned in the game readme, thankfully.
- Texture streaming can be disabled when using the 32-bit exe with the 'r_TexturesStreaming' command.
Only Crysis 1 32bit incorrectly detects 3DNow! on AMD CPUs, the 64-bit executable doesn't use 3DNow! but in the past I had to activate Windows Vista sp2 (or sp1, I don't remember) compatibility mode. On Windows 10 with AMD Ryzen 1600 CPU I can assure you that it works (without modifications or launchers), I have not tried on Windows 11 but I guess so.
I tried the 32 bit fix and it doesn't give any sound. I could play the 64 bit version of v1
2.1 but 2 problems: crysis64.exe with vista comp doesn't work ans crysis.exe has securom issues that I haven't been able to fix with another executable
Upon inspection, I found your executable for Bin64 is 32-bit, but Crysis64.exe is 64-bit. Actually I assumed the other way around as the 32-bit executable is significantly larger in size but is labelled as a SONYDADC launcher (launchers are usually smaller but it's opposite here).
Fuel's default shortcut forces you to slog through the setup launcher pop-up before starting the game. Having to go through this launcher wastes time and is pointless once you have the game setup the way you like it.
The default shortcut points to "GameSetup.exe" in your FUEL install folder. If you tried to be smart / sneaky, and just run the "FUEL.exe" file you got a pop-up saying the game has to be ran through the launcher. Nuts. Guess you're out of luck.
They hid the main game launcher as "SecuLauncher.exe". I assume this stands for "secure launcher", because FUEL uses SecuRom DRM. It probably kicks off SecuRom to verify DRM, then kicks off FUEL.exe to get the game going.
What causes SecuLauncher failed to start application 2000? After analyzing extensive user reports and references, we found that the error is often related to a missing Visual C Redist package. Some other factors like corrupted games files, launcher incompatibility, missing admin rights, and SecuROM verifications are also responsible for the SecuLauncer failed to start application.[2000].
So it's done, after more than 3000 lines of code this little project of mine is ready to be released to public.
I am kind of late to the party but maybe this mod launcher will still be usefull to some gamers out there.
BertHunter 2013
ModLauncher: How does the "Data_main" feature work?
- The mod creators or you can create a new folder inside a mod's folder and name it "Data_main".
Everytime you start the mod using the launcher, all files inside "Data_main" will be moved to the Data folder of the game, while preserving folder structure.
If a file with the same name is already found inside the game's "Data" folder, it will be moved to a backup folder.
Once the the game closes, everything will be moved back.