fehler meldung beim start des server

Bitte um Hilfe habe folgende Fehlermeldung bei Altis Life

arma 3 bin\config/cfgdiffcultypresets.fadedistancestart

Altis Life 4.4
Windows Rootserver

kann mir jemand bei dem fehler helfen ?
Logofile
[2016-05-30 20:26:42] Log session started
[2016-05-30 20:26:42] [0,0] SetSteamID( [A:1:0:0] )
[2016-05-30 20:26:42] [1,2] Connect() starting connection (eNetQOSLevelMedium, 162.254.197.42:27020, UDP)
[2016-05-30 20:26:43] [1,2] ConnectionCompleted() (162.254.196.41:27018, UDP)
[2016-05-30 20:26:43] [1,2] RecvMsgClientLogOnResponse() : [A:1:2770167810:6883] 'OK'
[2016-05-30 20:44:21] [3,2] LogOff()
[2016-05-30 20:44:21] [2,2] AsyncDisconnect()
[2016-05-30 20:44:21] [2,2] Log session ended

seit dem update

nein auser update auf die konsolen version nix

[2016-06-02 17:44:31] Loaded 1 apps from install folder "D:\Server\A3Master\steamapps\appmanifest_*.acf".
[2016-06-02 17:53:14] Loaded 1 apps from install folder "D:\Server\A3Master\steamapps\appmanifest_*.acf".

[2016-06-02 17:44:35] [3,2] LogOff()
[2016-06-02 17:44:35] [2,2] AsyncDisconnect()
[2016-06-02 17:44:35] [2,2] Log session ended
[2016-06-02 17:53:14] Log session started
[2016-06-02 17:53:14] [0,0] SetSteamID( [A:1:0:0] )
[2016-06-02 17:53:14] [1,2] Connect() starting connection (eNetQOSLevelMedium, 162.254.197.40:27018, UDP)
[2016-06-02 17:53:14] [1,2] ConnectionCompleted() (162.254.197.40:27018, UDP)
[2016-06-02 17:53:14] [1,2] LogOff()
[2016-06-02 17:53:14] [1,2] AsyncDisconnect()
[2016-06-02 17:53:14] [1,2] Log session ended

das sind die einzigen neuen logs ! die eingetragen sind !

meine config vom server !
maxPlayers = 100;
passwordAdmin = "pg";
class Missions {
class ARMA {
template = "Altis_Life.Altis";
difficulty = "Regular";
};
};
voteMissionPlayers = 0;
voteThreshold = 0;
disableVoN = 0;
vonCodecQuality = 1;
persistent = 1;
equalModRequired = 0;
hostname = "";
password = "";
verifySignatures = 0;
motdInterval = 0;

log vom 27.05 ist die neueste

ja firewall habe ich getestet !

jetzt installiere ich mein steam neu
das letzte was mir einfällt !

closed ! fehler lag wohl an dem update selbst