Forged Alliance Forever Forged Alliance Forever Forums 2015-08-18T23:47:59+02:00 /feed.php?f=3&t=10464 2015-08-18T23:47:59+02:00 2015-08-18T23:47:59+02:00 /viewtopic.php?t=10464&p=107850#p107850 <![CDATA[Re: Can't launch client on Windows 10]]> I had the same issue since forever and I did infact run FAF as Admin to get it started on Windows 7 :|
Since it annoyed me, I deactivated running FAF as Admin and started it to get the error message.

When reading on, have in mind that you could have a totally different error than me.
Confirm your error first before trying to apply patches that won't help.

The error message on running points towards the file in your FAF installation directory,
e.g.: C:\Program Files (x86)\Forged Alliance Forever\FAForever.exe.log

I opened up that file which told me about the actual error:

Traceback (most recent call last):
File "main.py", line 44, in <module>
File "util\__init__.pyc", line 169, in <module>
File "logging\__init__.pyc", line 1530, in basicConfig
File "logging\__init__.pyc", line 903, in __init__
File "logging\__init__.pyc", line 926, in _open
IOError: [Errno 13] Permission denied: 'C:\\ProgramData\\FAForever\\logs\\forever.log'


As you can see, this error points to ProgramData, which is a totaly different Folder.
For me the solution from here was to edit the security settings of the file so Users could edit forever.log.

For doing so right click the file, choose Properties, go to the tab Security, click Edit, choose User ("Your Pc-Name"/Users)
and change it below so you can alter and write - which was off for me.
Confirm the changes and leave the dialog, the game should start without admin rights.

I might have messed up some translations since my Windows-Interface is not in English.
There might be other ways or other security settings that might work, however, this is just what I tried out.

Also, this link might provide helpful information on changing security settings:
https://social.technet.microsoft.com/forums/windows/en-US/fd054677-9555-4e08-a179-4253acdc1709/how-to-change-security-settings-of-files-and-folders

The issue - at least for me - seems to be that running FAF as your "normal" User does inherit the user-rights to it and
since default users can't alter files in that ProgramData-Folder faf throws an error when starting.

Statistics: Posted by darkAco — 18 Aug 2015, 23:47


]]>
2015-08-01T19:44:08+02:00 2015-08-01T19:44:08+02:00 /viewtopic.php?t=10464&p=106343#p106343 <![CDATA[Re: Can't launch client on Windows 10]]> Statistics: Posted by DeadMG — 01 Aug 2015, 19:44


]]>
2015-08-01T16:15:09+02:00 2015-08-01T16:15:09+02:00 /viewtopic.php?t=10464&p=106338#p106338 <![CDATA[Re: Can't launch client on Windows 10]]>
DO NOT RUN FAF AS ADMIN.

Statistics: Posted by Deering — 01 Aug 2015, 16:15


]]>
2015-08-01T14:06:42+02:00 2015-08-01T14:06:42+02:00 /viewtopic.php?t=10464&p=106328#p106328 <![CDATA[Re: Can't launch client on Windows 10]]>
hotfog wrote:
Well, for those having this problem, the solution is mentioned in the first post!!

I too had this problem and managed to decrypt the first post.

The solution is :
1. Right click on the FAF icon.
2. Click on RUN AS ADMINISTRATOR.

fixes the crash when trying to join games / host games.

ps - you can do a permanent fix by right clicking on FAF icon, click properties, click compatability, click Change settings for all users, Ensure "Run as Administrator" is ticked, click apply then ok. Sorted.

:)


I don't recommend running FAF with administrator priveleges. It's not the right fix for the problem.

Statistics: Posted by Sheeo — 01 Aug 2015, 14:06


]]>
2015-07-31T19:16:03+02:00 2015-07-31T19:16:03+02:00 /viewtopic.php?t=10464&p=106275#p106275 <![CDATA[Re: Can't launch client on Windows 10]]>
Image

Statistics: Posted by DeadMG — 31 Jul 2015, 19:16


]]>
2015-07-31T18:56:04+02:00 2015-07-31T18:56:04+02:00 /viewtopic.php?t=10464&p=106272#p106272 <![CDATA[Re: Can't launch client on Windows 10]]>
I too had this problem and managed to decrypt the first post.

The solution is :
1. Right click on the FAF icon.
2. Click on RUN AS ADMINISTRATOR.

fixes the crash when trying to join games / host games.

ps - you can do a permanent fix by right clicking on FAF icon, click properties, click compatability, click Change settings for all users, Ensure "Run as Administrator" is ticked, click apply then ok. Sorted.

:)

Statistics: Posted by HotFog — 31 Jul 2015, 18:56


]]>
2015-07-31T13:15:26+02:00 2015-07-31T13:15:26+02:00 /viewtopic.php?t=10464&p=106254#p106254 <![CDATA[Re: Can't launch client on Windows 10]]>
Edit: and i didn't do have to do anything, just launched like I always did.

Statistics: Posted by Cuddles — 31 Jul 2015, 13:15


]]>
2015-07-31T10:50:44+02:00 2015-07-31T10:50:44+02:00 /viewtopic.php?t=10464&p=106243#p106243 <![CDATA[Re: Can't launch client on Windows 10]]>
DeadMG wrote:
I upgraded from Win7 to Win10. Win7 doesn't apply strict permissions to Program Files, but Win10 does. When you try to launch the client, it can't launch because it can't gain write permissions to the log file. You can of course launch the client in admin mode but that shouldn't really be required.


They use the same permission scheme and settings.

The issue is that your new user account doesn't have access to your old acl. I agree we shouldn't be putting logs in programdata / or really any of our data in there, since it requires installer-managed priveleges, which are brittle.

One problem with using $HOME/AppData is that the game can't handle unicode characters in filesystem paths, so that leaves out support for users with such characters.

Statistics: Posted by Sheeo — 31 Jul 2015, 10:50


]]>
2015-07-31T04:03:52+02:00 2015-07-31T04:03:52+02:00 /viewtopic.php?t=10464&p=106235#p106235 <![CDATA[Re: Can't launch client on Windows 10]]> Statistics: Posted by nine2 — 31 Jul 2015, 04:03


]]>
2015-07-31T02:42:00+02:00 2015-07-31T02:42:00+02:00 /viewtopic.php?t=10464&p=106233#p106233 <![CDATA[Re: Can't launch client on Windows 10]]> Any suggestions on what to try here?

Statistics: Posted by fuzzybum — 31 Jul 2015, 02:42


]]>
2015-07-31T02:14:46+02:00 2015-07-31T02:14:46+02:00 /viewtopic.php?t=10464&p=106232#p106232 <![CDATA[Re: Can't launch client on Windows 10]]> As a temporary measure, log files can be turned off

Are you 100% sure its the log files? Maybe it's not. Maybe post your log file

Statistics: Posted by nine2 — 31 Jul 2015, 02:14


]]>
2015-07-30T20:22:37+02:00 2015-07-30T20:22:37+02:00 /viewtopic.php?t=10464&p=106209#p106209 <![CDATA[Can't launch client on Windows 10]]>
Firstly, I'd argue that the log file is frankly an optional extra that the client should be able to function without.

But secondly, the client should be able to stick it in a temp directory somewhere that is not admin-only, so you can start FAF without administrator permissions.

I would post the log file like the kitty asks but.. well.. given the nature of the issue, I highly doubt that the log file on my disk contains anything relevant.

Statistics: Posted by DeadMG — 30 Jul 2015, 20:22


]]>