# Aseprite error in execution

**URL:** <https://community.aseprite.org/t/aseprite-error-in-execution/19941>\
**Category:** Development\
**Created:** [September 5, 2023, 11:20am UTC](https://community.aseprite.org/t/aseprite-error-in-execution/19941 "2023-09-05T11:20:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zwktps](https://community.aseprite.org/letter_avatar/zwktps/32/6_22734026db12803ebb3e059622ac3534.png) [@zwktps](https://community.aseprite.org/u/zwktps)\
**Post date:** [September 5, 2023, 11:20am UTC](https://community.aseprite.org/t/aseprite-error-in-execution/19941/1 "2023-09-05T11:20:13Z")

</div>

Hi, when I open aseprite on windows I get that the libcrypto-1\_1-x64.dll file was not found (I also tried on different windows PCs, both win10 and win11).  
I compiled from source code and the build was successful.

---

<div class="post-metadata">

**Author:** ![dacap](https://community.aseprite.org/user_avatar/community.aseprite.org/dacap/32/10_2.png) [@dacap](https://community.aseprite.org/u/dacap)\
**Post date:** [September 5, 2023, 11:22am UTC](https://community.aseprite.org/t/aseprite-error-in-execution/19941/2 "2023-09-05T11:22:37Z")

</div>

This can only happen in a compiled version because we static-link everything (there is no .dll). You should copy all your .dll (probably from `build/lib` or `bulid/obj` to `build/bin`).

---

<div class="post-metadata">

**Author:** ![zwktps](https://community.aseprite.org/letter_avatar/zwktps/32/6_22734026db12803ebb3e059622ac3534.png) [@zwktps](https://community.aseprite.org/u/zwktps)\
**Post date:** [September 5, 2023, 2:07pm UTC](https://community.aseprite.org/t/aseprite-error-in-execution/19941/3 "2023-09-05T14:07:07Z")

</div>

Thanks for the reply, I tried to do as you say, but nothing. I’ve tried various ways, like just putting the .dll files in the `bin` or `bin/data` folder OR directly moving the “lib” folder to `bin` or `bin/data`. Any other tips to fix?  
One more thing that might help you, I use windows server 2022 to compile.

---

<div class="post-metadata">

**Author:** ![ShayBox](https://community.aseprite.org/user_avatar/community.aseprite.org/shaybox/32/18050_2.png) [@ShayBox](https://community.aseprite.org/u/ShayBox)\
**Post date:** [February 28, 2024, 1:11am UTC](https://community.aseprite.org/t/aseprite-error-in-execution/19941/4 "2024-02-28T01:11:34Z")

</div>

Why does only the proprietary build statically link? That took extra intentional steps to separate the builds, just so people building Aseprite from source would have an even harder time. I’m not surprised, it’s not even the first or tenth time changes have been made just to make it harder to build, so people are more inclined to give up and pay, but I don’t reward that kind of behavior.

---

<div class="post-metadata">

**Author:** ![zunda3](https://community.aseprite.org/user_avatar/community.aseprite.org/zunda3/32/18327_2.png) [@zunda3](https://community.aseprite.org/u/zunda3)\
**Post date:** [February 12, 2025, 4:58pm UTC](https://community.aseprite.org/t/aseprite-error-in-execution/19941/5 "2025-02-12T16:58:14Z")

</div>

Hi, I’m in a similar situation.  
I stored the libcrypto-1\_1-x64.dll in the same folder as Aseprite.exe,  
then Aseprite started without error.

But this libcrypto-1\_1-x64.dll was copied by what I found when I happened to search my PC.

 ![スクリーンショット 2025-02-13 014722](https://community.aseprite.org/uploads/default/original/3X/4/6/461ce65e332f8bfde545ad786af05f6d5af2f366.png)

Anyway, this solution can be execute Aseprite.exe.  
However, I’m skeptical if this method is really correct.