# Error launch designer in windows 7 64 bit, with JAVA 7

**URL:** <https://forum.inductiveautomation.com/t/error-launch-designer-in-windows-7-64-bit-with-java-7/6752>\
**Category:** Ignition\
**Created:** [June 23, 2013, 10:07pm UTC](https://forum.inductiveautomation.com/t/error-launch-designer-in-windows-7-64-bit-with-java-7/6752 "2013-06-23T22:07:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cesarbarqueroarce](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@cesarbarqueroarce](https://forum.inductiveautomation.com/u/cesarbarqueroarce)\
**Post date:** [June 23, 2013, 10:07pm UTC](https://forum.inductiveautomation.com/t/error-launch-designer-in-windows-7-64-bit-with-java-7/6752/1 "2013-06-23T22:07:10Z")

</div>

The error is  
JARSigningException: Could Not verify signing in resource: [localhost:8080/main/system/jar/m/lauchclient.jar](http://localhost:8080/main/system/jar/m/lauchclient.jar)

How can I fixed?

---

<div class="post-metadata">

**Author:** ![mgross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mgross/32/3311_2.png) [@mgross](https://forum.inductiveautomation.com/u/mgross)\
**Post date:** [June 24, 2013, 3:49pm UTC](https://forum.inductiveautomation.com/t/error-launch-designer-in-windows-7-64-bit-with-java-7/6752/2 "2013-06-24T15:49:52Z")

</div>

This was apparently caused by a build issue with 7.6.1, which has since been fixed in 7.6.2-rc4. The safest fix is to download 7.6.2-rc4 and run the installer to update your Ignition installation. If you are feeling more brave, you can download a file and copy it into your Ignition installation following these steps:

1. Download launchclient.jar.pack.gz from [here](http://files.inductiveautomation.com/release/7_6_1_launchclient/launchclient.jar.pack.gz)

2. Stop your Ignition Gateway

3. Navigate to /lib/core/launch and replace launchclient.jar.pack.gz with the one you just downloaded.

4. Start your Ignition Gateway. You should now be able to launch the Designer and clients from the Gateway without issues.

---

<div class="post-metadata">

**Author:** ![julienb](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@julienb](https://forum.inductiveautomation.com/u/julienb)\
**Post date:** [August 21, 2013, 4:48am UTC](https://forum.inductiveautomation.com/t/error-launch-designer-in-windows-7-64-bit-with-java-7/6752/3 "2013-08-21T04:48:50Z")

</div>

Sorry to bump this but thank you so much for this simple remedy…

Another fine example of the brilliance of this community driven support system. I spent wasted time in google searching this JARsigningexception issue without any real remedy (cache, java settings etc) and then finally tried here…

Silly me! it should have first port of call it seems, first result too!

Thanks again, much appreciated

---

<div class="post-metadata">

**Author:** ![adriancampos](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@adriancampos](https://forum.inductiveautomation.com/u/adriancampos)\
**Post date:** [November 13, 2013, 4:15pm UTC](https://forum.inductiveautomation.com/t/error-launch-designer-in-windows-7-64-bit-with-java-7/6752/4 "2013-11-13T16:15:05Z")

</div>

I downloaded the file, and replace the old one.

But still give me an error when I try to open a client from another machine.

This time:

ValidationException: Checksum mismatch for file " launchclient.jar.pack.gz". C2B470FA != A4B589D1

---

<div class="post-metadata">

**Author:** ![mgross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mgross/32/3311_2.png) [@mgross](https://forum.inductiveautomation.com/u/mgross)\
**Post date:** [November 15, 2013, 3:12pm UTC](https://forum.inductiveautomation.com/t/error-launch-designer-in-windows-7-64-bit-with-java-7/6752/5 "2013-11-15T15:12:41Z")

</div>

Maybe try clearing your local jars? Run `javaws -uninstall` from the command line and relaunch the client from the gateway. BTW, I would recommend upgrading to 7.6.3, which has a proper launchclient.jar and lots of other bugfixes.