Hello ramazanyusuf,
most likely your graphic card fails to render Arma 3 Launcher window correctly. Please start it in the safe-mode and disable the hardware acceleration for Launcher: https://arma3.com/launcher/troubleshooting

I'm still thinking about that, because Arma and Launcher shares the code, the upload/download technology is different, but the list of the items should be the same.

This is usually caused by large number of subscribed items on Steam Workshop. When a large list of mods is being processes, there is a momentary spike in memory usage while the list of mods is transferred from Steam to Launcher and if the OS can't allocated necessary amount of memory fast enough, it will cause the crash.

Hello,
could you please upload Launcher logs? You can export them from Options menu choose Export Launcher logs to Desktop. Also please check you desktop for any text file with error report, Launcher is supposed to create one when if it crashes.

Hello,
you're right, there seems to be an issue after Steam update on 18th January. We're trying to put together some details, but for now it seems that restarting Steam client helps to solve the issue.

Hello,
Steam client is supposed to always download the mods to a same drive as where the game is installed. We have no control over this.

Hello,
unfortunately Arma 3 Launcher no longer have control over download process, it's all controlled by Steam client.

Hello guys,
copy the file XAPOFX1_5.dll

• from Jun2010_XAudio_x86.cab to C:\Windows\SysWOW64\
• from Jun2010_XAudio_x64.cab to C:\Windows\System32\

Steam Wars: Episode IV - A New Hope
http://steamcommunity.com/groups/SteamClientBeta#announcements/detail/586991815869459128

Hello,
from Dependency Walker report it's clear that you've corrupted file C:\Windows\syswow64\XAPOFX1_5.DLL, which is a part of DirectX. You can get that file from another computer, attempt to re-install DirectX or use my fix from http://arma.jiripolasek.com/ if nothing above works.

Hello Sgt.Smile,
it seems that you're graphic card has a trouble rendering the program window. Please try to start Launcher in the safe mode and disable the hardware acceleration: https://arma3.com/launcher/troubleshooting

Hello,
this error, also known as Steam error 81, is often caused by 3rd party software that blocks Steam / game communication and prevents Steam from starting the game at all. In the past we've noticed that this was caused by Comodo Antivirus, Norton AV or Spacedesk (multi-monitor utility). Try to end all running software and start the game again.

The file at fault is C:\Windows\SysWOW64\X3DAUDIO1_7.DLL, you have wrong version of the file there (64-bit instead of 32-bit). You've to replace the file exactly on this path, and this path only (there are other files with the same name, but they are a different version).

Please save the report from Dependency walker, put it into ZIP archive and upload it here. We'll identify the corrupted file(s) for you.

Hello,
the error code means that the system can't start the game, because some file (or files) is corrupted. There are no game logs, because the game wasn't started yet. As is written on https://community.bistudio.com/wiki/Arma_3_Unusual_process_exit you can use Microsoft Dependency Walker (http://www.dependencywalker.com) to identify the corrupted DLL, and most likely you will come to that some DirectX file is corrupted.

In T122375#1556907, @SirBoston wrote:

And I do have "C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.dll"
Should I delete it?

In T122375#1556435, @SirBoston wrote:

Error Code: 0x80070002

In the correct installation of .NET Framework, there have to be a System.DLL on the exact path I've posted before. Otherwise the game launcher (and many other applications build on .NET Framework 4) can't work.

Hello,
according to the report its an entirely different file "System.Management.Automation.dll", not "System.dll".
Are you sure that you've send a report for the correct file?

Hello SirBoston,
I'm sorry for the delay, I didn't forgot about you, but rather run out of options that can be easily done.

Hello xnooztv,
it seems that you've libraries from two different versions of Launcher combined in one folder, and that is causing the crash. If the verification of the game cache doesn't help, please manually delete the folder D:\Program Files (x86)\Steam\steamapps\common\Arma 3\Launcher\fr-FR\ . This will fix the crash, but also it will remove French localization; to re-download it you have to run the verification of the game cache again.

Hello blackxpade,
the logs says that Launcher can't start because it can't load the file D:\Steam\steamapps\common\Arma 3\Launcher\log4net.dll.
Did you tried to verify the integrity of the game cache as Jawsh suggested? It should force Steam to re-download any corrupted or missing file. If the issue will persist after that and the file exists in the directory (as written above), please try to delete the file and verify the game cache again to force the re-download.

Hello,
according the error code it is a Steam error 53 (35 hexadecimal = 53 decimal). Please take a look at theirs support page for this error: https://support.steampowered.com/kb_article.php?ref=9677-EUDC-7384

That means that your Windows version has this .NET Framework already implemented as part of the system. So you have to run the check on the system itself:

