Good day,
I can't protect the final exe, even with all protection options unchecked
Always the same error:
unable to create output file
output file is already opened or it is write protected
and it is not (100% sure)
The output file has 33 files embedded
I use v3.120 full version
vs.net 2010 C# project
win 7 x64
Any help will be much appreciated.
Regards
output file is already opened
Re: output file is already opened
Hi ggpnet,
Please check the following:
1. Check if the file entered as output in Enigma Protector is not already running (run Task Manager - All Processes, check if this file is not existed there).
2. Check if output file exists on the disk, try to delete it manually from the disk before protection.
3. Run Enigma Protector with administrator privileges. Also check of the output file path does not point to write protected folder.
Please check the following:
1. Check if the file entered as output in Enigma Protector is not already running (run Task Manager - All Processes, check if this file is not existed there).
2. Check if output file exists on the disk, try to delete it manually from the disk before protection.
3. Run Enigma Protector with administrator privileges. Also check of the output file path does not point to write protected folder.
Re: output file is already opened
The problem was Bitdefender
This suite execute a real pursuit of the applications protected with Enigma. This is really annoying.
There is some workaround to solve this insane situation ?
I'd like don't lose Bitdefender money.
Regards
This suite execute a real pursuit of the applications protected with Enigma. This is really annoying.
There is some workaround to solve this insane situation ?
I'd like don't lose Bitdefender money.
Regards
Re: output file is already opened
Difficult to say how and why it prevents file from being written. While protection, Enigma Protector creates many temporary files (inside TEMP folder), BitDefender may block some of these files, or the only output one... no ideas.
Anyway, the suggestion would be to submit the sample to bit defender engineers and ask their to fix the problem.
Initially, add the file entered as output protected in the clean list of bitdefender. It will fix the problem for a while.
Then, submit the protected sample to their engineers at http://forum.bitdefender.com/index.php?showforum=138 and hope, the problem will be soon fixed for a future antivirus updates.
Anyway, the suggestion would be to submit the sample to bit defender engineers and ask their to fix the problem.
Initially, add the file entered as output protected in the clean list of bitdefender. It will fix the problem for a while.
Then, submit the protected sample to their engineers at http://forum.bitdefender.com/index.php?showforum=138 and hope, the problem will be soon fixed for a future antivirus updates.
