# \[BUG-9263\] Designer Launcher Fails to Launch

**URL:** <https://forum.inductiveautomation.com/t/bug-9263-designer-launcher-fails-to-launch/85605>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 13, 2024, 3:35am UTC](https://forum.inductiveautomation.com/t/bug-9263-designer-launcher-fails-to-launch/85605 "2024-02-13T03:35:58Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [May 3, 2024, 1:03pm UTC](https://forum.inductiveautomation.com/t/bug-9263-designer-launcher-fails-to-launch/85605/28 "2024-05-03T13:03:53Z")

</div>

This thread is about a different issue than you are having.

Looks more like these:

> [@How to turn off certification revocation check in Ignition 8.1.37?](https://forum.inductiveautomation.com/t/how-to-turn-off-certification-revocation-check-in-ignition-8-1-37/86440):
>
> Since I updated from Ignition 8.1.32 to 8.1.37, when I launch the applications from Vision Client Launcher, the following error window appears: "Launch client jar Invalid. This launch client jar signature is invalid. Contact an administrator" In visionclientlauncher.log, the following trace is seen: ERROR [LaunchClientJarService] [2024/02/27 12:35:57]: Launch client jar Invalid java.security.cert.CertPathValidatorException: Unable to determine revocation status due to network error …

> [@Designer startup : Verifying Signature of Designer](https://forum.inductiveautomation.com/t/designer-startup-verifying-signature-of-designer/82670/9):
>
> I understand the slight delay can be frustrating, but this provides a robust industry-standard way to verify the authenticity of jars downloaded over the internet. the soft-fail mechanism is the default we use specifically because most launch cases are on networks without internet access. The "strict" mode would actually require a connection to one of the revocation endpoints ([ocsp.digicert.com](http://ocsp.digicert.com) or [cacerts.digicert.com](http://cacerts.digicert.com)) which is why its not the default (but can be turned on in the launchers' conf…

Which have to do with network access blocking the revocation checks.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-9263-designer-launcher-fails-to-launch/85605)._