You can try to uninstall it and install it again (I'd suggest to restart the computer in between) or try to use this tool Microsoft .NET Framework Repair Tool: https://www.microsoft.com/en-us/download/details.aspx?id=30135

Hello SirBoston,
you're missing the core .NET Framework library which is required to run Arma 3 Launcher. Please try to re-install the latest .NET Framework to fix the issue: http://go.microsoft.com/fwlink/?LinkId=780601

Hi, it's actually my fault, because it's based on the development branch version, so Launcher is expecting the 64-bit executable in the installation folder. I'm sorry, I focused too much on the problem at hand and forgot about this "little" detail. I'll fix it tomorrow first thing in the morning, but you can workaround the error message by copying the arma3.exe as arma3_x64.exe to give Launcher what it expects.

Hello,
could you please try this version: http://arma.jiripolasek.com/files/Launcher_999901.zip ? I believe that I've pinpointed (and fixed) the problem.

Hello James,
yes, you're safe to use the older Launcher, at least for now. As for the other versions I want to test them before I send them to you, to not bother you needlessly, but my Steam is currently acting up and I'm trying to make it work again.

Hello edog1234567,
can you please go to: Steam / Settings / Downloads and click on Clear download cache?

Ok, that's great.

Hello jumbo,
I'm afraid that I can't offer you much of a help in this case. But I'll bring this issue to attention of BattlEye developers. Or you can contact them yourself if you want: https://www.battleye.com/support/

Thank you for the logs, James.
Could you please try this version of Launcher? It's the version from previous release (1.64): http://arma.jiripolasek.com/files/Launcher_138522.zip
It should be enough to unpack it to your desktop, if the installed correctly, it should find it automatically.

Hello,
could you please try to disable BattlEye integration in Launcher, and start the game through Launcher without BattlEye. Is then FreeSync active or not?

Hi James,
could you please upload me a new log to see where the error has moved after adding the page file?

Hello James,
TheMasterofBlubb is the most likely right. It is likely that the issue can be fixed by enabling the page file (because the cause would be the memory fragmentation). Could you please give it a try and re-enable the paging file?

Hello,
in Launcher you have to switch the selected platform to 64-bit at Parameter / All Parameters. The default version is set to 32-bit game, because at this moment it is more compatible with existing mods.

Hello James,
the logs shows that the error occurs rather quickly and is always tied to retrieving the list of running programs (Launcher searches the list for the game). It looks like a good point where to put some diagnostics, I'll update Launcher and send you a diagnostic build to gather more information about the issue.

In T121989#1547484, @Ex3s wrote:

Well, everything works fine until I click on the mods tab. I'm guessing I have way too many.

Hello,
I have a quick question: by any chance, did you disabled your paging files on all your drives?

Hello Ex3s,
thank you for the logs. We're currently investigating the issue and putting together some tools to diagnose the issue you're experiencing.

Hello James_Fritz,
could you please attach the complete logs from Launcher and attach them to the issue of feedback tracker? You can either get Launcher to create it from Option / Export Launcher logs to desktop, or gather them manually: http://arma.jiripolasek.com/howtos.html

In T121973#1545172, @celticalliance wrote:

I am not sure if this is related to this issue but after the hotfix I have noticed that in the Launcher, in the Mods section, there is an orange star behind the preset name to indicate it is not saved yet. This started happening AFTER the hotfix was applied and I made a few changes to a preset.

After saving the preset, when I close down the Launcher and restart it the preset still appears as unsaved.

Merely mentioning this because it may be related since my issue relates to mods, and presets seem to be marked as unsaved now.

Hello,
sorry for the trouble. Could you please upload the Arma 3 Launcher logs? This is how you get it manually: http://arma.jiripolasek.com/howtos.html

Hello,
could you please go to BattlEye page in Arma 3 Launcher and disable to check to disable the BattlEye.

Hello,
we're sorry for the inconvenience. I'm afraid I'm currently not aware of any possible fix as this is the first time I've encountered this particular issue on Windows 10. We know that it happened (and happens) to some users on Windows 7, and it is caused by particular Windows patch and that it could be fixed by uninstalling the patch. But it seems that on Windows 10 the fix won't work in the same way.

Hello,
the game can't start without Steam running. If the Steam client is running, then it is probably blocked by some security settings on your PC (it can be either the operating system, or an antivirus or a firewall) and is not accessible by the game launcher or the game itself. Other possible solutions are listed here: https://community.bistudio.com/wiki/Arma_3_Unusual_process_exit#0x00000035_-_ERROR_BAD_NETPATH

Hello,
we've tried to emulate your problems, but unfortunately we've discovered that the old version of Publisher won't work anymore as it requires an old version of Steam client and Steam services that are no longer available.

Hello,
Steam have downloaded a files from two different version of the game. Apparently Steam is unable to get the correct files by itself. Please delete folder E:\Steam\steamapps\common\Arma 3\Launcher and then verify the integrity of the game cache again, that should force Steam to re-download the correct files.

Hello,
I'd guess that instead of creating the shortcut, you've moved Launcher to your desktop by accident. Launcher program is then missing the other files that it needs to run and that are in the game directory.

Hello payuu123,
as posted above, you basically have two options:

You can wait for Microsoft to release an updated version or uninstall it (http://windows.microsoft.com/en-us/windows/troubleshoot-problems-removing-updates#1TC=windows-7)

@Jawsh: It affects only some users, not all of them. This issue appeared only after the mentioned patch was released by Microsoft and it can be fixed by uninstalling the patch. But above that we've never been able to determine the exact cause, not even to replicate the issue on any of our machines.

Hello,
as far as we know this issue is caused by the Windows security update KB3078601. You can wait for Microsoft to release an updated version or uninstall it (http://windows.microsoft.com/en-us/windows/troubleshoot-problems-removing-updates#1TC=windows-7)

Not at all. Those are not real folders, but a directory junction - kind of a virtual folder that shares content with another folder. So the files you see in there are not the copy but literally the same file as in Steam\steamapps\workshop\content\107410.

Hello ookexoo,
thank you for bringing this to our attention. The intended behavior is indeed that the directory link (the "folder" in the !Workshop folder) should be renamed when the name of the mod changes. We'll investigate why this is not happening and fix the issue.