[HELP] Error: "File is already protected (packed), protection stopped" - Even with Fresh Compilation

[gto70070]

Problem Description
I'm encountering a persistent error when trying to protect my C# executable with The Enigma Protector. The error message is:

ERROR: Unexpected exception: 檔案已經被保護（壓縮）過，保護已停止
(Translation: File is already protected (packed), protection stopped)
Technical Details
Target File: MyApplication.exe (C# .NET Framework 4.7 application)
File Entropy: -1.05 (shown in log)
Development Environment: Visual Studio, C# 7.3
Project Type: Windows Desktop Application
What I've Already Tried
Complete folder deletion and recompilation
Deleted entire project folder
Recreated project from scratch
Recompiled with fresh build
Visual Studio cache clearing
Cleaned solution
Rebuilt solution
Deleted temporary files
Different build configurations
Tried both Debug and Release modes
Verified no optimization settings are enabled
Log Output
[20:14:43] Loading project settings...
[20:14:43] Loading main information
[20:14:43] Loading registration features - Registration information storage
[... (additional loading messages) ...]
[20:14:43] Protecting file: C:\MyProject\bin\debug\MyApplication.exe
[20:14:43] File entropy: -1.05
[20:14:43] ERROR: Unexpected exception: 檔案已經被保護（壓縮）過，保護已停止
Questions
Why does The Enigma Protector detect my freshly compiled executable as "already protected"?
Is the negative entropy value (-1.05) indicating a problem with the file?
Are there any specific Visual Studio settings that might cause this issue?
How can I ensure my executable is in a "clean" state for protection?
System Information
Windows 11
Visual Studio (2022)
.NET Framework 4.7
The Enigma Protector (7.80)
Additional Notes
The executable runs perfectly fine before attempting protection. This issue persists even with completely new projects and fresh compilations.

Any help or guidance would be greatly appreciated!

Thank you in advance for your assistance.

[Enigma]

Hi, try to enable the option Miscellaneous - Other - Do not check if compressed.

[gto70070]

Hi, try to enable the option Miscellaneous - Other - Do not check if compressed.

Thank You - Problem Solved!
Hi Enigma,

Thank you so much for the quick response and solution!

Solution Confirmed
I enabled the option Miscellaneous → Other → Do not check if compressed as you suggested, and it worked perfectly!

Results
The protection process now completes successfully
No more "File is already protected" error
The executable works normally after protection
What I Learned
It seems the issue was related to The Enigma Protector's compression detection algorithm incorrectly identifying my freshly compiled C# executable as already compressed/protected, possibly due to the negative entropy value (-1.05).

For Future Reference
For anyone else encountering this issue with C# .NET Framework applications:

Go to Miscellaneous → Other → Do not check if compressed
Enable this option to bypass the compression detection
This resolves the false positive detection
Appreciation
Thank you for the excellent support and quick resolution. The Enigma Protector is working great now!

[Enigma]

I assume that this problem happen due to resources, added to the .net application, probably compressed resources.

If there are no such resources, just simple compiled file, can you please give us a sample to check? If this is common problem for every compiled .net executable, this has to be fixed.

[gto70070]

Hi Enigma,

Thank you for the clarification. Your assumption is correct.

My C# project includes a number of PNG/JPG files set as "Embedded Resource" in Visual Studio. These resources are then compiled into the final assembly. It makes perfect sense that Enigma Protector's entropy check might flag these compressed resources.

For now, the "Do not check if compressed" option is a great solution. If your team decides to refine the detection algorithm in the future and needs a minimal reproducible example, I would be happy to create and provide a simple test project with embedded images.

Best regards,

[Enigma]

That's makes sense, thank you for confirmation!