# Error launching Designer remotely with error java.nio.file.FileAlreadyExistsException **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [November 7, 2020, 1:07pm UTC](https://forum.inductiveautomation.com/t/error-launching-designer-remotely-with-error-java-nio-file-filealreadyexistsexception/40410 "2020-11-07T13:07:07Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\ **Post date:** [November 8, 2020, 12:15am UTC](https://forum.inductiveautomation.com/t/error-launching-designer-remotely-with-error-java-nio-file-filealreadyexistsexception/40410/2 "2020-11-08T00:15:46Z")
See these threads: > [@\[BUG-YT-336\] Exception launching designer](http://forum.inductiveautomation.com/t/bug-yt-336-exception-launching-designer/38139/5): > > I think we can change jre-win folder name to 11.0.7 to solve this problem. [image] > [@Unable to launch designer after updating to 8.0.16](http://forum.inductiveautomation.com/t/unable-to-launch-designer-after-updating-to-8-0-16/38805/15): > > @framebuilder Deleting the jre-win dir if it exists before launching a client would help if there is a prior failure. The JRE is only dowloaded once per version so after it succeeds there should be no issue from there on out so simply launching a client or designer on a machine should allow you to get a cached runtime (assuming you don’t hit this issue, which the previously mentioned workaround should fix) It should also be noted that a fix for this is currently submitted for testing and shoul… --- _[View the full topic](https://forum.inductiveautomation.com/t/error-launching-designer-remotely-with-error-java-nio-file-filealreadyexistsexception/40410)._