# Windows Defender objects to the installer

**URL:** <https://discourse.joplinapp.org/t/windows-defender-objects-to-the-installer/48320>\
**Category:** Support\
**Created:** [13 January 2026 09:44 UTC](https://discourse.joplinapp.org/t/windows-defender-objects-to-the-installer/48320 "2026-01-13T09:44:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [13 January 2026 11:52 UTC](https://discourse.joplinapp.org/t/windows-defender-objects-to-the-installer/48320/3 "2026-01-13T11:52:38Z")

</div>

This may also be because the code signing certificate was recently updated. Normally this error disappear after a few days, once Windows knows about the certificate.

Thank you for reporting it as a false positive! I assume the more such reports they get, the faster the app and certificate get whitelisted

---

_[View the full topic](https://discourse.joplinapp.org/t/windows-defender-objects-to-the-installer/48320)._
