.NET Reactor doesn't work on Win 7 Ultimate?

[jacob]

Subj

I have long ago used .NET Reactor 3.1.0.0 on Windows XP, worked more
or less well. Now tried to use Reactor 4.1.0.0 and then 4.2.7.5 under
Win 7 Ultimate, it just doesn't work! Using almost any protection
method leads to protected application crashing upon startup with
InvalidProgramException! What the heck? I have tried to create an
absolutely basic Hello World application without a line of my own code
and protect it, to ensure it's not my program doing something
incompatible, still doens't work.

I tried to enable protections one-by-one and found the following. Only
three protection methods seem to work for me now: 1) Native Exe Stub,
2) Obfuscation, 3) Control Flow Obfuscation. As soon as I select any
other method (like Supress ILDASM, or NecroBit or String Encryption or
any other method) protected executable stops working. If I enable any
locks (like expiration date lock or any other) application doesn't
work, too!

Have sent an e-mail to support a few days ago, sent another one today
- no reply! Interesting way of work.

So, everyone - beware. I wonder how this Reactor can be used for
commercial applications if these applications stop working on Win 7 as
a result (even if it is just Win 7 Ultimate)?

I'll post here further if I receive any response from support.

--
You received this message because you are subscribed to the Google Groups ".Net Reactor Support" group.
To post to this group, send email to net-react...@googlegroups.com.
To unsubscribe from this group, send email to net-reactor-sup...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/net-reactor-support?hl=en.

[Glen Harvy]

Hi Jacob,

First of all you should change the subject line by adding 'does not work
for me.'

I have one problem only with my .Net Reactor program running on Win7
Ultimate and that is I can't use Control Flow Obfuscation. I also can't
use Native Exe Stub because my project runs on x64 bit machines as well.
The Control Flow Obfuscation may or may not have something to do with
the OS however I find that very hard to believe.

When I asked Denis for help regarding Control Flow he offered to go
through my project for me to ascertain the cause. He actually wanted the
code so he could fix or create a work-around to incorporate into .Net
Reactor. I preferred that he not waste his time going through my
thousands of lines of code as together with everything else, I could
live without Control Flow Obfuscation.

It turns out that a more recent release of .Net Reactor plus some code
changes on my part seem to have fixed that issue as well although I
cannot be certain. I have still not enabled Control Flow Obfuscation
although I have hived of part of my code to a dll (that was a design
decision not influenced by .Net Reactor) which has Control Flow
Obfuscation.

You may be interested to know that I also can't use Windows Firewall
that comes with Win7 Ultimate. Now writing to support at MS is one
thing. Getting a meaningful reply without coughing up many hundreds of
dollars which will only be refunded if it's found to be a bug in Windows
Firewall is not an option. I paid $25 and upgraded my AVG Anti-Virus to
include their Firewall - works great.

My version of .Net Reactor works more or less well as well. So does
Windows 7 Ultimate work more or less well. Oddly enough, I am very happy
with both of them - more or less.

Do you think you can post some detailed information, perhaps a copy of
your email support request to Denis for example, so that we may all try
to help you overcome the less with the more.

Glen.

[jacob]

Hello Glen, thanks for replying.

Well, it doesn't work FOR ME but it's not my program (since even the
Hello World without single line of my code doesn't work) and my system
is pretty standard 32-bit Win7 Ultimate, really. No weird system
software installed, my CPU is pretty widespread Intel Core 2 Duo etc.
So, I don't understand which is here specific to me or my system.

I'm sorry that Control Flow Obfuscation doesn't work for you, as far
as I understand it is one of the key protections of Reactor, as it
seems to make it impossible to decompile back to pure C# (Reflector
crashes attempting that), which makes modification of the protected
version a substantially more challenging task. At least I hope it
makes it impossible, for that Reactor needs to irreversibly destroy
the C#-specific structure of the IL, which I think should be
theoretically possible.

I have never encountered any problems in Microsoft software, by the
way. It seems to do its work very robustly, not having a lot of
features but what they have usually works.

Regarding my e-mail to support, I mostly explained everything, except
giving the error details that I get when run protected executables.
Not sure if it is useful to anyone, but here they go:

When using just the Necrobit protection (here and below I am turning
on ONLY the protection described, the other protections are turned
off):

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: helloworld.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 4bf46e43
Problem Signature 04: HelloWorld
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4bf46e43
Problem Signature 07: 5
Problem Signature 08: 12
Problem Signature 09: System.InvalidProgramException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

When using Anti ILDASM:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: helloworld.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 4bf46e26
Problem Signature 04: HelloWorld
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4bf46e26
Problem Signature 07: 4
Problem Signature 08: 12
Problem Signature 09: System.InvalidProgramException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

When using Anti Tampering:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: helloworld.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 4bf46e02
Problem Signature 04: HelloWorld
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4bf46e02
Problem Signature 07: 4
Problem Signature 08: 12
Problem Signature 09: System.InvalidProgramException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

When using String Encryption:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: helloworld.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 4bf46dde
Problem Signature 04: HelloWorld
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4bf46dde
Problem Signature 07: 4
Problem Signature 08: 12
Problem Signature 09: System.InvalidProgramException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

When using Compress & Encrypt Resources:

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: helloworld.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 4bf46db6
Problem Signature 04: HelloWorld
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4bf46db6
Problem Signature 07: 4
Problem Signature 08: 17
Problem Signature 09: System.InvalidProgramException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

I have checked (attaching the debugger) that the exception happens not
inside the code of the application, but before that.

> For more options, visit this group athttp://groups.google.com/group/net-reactor-support?hl=en.- Hide quoted text -
>
> - Show quoted text -

[Glen Harvy]

Well it certainly has me baffled because, as I said before, works for me
on Windows Ultimate.

Perhaps someone else will be able to assist you.

Good luck.

Glen.

[jacob]

Hi everyone.

I have received a reply from support on Saturday, and we have found
out that somehow my .NET Reactor license made this happen (?). At
least, in demo mode program works fine. I wonder how this could have
happened given that the license was accepted by .NET Reactor, showed
my name in the title bar correctly etc, however this is what happened.
So if anyone else has this problem - trying demo mode is a good idea.