![]() I would only hope for you guys to look into that and try out different possibilities for the executable to communicate with the system, that would be a beautiful solution that would help more users in the end than just those with Comodo.ĥ) Are there any steam 'launch options' or command line arguments I could try? Maybe its a DirectX problem? I would want to try launching in windowed borderless mode for example or forcing a specific version of DirectX if it is possible. Most probably it is related to some of the firewall's global policies like data execution prevention, where the firewall finds the exec calls nonacceptable and blocks them (although there's nothing like that in the log, thats weird). ![]() Since the call from Steam->Game executable was registered by the firewall (I see that specific 'create process' call in the log) and was explicitly allowed, and that the executable fails to launch - I believe this is not a Steam error. ![]() ![]() Googling reveals the only instance of that problem (with that same executable error too) was with a particular update of ARMA 3, and the problem was solved only for a couple of users who were actually using Comodo/Mcafee and uninstalled those, but not for the others. 1) I have tried running explicitly as admin - it doesn't helpĢ) As I mentioned earlier there is no log file.ģ) Launching through Steam gives an instant (no delay) error code 81 popup, launching the game exec directly gives a no delay instant "Application Load error Q:0000065432" both with and without Steam running in the background (doesn't force Steam launch in the latter case btw)Ĥ) I am indeed using Comodo, but as this is the first problem I have with it in a long time of use and I have put effort into configuring it/populating the lists etc., and unfortunately I am not willing to drop it. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |