Output File Not Really Obfuscated At All

[JayRenegade]

I've successfully managed to run ConfuserEX over a VS.NET 2013 Express .exe file.

Inspecting it with a hex editor reveals that the output file is slightly different from the input file.

Inspecting it with IL Spy, however, reveals that all the code is still readable. Every once in a while I will stumble across a variable name that has been changed, but not much else.

I was expecting a before/after difference such as the one displayed here: http://yck1509.github.io/ConfuserEx/.

What can I do to get ConfuserEX working well for me?

[yck1509]

Hi, I suppose you used it incorrectly. Would you mind telling more about how you use ConfuserEx to protect?

[JayRenegade]

I used the GUI.

I set the base directory to the directory of the .exe file. The GUI then says the output directory is going to be the Confused directory in the base directory.

I add the .exe file to the list below.

Then I go to the protect tab and push the button. I see a log of the file being successfully processed.

Another .exe file then appears in the Confused directory.

I compare the confused file with the original one and do not see much difference.

[yck1509]

You have to set protection rules. The simplest way is:

1. Go to Settings tab.
2. Select
3. Click + button
4. Select the newly added rule and click the edit button (with icon of notepad)
5. Choose Normal preset
6. Click Done

[JayRenegade]

Thanks, with your help I managed to get it working at maximum protection settings.

When I select the compressor packer, the software won't run though.

When you wrote '2. Select', did you mean select the compressor?

[yck1509]

The compressor problem should be fixed now. Please try again.

[JayRenegade]

It works great, thanks. Your software is awesome, mate.