Quartus 21.1 Lite triggering Bitdefender 7.6.1.202

[Ben67]

My company enforces deployment of Bitdefender antivirus, currently at version 7.6.1.202.  I recently installed Quartus 21.1 lite edition, only to find that I cannot compile as C:\intelFPGA_lite\21.1\quartus\quartus_map and quartus_asm.exe are both being trapped in sandbox analysis.

Please coordinate with Bitdefender so your product does not falsely trigger antivirus.

[Kenny_Tan]

Hi,

Thanks for using Intel community forum,

Kindly expect some delay in the reply due to holiday.

Thanks,

[SyafieqS]

Hi Ben,

Thanks for the feedback, I will file a report internally.

As a workaround, can should allow the application in sandbox if Bitdefender.

Let me know any other concern.

[SyafieqS]

Hi Ben,

May I know if there is any update?

[Ben67]

So unlike the traditional operation of an antivirus sandbox, Bitdefender as deployed at my work place does not allow programs to run while in the sandbox.  Instead, Quartus gives an error about unexpected termination of it's child process, and between 5 and 10 minutes later Bitdefender finishes its sandbox operation and lets that particular executable run unhindered the next time (and typically stumbles into the next child process it does not like.)

For now, I am able to retarget some Max II CPLDs into Max V CPLDs.  Eventually I will need to move on to retargeting Cyclone IV FPGAs, and I assume there will be additional blocked executables for the FPGA design flow that were not triggered in the CPLD design flow.

Given that there are 117 executables in the bin64 subdirectory, I was hoping Intel would work with Bitdefender to prevent the false positive threat detection as opposed to me having to spend a day running the design flow repeatedly until all the executables get flagged as benign.

[SyafieqS]

Ben,

Understood. This might take sometime for fixes on this.

Is disabling the antivirus temporarily feasible as workaround? 

[Ben67]

Disabling the antivirus is not feasible.  Corporate IT is clear on this.  They won't even whitelist the application and its executables.

[SyafieqS]

Ben,

I am not able to reproduce the issue due to different env.

Is this issue occur to all machine?

Can you you try to other env machine?

[Ben67]

I only have the one computer.  It's been nearly a month - doen't Intel just have to send the executables causing false positive triggering to Bitdefender so they can whitelist them?

[SyafieqS]

Ben,

I will feedback this issue to our engineering. However, due to different priority on hand in engineering, the fix will take some time.