How To Fix Launcher.exe Application Error

[Natalí Stibb]

Ive read through quite a few threads on the SWToR website and this one as well. I've attempted to run the repair utility ( -WARS-The-Old-Republic/GUIDE-Launcher-Troubleshooting/m-p/4805820#2); I've uninstalled the game and reinstalled via the SWToR website and that didn't work; I uninstalled and reinstalled via my old CDs and that didn't work; I've also checked my AV (AVG Free) and Windows 7 firewalls and SW is allowed access. I had read it may be an issue with the BITRAIDER files, but I didn't have any of the aforementioned files to play with: =729911 when I went through my EA file directory.

I'm not very technical in the PC sense (bought a gaming PC to play this game), so some of the more technical talk is above me. I found this post but it's a little daunting and I'm not sure if it's still applicable? =673714

EDIT: reinstalled from Website, ensured I added the entire EA folder to my AV exceptions list and now the launcher actually opens (ST). It attempts to start downloading but I receive an error that says it's encountered an "unspecified error, please try this patch again". Then the same 05 error occurs.

I also had this application error today. It happened after installing AVG free. To fix this opened up the AVG desktop. In the top right hand corner click on menu. From there go to settings and click on exceptions. Once you're in exceptions, go to browse and add the entire EA file (I know there are only certain files that NEED to be added but this is the easiest way). Usually it's kept at C:>Program Files x86 (or just Program Files if you're using 32bit WIN)>Electronic Arts. Click on the box next to the file and hit okay. Then hit green "OK" button on AVG. Afterwards it should load fine (or at least it did for me).

So i got this error 1 week ago tesv.exe application error 0xc000001d,been trying to fix it.Skyrim was working fine before.Then i stop playing for 3 days,i run skse like usual and bam error.So i un-installed every mod i have,re-install one by one checking to see what was the problem.And it's enb wich is causing problem, specifically d3d9.dll.This is what the event log says.

Same Error here. Using MO to launch the game start giving this error. Skyrim successfully launches trough the Steam and trough SKSE (from game folder), but launching it trough MO (both vanilla and skse) causes this error.

I'm suffering the same error, also on Windows 10, as of just a few days ago. It's definitely related to ENB - launching Skyrim without ENB does not trip the error, and launching it with the ENB d3d9.dll invariably does, regardless of whether it's through MO or not. I've also been able to use a SweetFX d3d9.dll just fine.

The problem for me started when my computer installed the Windows Creators Update, which is (as far as I can tell) the only thing that could have caused the game to stop working for me literally overnight. It seems that that error code relates to the program not being able to access a resource it needs, so that update must have changed or moved some component that ENB is expecting... and since Boris isn't interested in working on compatibility for Windows 10, it may well be borked forever, unless someone can identify what got screwed up.

Same issue and the ONLY thing I've added to Win 10 is the new update from last week for 'creators'. Wonder if Microcough broke something with DX9 games. I know they have some DX12 update coming out pretty soon.

Hello, exactly as IMAetAR said above, if TESV.exe, SkyrimLauncher.exe or skse_loader.exe have the option to run in compatibility mode active with any of the previous windows operating system like Win7 or 8, remove the compatibility mode on all 3 files.

iTunesHelper.exe - Application Error: The application was unable to start correctly (0xc0000022). Click OK to close the application.

I tried completely deleting everything itunes and its related components in the specific order suggested (i first deleted itunes then apple software update, then apple mobile device support, apple application support 32-bit, apple application support 64-bit), then even restart in safe mode, ran a cleaner to make sure nothing remained.

Thanks packiayaraj! I have experience that problem before and Im sure I will go through it again, at least now I have somewhere to look.. I would always google my errors and get all sorts of methods...

I keep getting random HP .exe application error messages, and I don't know how to get rid of them. I've tried everything and they haven't gone away. It could have something to do with some updates I recently applied. I don't know. I'm not an expert on this at all. I just want some help.

Updating the Nvidia drivers just meant i could get into the game again.

However that bug was a follow up error. The original bug was the CTD while I was in the sim.

That was posted 1st, the 2nd issue was resolved with a driver update.

Have a look at your Reliability and Maintenance history. I was having a number of CTDs when I checked my history and I noticed that the GameManager which is Synapse 3 for razer products was having issues also. Uninstalled and the CTDs seemed to be a lot less. From what I read Synapse 3 has been causing a lot of issues in a lot of games. You might find something conflicting with MSFS in there.

However, it is crashing (everytime, also when I use the additional data that I downloaded on the first time, usually on the FlightSimulator+0x193b422 address, previous calls can vary) when I select the flight:

Looks like, the problem was with the low available memory. I noticed in the task manager that if the commited memory is going to be full than it crashes. Firstly, I increased the virtual memory by 4GB but it was not suffiecient. 16GB memory increase seems to be OK. I measured that the application needs around 10GB to start a basic flight.

Now, I am using the previously downloaded data.

I had similar CTD errors right after installing for the first time the game, wouldn`t pass in the Fly stage when Loading. After some reading and updating every software and Windows, did also the BIOS and Chipset Updates for MainBoard, still no succes at that time. What I think it solved my issue was the fact that I had no Paging Files alocated in the system and did some tweeks setting up on the HDD the minimum Paging files - 16000MB and maximum 48000MB, and after this the Game loaded and I could fly normal and without any other errors.

So try it, maybe this is the solution, and give a feedback.

Good luck!

In most cases, client.launcher.exe file problems are due to the file missing or being corrupted (malware / virus) and often seen at Third-Party Application program startup. Ordinarily, installing a new version of the EXE file will repair the problem creating the error. Moreover, as an overall cleanup and preventive measure, we recommend using a registry cleaner to cleanup any invalid file, EXE file extension, or registry key entries to prevent related error messages.

Please take caution in ensuring the file is placed in the correct file directory. Following these instructions carefully should resolve your client.launcher.exe error, but we recommend running a brief check. Re-open and test Third-Party Application to see if the issue has been successfully solved.

Third-Party Application-involved client.launcher.exe issues happen during install, when client.launcher.exe-related software is running, startup or shutdown, or during the Windows installation process. It's important to note when client.launcher.exe issues happen, as it helps troubleshoot Third-Party Application problems (and report to Windows Software Developer).

The launcher did not gave any options what apps/components should be installed from the start. I think thats what the launcher is for right? To install the apps. But I can not launch it from our company network.

If we use the launcher outside our company network we do not get this error. Thats the reason we think it has something to do with specific ports used by the launcher. Are they the same as the ports from the nucleus documentation you send me?

@maximilian.auer -

Please look at this link to see information about firewalls in terms of Nvidia Launcher. Allowing these links (or all of nvidia.com) should solve your issues with Launcher at work vs home.

The Firewall re-encrypts with the companies private Certification Authority, so the client needs to check the certificate against a private root ca certificate.

The Firewall delivers the webservers certificate and the appropriate intermediate certificate, so the chain should be completely available for the client.

Debugging and checking the logs provided by maximilian.auer brought us to the electron framework. It seems the omniverse clients is build with this framework. According this issue[1] on Github it depends on the underlying http request lib if an internal ca store (like Firefox) or the system ca store is used to check the Certificate provided by a Webserver.

[1] Electron's chromium is trusting different CAs then Electron's NodeJS Issue #11741 electron/electron GitHub

[2] Ignore invalid self-signed ssl certificate in node.js with https.request? - Stack Overflow

3a8082e126