Page 1 of 1

ERROR 36 HELP

Posted: 2015-11-23 15:54
by Clup
I installed PR after I refreshed my Computer I had the installer of 1.3. I installed it after installation when I opened the file it said error 39: Key Error. Then I went to a post in which it said it was fixed in 1.3.1.0 it said to download prbf2_1.3.0.0_to_1.3.1.0_client_patch.prpatch to fix it but after it i got a message of Error 36: Key Error. Log file is
Thanks Im waiting to play PR

Code: Select all

Project Reality Log File
PRLauncher.exe started at: 2015-11-23T21:15:18

Critical Error: 36: Key Error.

 > System.IO.FileNotFoundException: Could not load file or assembly 'System.Security, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Security, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at Reality.Utils.DataProtection.Protect(Byte[] a)   at K.a(MethodBase a, Boolean b)
   at K.Ob(b a)
   at K.d()
   at K.e()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


Re: ERROR 36 HELP

Posted: 2016-07-02 11:59
by StalkerBR42
Same Error for me.

Code: Select all

Project Reality Log File
prlauncher.exe started at: 2016-07-02T08:42:26

Critical Error: 36: Key Error.

 > System.BadImageFormatException: Could not load file or assembly 'System.Security, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The module was expected to contain an assembly manifest.
File name: 'System.Security, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at Reality.Utils.DataProtection.Protect(Byte[] a)   at da.a(MethodBase a, Boolean b)
   at da.Ob(a a)
   at da.d()
   at da.e()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



I've tried starting with the administrator mode and compatibility but nothing works.