<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Microsoft Photos.exe in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/microsoft-photos-exe/m-p/1247534#M9101</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/286656921"&gt;@J.Indoc&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, this is a known behavior where the legitimate &lt;STRONG&gt;Microsoft Photos.exe&lt;/STRONG&gt; process triggers &lt;STRONG&gt;“Suspicious File Modification”&lt;/STRONG&gt; alerts within the &lt;STRONG&gt;Anti-Ransomware Protection&lt;/STRONG&gt; module. These alerts are typically false positives caused by the application interacting with &lt;STRONG&gt;decoy files&lt;/STRONG&gt; created by the Cortex XDR agent.&lt;/P&gt;
&lt;HR /&gt;
&lt;H4&gt;Root Cause Analysis&lt;/H4&gt;
&lt;H5&gt;Decoy (Honeypot) Files&lt;/H5&gt;
&lt;P&gt;The Anti-Ransomware module places hidden decoy files (often starting with &lt;CODE&gt;ZZZZZ&lt;/CODE&gt; or &lt;CODE&gt;!!!!!&lt;/CODE&gt;) in various directories to detect encryption attempts.&lt;/P&gt;
&lt;H5&gt;Application Behavior&lt;/H5&gt;
&lt;P&gt;Applications like the Windows Photos app often scan, index, or perform cleanup operations on directories where these decoys reside. When &lt;STRONG&gt;Photos.exe&lt;/STRONG&gt; modifies or even enumerates these protected files, the agent may interpret this behavior as potential ransomware activity and generate an alert.&lt;/P&gt;
&lt;H5&gt;Aggressive Mode&lt;/H5&gt;
&lt;P&gt;These alerts are most frequent when the Ransomware Protection module is set to &lt;STRONG&gt;Aggressive&lt;/STRONG&gt; mode. In this mode, the agent places more decoy files in user-accessible locations, increasing the likelihood that benign applications will interact with them.&lt;/P&gt;
&lt;HR /&gt;
&lt;H4&gt;Recommended Resolutions&lt;/H4&gt;
&lt;H5&gt;1. Revert to Normal Protection Mode (Standard Fix)&lt;/H5&gt;
&lt;P&gt;The most common way to resolve these false positives is to change the protection mode from &lt;STRONG&gt;Aggressive&lt;/STRONG&gt; to &lt;STRONG&gt;Normal&lt;/STRONG&gt; in the Malware Security Profile. Normal mode maintains strong protection while reducing exposure of decoy files to benign processes.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Steps:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Navigate to &lt;STRONG&gt;Endpoints → Policy Management → Prevention → Profiles&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Edit the &lt;STRONG&gt;Malware Security Profile&lt;/STRONG&gt; assigned to the affected endpoints&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Locate the &lt;STRONG&gt;Anti-Ransomware Protection&lt;/STRONG&gt; section&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Change &lt;STRONG&gt;Protection Mode&lt;/STRONG&gt; from &lt;EM&gt;Aggressive&lt;/EM&gt; to &lt;EM&gt;Normal&lt;/EM&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Save the profile and ensure it is applied to the relevant policy rules&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H5&gt;2. Create a Process Exception&lt;/H5&gt;
&lt;P&gt;If &lt;STRONG&gt;Aggressive&lt;/STRONG&gt; mode must remain enabled, you can create a targeted exception for &lt;STRONG&gt;Photos.exe&lt;/STRONG&gt; to prevent it from being monitored by the Anti-Ransomware module.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Steps:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Go to &lt;STRONG&gt;Settings → Exception Configurations → Legacy Agent Exceptions&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Click &lt;STRONG&gt;+ Add Rule&lt;/STRONG&gt; and select the appropriate platform (Windows)&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Select &lt;STRONG&gt;Process Exceptions&lt;/STRONG&gt; as the module type&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;In &lt;STRONG&gt;Target Properties&lt;/STRONG&gt;, enter the process name: &lt;CODE&gt;photos.exe&lt;/CODE&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;In &lt;STRONG&gt;Module Name&lt;/STRONG&gt;, select &lt;STRONG&gt;Anti-Ransomware Protection&lt;/STRONG&gt; and add it&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Define the scope (Global or specific Profiles) and click &lt;STRONG&gt;Create&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR /&gt;
&lt;H5&gt;3. Hash Exception&lt;/H5&gt;
&lt;P&gt;Alternatively, you can add the specific file hash of the legitimate &lt;STRONG&gt;Photos.exe&lt;/STRONG&gt; binary to the &lt;STRONG&gt;Allow List (Hash Exceptions)&lt;/STRONG&gt;. This approach is useful if the behavior is isolated to a specific version of the executable.&lt;/P&gt;
&lt;HR /&gt;
&lt;H4&gt;Verification&lt;/H4&gt;
&lt;P&gt;You can confirm that the alert was triggered by decoy file interaction by reviewing the alert data dump. Indicators typically include file paths similar to:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;CODE&gt;C:\ProgramData\Cyvera\Ransomware\...\ZZZZZ.doc&lt;/CODE&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;CODE&gt;C:\Users\&amp;lt;user&amp;gt;\Pictures\!!!!!.jpg&lt;/CODE&gt;&lt;CODE&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;&lt;BR /&gt;&lt;/CODE&gt;If you feel this has answered your query, please let us know by clicking like and on&amp;nbsp;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Thu, 05 Feb 2026 16:19:00 GMT</pubDate>
    <dc:creator>susekar</dc:creator>
    <dc:date>2026-02-05T16:19:00Z</dc:date>
    <item>
      <title>Microsoft Photos.exe</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/microsoft-photos-exe/m-p/1247459#M9097</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Does anyone experience receiving alerts from photos.exe due to "Suspicious File Modification" and the Module is "Anti-Ransomware Protection" even the program is legitimate?&lt;BR /&gt;Other factors I'm seeing is due to possibly outdated version of the said program. *See attached reference photo*&lt;BR /&gt;&lt;BR /&gt;I'm hoping from anyone's advice from other members with the same experience on how you handle this issue and some pointers on how to resolve it.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Cheers!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 15:55:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/microsoft-photos-exe/m-p/1247459#M9097</guid>
      <dc:creator>J.Indoc</dc:creator>
      <dc:date>2026-02-05T15:55:56Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft Photos.exe</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/microsoft-photos-exe/m-p/1247534#M9101</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/286656921"&gt;@J.Indoc&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, this is a known behavior where the legitimate &lt;STRONG&gt;Microsoft Photos.exe&lt;/STRONG&gt; process triggers &lt;STRONG&gt;“Suspicious File Modification”&lt;/STRONG&gt; alerts within the &lt;STRONG&gt;Anti-Ransomware Protection&lt;/STRONG&gt; module. These alerts are typically false positives caused by the application interacting with &lt;STRONG&gt;decoy files&lt;/STRONG&gt; created by the Cortex XDR agent.&lt;/P&gt;
