Thank you for the added feedback; it does indeed look like an issue between the Quarantine Manager and Path Finder from what you're describing. It seems like the QM is getting the wrong files listed for the detection -- is locking them for access (which is what the QM is supposed to do) and then the actual threat is flushed from the cache, removing the detection from the QM. This is just my subjective take on the situation though; I'll see if it can be replicated, and if it can, I'll forward the issue on to the product team.
Thank you for the added feedback; it does indeed look like an issue between the Quarantine Manager and Path Finder from what you're describing. It seems like the QM is getting the wrong files listed for the detection -- is locking them for access (which is what the QM is supposed to do) and then the actual threat is flushed from the cache, removing the detection from the QM. This is just my subjective take on the situation though; I'll see if it can be replicated, and if it can, I'll forward the issue on to the product team.