https://bugs.kde.org/show_bug.cgi?id=521262
--- Comment #6 from George Koulomzin <[email protected]> --- Again, per Gemini (FWIW): How Developers Fix False Positives Tom's Hardware Because end-users cannot locally override a SAC block, the burden of fixing the rejection falls entirely on the software developer. They have three paths to get their files recognized as safe: 1. *Manual Submission:* Developers can submit the rejected files directly to the *Microsoft Security Intelligence portal*. Microsoft's security analysts will manually review the binaries. If deemed safe, Microsoft forces a manual override in the Intelligent Security Graph, instantly updating the file's global cloud reputation to "clean." 2. *Comprehensive Signing:* The developer must audit their build pipeline to ensure every single |.exe|, |.dll|, installer, and script is cryptographically signed with a trusted CA before distribution. 3. *Microsoft Store Distribution:*Applications published through the Microsoft Store are automatically re-signed by Microsoft's own certificate. SAC completely ignores its standard checks for Store apps and grants them automatic, immediate trust. Microsoft Learn If Digikam 9.1 triggered this error on your machine, it is highly probable that the Digikam developers updated or added a new third-party |.dll| for version 9.1, but failed to digitally sign it. Because the update is new, the file hash hasn't accumulated enough global telemetry to earn a safe cloud reputation, causing SAC to block it. I will wait a couple of days. If still not recognized, I will revert to 9.0. George On 6/9/2026 1:50 PM, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=521262 > > Maik Qualmann<[email protected]> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |[email protected] > > --- Comment #4 from Maik Qualmann<[email protected]> --- > It is recommended to disable Smart Application Control in Windows 11 if you > encounter this error message. The issue can occur with unsigned or corrupted > files. It is possible that the current digiKam package is not yet "recognized" > by Microsoft and is therefore being blocked. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
