Reply to thread

Message

<blockquote data-quote="rashmi" data-source="post: 1105491" data-attributes="member: 107361">My Comodo setup will obliterate this exploit, as I use &quot;block&quot; for unrecognized files and elevated prompts. <img class="smilie smilie--emoji" loading="lazy" alt="😛" title="Face with tongue&nbsp; &nbsp; :stuck_out_tongue:" src="https://cdn.jsdelivr.net/joypixels/assets/6.6/png/unicode/64/1f61b.png" data-shortname=":stuck_out_tongue:" />We have malware files interacting with the actual system, a running process, and Comodo&#039;s cmdagent in quarantine, correct? I wonder if the current Comodo certificate issue plays some part in this, as cmdagent is in quarantine.You tested on Windows 10. Possible for you to test again? You can test and just provide the outcome here; no need for video.1. Use Comodo&#039;s previous version, not 2025. I guess it has a valid certificate, right?2. If Comodo treats a VM file as unrecognized, mark it as &quot;trusted&quot; in file rating, not &quot;ignore&quot; in containment.3. Also disable the containment setting: &quot;Enable automatic startup for services installed in the container.&quot;</blockquote>

[QUOTE="rashmi, post: 1105491, member: 107361"] My Comodo setup will obliterate this exploit, as I use "block" for unrecognized files and elevated prompts. 😛 We have malware files interacting with the actual system, a running process, and Comodo's cmdagent in quarantine, correct? I wonder if the current Comodo certificate issue plays some part in this, as cmdagent is in quarantine. You tested on Windows 10. Possible for you to test again? You can test and just provide the outcome here; no need for video. 1. Use Comodo's previous version, not 2025. I guess it has a valid certificate, right? 2. If Comodo treats a VM file as unrecognized, mark it as "trusted" in file rating, not "ignore" in containment. 3. Also disable the containment setting: "Enable automatic startup for services installed in the container." [/QUOTE]

Verification