06-04-2025 01:49 AM
Is anyone else seeing warning being generated on malware profiles and and their associated policies please?
For a couple of weeks, all of our Windows policies have been in a warning state. Investigating this we found that the malware profile was generating the warning due to PowerShell and VBScript detections being disabled. This includes the default policy as well.
We're currently running production in report-only to see what the impact will be,
In test, we've set both to block, and even enabled on-write and ASP\ASPX scanning in the malware profile but the warning remains in place although the profile itself is no longer displaying any warnings.
Uncomfortable with having the warnings in the UI, we have raised a call with TAC and we have a session to look at this afternoon but is anyone else seeing this\have a workaround?
06-05-2025 04:38 AM
The outcome of the TAC call was that this was also a known issue and we're expecting a fix next week.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
