I’m seeing a significant number of Windows 10/11 machines flagged for Microsoft Photos vulnerability when the ‘detected’ file doesn’t exist on the Windows machine.
For instance, this is what OpenVAS complained about:
C:\UTILS\sysinternals>psexec -h \\c4b0 cmd /c dir "C:\Program Files\WindowsApps\Microsoft.Windows.Photos*"
PsExec v2.4 - Execute processes remotely
Copyright (C) 2001-2022 Mark Russinovich
Sysinternals - www.sysinternals.com
Volume in drive C is Windows
Volume Serial Number is EE7D-CE5D
Directory of C:\Program Files\WindowsApps
03/04/2025 08:56 AM <DIR> Microsoft.Windows.Photos_2025.11020.11001.0_neutral_~_8wekyb3d8bbwe
03/04/2025 08:56 AM <DIR> Microsoft.Windows.Photos_2025.11020.11001.0_x64__8wekyb3d8bbwe
0 File(s) 0 bytes
2 Dir(s) 137,598,054,400 bytes free
cmd exited on c4b0 with error code 0.
and there this affected Microsoft.Windows.Photos_2019.19071.12548.0_neutral_split.scale-100_8wekyb3d8bbwe package is still included.
Not sure if this is works as expected / by design so have raised an internal Ticket for the team responsible for this topic but can’t give any info if / when / how this is getting handled.