# Error: Update installation was blocked, digital signature mismatch. Please contact technical support

**URL:** <https://forum.fxsound.com/t/error-update-installation-was-blocked-digital-signature-mismatch-please-contact-technical-support/6804>\
**Category:** General Discussion\
**Tags:** verified-bug\
**Created:** [August 19, 2026, 12:27pm UTC](https://forum.fxsound.com/t/error-update-installation-was-blocked-digital-signature-mismatch-please-contact-technical-support/6804 "2026-08-19T12:27:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![thunder](https://avatars.discourse-cdn.com/v4/letter/t/a8b319/32.png) [@thunder](https://forum.fxsound.com/u/thunder)\
**Post date:** [August 19, 2026, 12:27pm UTC](https://forum.fxsound.com/t/error-update-installation-was-blocked-digital-signature-mismatch-please-contact-technical-support/6804/1 "2026-08-19T12:27:16Z")

</div>

The last update of 74.36MB 2026-08-19 failed with signature mismatch.

DoesFxSound is subject to a viral hack into his own source control ?

---

<div class="post-metadata">

**Author:** ![myFxSound](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/myfxsound/32/2375_2.png) [@myFxSound](https://forum.fxsound.com/u/myFxSound)\
**Post date:** [August 19, 2026, 3:05pm UTC](https://forum.fxsound.com/t/error-update-installation-was-blocked-digital-signature-mismatch-please-contact-technical-support/6804/2 "2026-08-19T15:05:13Z")

</div>

Yeah I just had that earlier too…

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [August 19, 2026, 3:24pm UTC](https://forum.fxsound.com/t/error-update-installation-was-blocked-digital-signature-mismatch-please-contact-technical-support/6804/3 "2026-08-19T15:24:54Z")

</div>

From v1.2.11.0 we are signing the build with a new certificate.

Due to Organisation Validation reuse period change, we had to go through the validation process and get a new certificate instead of renewing the certificate.

This could be the reason for update unable to match the digital signature.

You can uninstall and install the new version instead of updating.

[Shortening domain and OV - organization validation reuse periods](https://docs.digicert.com/en/certcentral/perform-domain-control-validation--dcv-/domain-validation-requirements-and-reuse-periods/shortening-domain-and-ov-organization-validation-reuse-periods.html)

---

<div class="post-metadata">

**Author:** ![thunder](https://avatars.discourse-cdn.com/v4/letter/t/a8b319/32.png) [@thunder](https://forum.fxsound.com/u/thunder)\
**Post date:** [August 19, 2026, 3:53pm UTC](https://forum.fxsound.com/t/error-update-installation-was-blocked-digital-signature-mismatch-please-contact-technical-support/6804/4 "2026-08-19T15:53:15Z")

</div>

This sound like a grace period for owner of domain like [fxsound.com](http://fxsound.com). If you miss the grace period your old certificate could be bought by a third party and I and you will loose all past version confidentiality. I would call digicert to ask them If your old certificate number are unique to your old organisation.

Have a nice day  
Database Admin Canadian Army

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [August 19, 2026, 6:16pm UTC](https://forum.fxsound.com/t/error-update-installation-was-blocked-digital-signature-mismatch-please-contact-technical-support/6804/5 "2026-08-19T18:16:53Z")

</div>

Certificate cannot be simply issued to anyone without authenticating their identity through proofs about the organization through organization validation.

You seem to have misunderstood the domain reservation with code signing certificate.