Page 1 of 1
Incompatible with Windows 2012 R2
Posted: Sun Jan 07, 2018 3:18 am
by buzzard
I can't Open .exe here. It crashes frequently and Ref to
http://go.microsoft.com/fwlink/?linkid=280262
How Can I fix It? It's Ok Without Protection.
Re: Incompatible with Windows 2012 R2
Posted: Sun Jan 07, 2018 3:34 am
by buzzard
Code: Select all
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: TinderFox.exe
Problem Signature 02: 1.0.8.0
Problem Signature 03: 5a4deecf
Problem Signature 04: mscorlib
Problem Signature 05: 4.0.30319.34209
Problem Signature 06: 534894cc
Problem Signature 07: 34a
Problem Signature 08: 2f
Problem Signature 09: System.ArgumentOutOfRange
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: ce5b
Additional Information 2: ce5b49422f022c6dda4928588238e53e
Additional Information 3: 7fbe
Additional Information 4: 7fbed352f6a86ade60b7e7da12660f5d
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=280262
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Code: Select all
Problem signature:
Problem Event Name: APPCRASH
Application Name: TinderFox.exe
Application Version: 1.0.8.0
Application Timestamp: 5a4deecf
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.3.9600.16408
Fault Module Timestamp: 523d4548
Exception Code: c000041d
Exception Offset: 00012eec
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 06b1
Additional Information 2: 06b1102270e737fdfaf8eb0eaa5854b0
Additional Information 3: 11c6
Additional Information 4: 11c68d2a882e63432b923f2309d894b3
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=280262
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
This Two Errors
Re: Incompatible with Windows 2012 R2
Posted: Mon Jan 08, 2018 1:20 pm
by Enigma
Hi buzzard, can you please send us this NON protected file and all files that we may need to test the issue at
support@enigmaprotector.com?