&lt;HR /&gt;
&lt;H4&gt;Root Cause Analysis&lt;/H4&gt;
&lt;H5&gt;Decoy (Honeypot) Files&lt;/H5&gt;
&lt;P&gt;The Anti-Ransomware module places hidden decoy files (often starting with &lt;CODE&gt;ZZZZZ&lt;/CODE&gt; or &lt;CODE&gt;!!!!!&lt;/CODE&gt;) in various directories to detect encryption attempts.&lt;/P&gt;
&lt;H5&gt;Application Behavior&lt;/H5&gt;
&lt;P&gt;Applications like the Windows Photos app often scan, index, or perform cleanup operations on directories where these decoys reside. When &lt;STRONG&gt;Photos.exe&lt;/STRONG&gt; modifies or even enumerates these protected files, the agent may interpret this behavior as potential ransomware activity and generate an alert.&lt;/P&gt;
&lt;H5&gt;Aggressive Mode&lt;/H5&gt;
&lt;P&gt;These alerts are most frequent when the Ransomware Protection module is set to &lt;STRONG&gt;Aggressive&lt;/STRONG&gt; mode. In this mode, the agent places more decoy files in user-accessible locations, increasing the likelihood that benign applications will interact with them.&lt;/P&gt;
&lt;HR /&gt;
&lt;H4&gt;Recommended Resolutions&lt;/H4&gt;
&lt;H5&gt;1. Revert to Normal Protection Mode (Standard Fix)&lt;/H5&gt;
&lt;P&gt;The most common way to resolve these false positives is to change the protection mode from &lt;STRONG&gt;Aggressive&lt;/STRONG&gt; to &lt;STRONG&gt;Normal&lt;/STRONG&gt; in the Malware Security Profile. Normal mode maintains strong protection while reducing exposure of decoy files to benign processes.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Steps:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Navigate to &lt;STRONG&gt;Endpoints → Policy Management → Prevention → Profiles&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Edit the &lt;STRONG&gt;Malware Security Profile&lt;/STRONG&gt; assigned to the affected endpoints&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Locate the &lt;STRONG&gt;Anti-Ransomware Protection&lt;/STRONG&gt; section&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Change &lt;STRONG&gt;Protection Mode&lt;/STRONG&gt; from &lt;EM&gt;Aggressive&lt;/EM&gt; to &lt;EM&gt;Normal&lt;/EM&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Save the profile and ensure it is applied to the relevant policy rules&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H5&gt;2. Create a Process Exception&lt;/H5&gt;
&lt;P&gt;If &lt;STRONG&gt;Aggressive&lt;/STRONG&gt; mode must remain enabled, you can create a targeted exception for &lt;STRONG&gt;Photos.exe&lt;/STRONG&gt; to prevent it from being monitored by the Anti-Ransomware module.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Steps:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Go to &lt;STRONG&gt;Settings → Exception Configurations → Legacy Agent Exceptions&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Click &lt;STRONG&gt;+ Add Rule&lt;/STRONG&gt; and select the appropriate platform (Windows)&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Select &lt;STRONG&gt;Process Exceptions&lt;/STRONG&gt; as the module type&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;In &lt;STRONG&gt;Target Properties&lt;/STRONG&gt;, enter the process name: &lt;CODE&gt;photos.exe&lt;/CODE&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;In &lt;STRONG&gt;Module Name&lt;/STRONG&gt;, select &lt;STRONG&gt;Anti-Ransomware Protection&lt;/STRONG&gt; and add it&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Define the scope (Global or specific Profiles) and click &lt;STRONG&gt;Create&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR /&gt;
&lt;H5&gt;3. Hash Exception&lt;/H5&gt;
&lt;P&gt;Alternatively, you can add the specific file hash of the legitimate &lt;STRONG&gt;Photos.exe&lt;/STRONG&gt; binary to the &lt;STRONG&gt;Allow List (Hash Exceptions)&lt;/STRONG&gt;. This approach is useful if the behavior is isolated to a specific version of the executable.&lt;/P&gt;
&lt;HR /&gt;
&lt;H4&gt;Verification&lt;/H4&gt;
&lt;P&gt;You can confirm that the alert was triggered by decoy file interaction by reviewing the alert data dump. Indicators typically include file paths similar to:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;CODE&gt;C:\ProgramData\Cyvera\Ransomware\...\ZZZZZ.doc&lt;/CODE&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;CODE&gt;C:\Users\&amp;lt;user&amp;gt;\Pictures\!!!!!.jpg&lt;/CODE&gt;&lt;CODE&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;&lt;BR /&gt;&lt;/CODE&gt;If you feel this has answered your query, please let us know by clicking like and on&amp;nbsp;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;
&lt;P&gt;&lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Thu, 05 Feb 2026 16:19:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/microsoft-photos-exe/m-p/1247534#M9101</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-02-05T16:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft Photos.exe</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/microsoft-photos-exe/m-p/1247744#M9105</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/241098"&gt;@susekar&lt;/a&gt;,&lt;BR /&gt;Thank you for your insights in my concern. All recommended methods are all working.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Feb 2026 16:59:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/microsoft-photos-exe/m-p/1247744#M9105</guid>
      <dc:creator>J.Indoc</dc:creator>
      <dc:date>2026-02-09T16:59:06Z</dc:date>
    </item>
  </channel>
</rss>

