@nwchong I assume that you are using ENS and if that is the cause I would like you to set exclusions for that particular application. Check if the policy is set correctly for the PUP.
On the other hand, I would like you to submit the sample to McAfee and obtain a negative extra DAT.
I would also like you to go through the KB article KB88482#OAS
yes, I am using ENS and we have set the policy at EPO to restrict most of the Windows default App. I don't want them to use the Windows App.
My question is why we did not access or open the App, the On-Access Scan still will prompt it detected ?
Second question is after ENS detected yesterday, why it still detect it today again ?
@nwchong Can you please ensure that proper exclusions are set for that particular Windows Application, if not I would recommend you to set exclusions for the Windows App related process and if required exclude the path as well.
In regards to: "My question is why we did not access the App and yet it still prompt detected a threat at On-Access Scan?"
Something on the system will have triggered a read/ write activity on the app causing it to be picked up by OAS.
@nwchong As mentioned by @Former Member unless there is no trigger during I/O read write operations there will not be any issue.
I would suggest you to see if you have set any exclusions to that particular application, if so what sort of exclusion that you have added.
My personal suggestion would be to add the application related process to low risk so that you can un-check the scan during read write options. Also I would like you to exclude the complete path of the application.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: