Forum Discussion

Jens's avatar
Jens
Icon for Occasional Contributor rankOccasional Contributor
4 months ago

Quartus did not start

Hi, Since the switch to European Summer Time we cannot start Quartus Prime 2025 in Windows 11. Error Message: The application could not be started correctly (0xc0000142) What could be the reason ...
general
Jens's avatar
Jens
Icon for Occasional Contributor rankOccasional Contributor
4 months ago

It seems Sophos isn't the problem. Our administrator has partially disabled Sophos's access and Quartus didn't start.

We have followed the debugging steps suggested by KennyT and the process monitor is showing numerous issues with “NAME NOT FOUND”.

  • syoma's avatar
    syoma
    Icon for New Contributor rankNew Contributor
    4 months ago

    Hi Jens

    We have just tested with Sophos Endpoint Agent settings and this is actually it. If you use Override Sophos Central Policy for up to 4 hours to troubleshoot and uncheck Malicious Behavior Detection ("Erkennung von schädlichem Verhalten") option in Runtime Protection - then Quartus is starting normally. So we are pretty sure it has something to do with it. 

    Could you please check on your side this again?

    • KennyT_altera's avatar
      KennyT_altera
      Icon for Super Contributor rankSuper Contributor
      4 months ago

      Thank you for your feedback, we will also investigate this and get back to you. 

    • Jens's avatar
      Jens
      Icon for Occasional Contributor rankOccasional Contributor
      4 months ago

      Hi syoma,

      I asked our IT department to disable the Sophos “detect malicious behavior” feature.

      After that, Quartus started up.
      However, for security reasons, this isn't a long-term solution for us.

      Can Altera provide a bug fix for this?

      Jens

      • syoma's avatar
        syoma
        Icon for New Contributor rankNew Contributor
        4 months ago

        Yes, we also disabled “detect malicious behavior” feature for 2 weeks to be able to work, as we were unable to make folder based exception (it seems that Quartus accesses something in windows system folders) and this will also not work for installer, so someone needs to check why Sophos blocks Quartus Software starting from 24 and newest installer. Unfortunately Sophos Logs showing no hints.