[Resolved] Strange Issue With Publisher Signature

[Vicarian]

I've been trying to resolve this issue for quite some time today. I have the Steam version of FA. I reinstalled FAF and got the files as usual. Then I try running ForgedAlliance.exe from ProgramData. The game, despite setting the /log flag will not generate a log. Nor will it write changes to my Game.prefs file. When I attempt to run the game in this manner, I receive an error message saying that the file's publisher is unknown. Elevating the binary removes the error, but the game still won't write new data, therefore I can't generate any logs, or keep settings like unit cap, GAZ_UI settings, etc. Anyone know how I might resolve this? Searching the forums has turned up nothing, and resolutions found via Google for other cases not specific to FA aren't working for me.

[Vicarian]

Well, the temporary fix was basically copying over an old version of the binary I had on my laptop. Suppose I'll look into hex editing over the weekend to see if I can find a fix for the signature portion of the binary. Just means I won't be able to play online for a bit.

[Cuddles]

Did you run it as Administrator when you installed it?

[Vicarian]

The installation of FAF or the installation of FA via Steam?

[Xinnony]

FAF i thinks

[Vicarian]

Ok, so either Zep fixed the signature, or running FAF as administrator allowed my machine to ignore the security issue that the binary raised. Either way, I have 3631 now and it keeps settings.