Warning on malware profile being set to report only

Karl-Foley — Wed, 04 Jun 2025 08:49:36 GMT

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?

Re: Warning on malware profile being set to report only

Karl-Foley — Thu, 05 Jun 2025 11:38:33 GMT

The outcome of the TAC call was that this was also a known issue and we're expecting a fix next week.

Re: Warning on malware profile being set to report only

N.Nadhirah — Wed, 16 Jul 2025 07:43:10 GMT

Hi, we're experiencing a similar issue with the malware profile. Are there any updates on this problem? Has Palo Alto released a fix yet?

topic Re: Warning on malware profile being set to report only in Cortex XDR Discussions

Warning on malware profile being set to report only

Re: Warning on malware profile being set to report only

Re: Warning on malware profile being set to report only