Forum Discussion
Quartus did not start
For us it is currently resolved with a workaround of updating Sophos to
- 2025.2.3.32.2-MR5 core
- 2025.2.3.9.3-MR5 intercept
and also adding exclusions to the Quartus bin64 executables folder. Specifically:
- Add a Process Exclusion
- Add a File/Folder Exclusion
- Add an Exploit Mitigation Exclusion for the process and path
The form of the exception entry is also sensitive, and works with (for example)
D:\intelFPGA_pro\24.1\quartus\bin64\*.exe but not D:\intelFPGA_pro\24.1\quartus\bin64\*
Sophos has not said whether the exceptions are permanent or whether they will work to resolve the underlying false detections related to Quartus.
Hi billmax,
We tried applying this workaround to Quartus 25.3.1, but unfortunately it didn't work.
Jens
- billmax3 months ago
Occasional Contributor
The update has to be pushed to the client computer. If you're sure that's done the only thing I know to do is open your own support case with Sophos. You can reference case ID 03158718.
- KennyT_altera2 months ago
Super Contributor
Hi Jens, did you manage to open up a case with Sophos?
- Jens2 months ago
Occasional Contributor
Hello KennyT,
I can't arrange that myself. But I've checked with the system administrator.
Jens
- KennyT_altera2 months ago
Super Contributor
Do Sophos create a KDB on their side? Can help us clarify with them?