# V1.11.7 Precompilation errors (Windows)

**URL:** <https://discourse.julialang.org/t/v1-11-7-precompilation-errors-windows/132497>\
**Category:** General Usage\
**Tags:** error-message\
**Created:** [September 18, 2025, 6:21pm UTC](https://discourse.julialang.org/t/v1-11-7-precompilation-errors-windows/132497 "2025-09-18T18:21:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![braamvandyk](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/braamvandyk/32/5086_2.png) [@braamvandyk](https://discourse.julialang.org/u/braamvandyk)\
**Post date:** [September 18, 2025, 6:21pm UTC](https://discourse.julialang.org/t/v1-11-7-precompilation-errors-windows/132497/1 "2025-09-18T18:21:49Z")

</div>

I updated to Julia 1.11.7 and then ran a script to update packages in a set of projects. On two of the projects, a Windows error message popup appears: The first is for LERC\_jll while compilng Plots → UnitfulExt and the second while compiling DynamicExpressions → DynamicExpressionsSymbolicUtilsExt. The message is the same:

```julia-auto
julia.exe - Bad Image

C:\users\xxxxx\.julia\compiled\v1.11\LERC_jll\0PXNr_klCcj.dll is either not designed to run on Windows or it contains an error. Try reinstalling the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x0e90002.

```

In the second case this was for the file DispatchDoctorChainRulesCoreExt, while the first was for LERC\_jll, as indicated above.

To be honest, I’m not sure where to log this issue, but I suspect this is under the main Julia repo. Any wisdom? I don’t want to log issues in all the wrong places and this does seem to only have the compiler as a common thread, but any guidance would be appreciated.

---

<div class="post-metadata">

**Author:** ![ufechner7](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ufechner7/32/51363_2.png) [@ufechner7](https://discourse.julialang.org/u/ufechner7)\
**Post date:** [September 18, 2025, 8:59pm UTC](https://discourse.julialang.org/t/v1-11-7-precompilation-errors-windows/132497/2 "2025-09-18T20:59:23Z")

</div>

> [@braamvandyk](#):
>
> ran a script to update packages in a set of projects.

This is nothing anybody else can reproduce. Please, share a problem we can try to reproduce. For example, share the output of

```julia-auto
using Pkg
Pkg.status()

```

and then the output of

```julia-auto
Pkg.update()

```

Also useful: the output of:

```julia-auto
versioninfo()

```

---

<div class="post-metadata">

**Author:** ![nsajko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsajko/32/221187_2.png) [@nsajko](https://discourse.julialang.org/u/nsajko)\
**Post date:** [September 18, 2025, 10:19pm UTC](https://discourse.julialang.org/t/v1-11-7-precompilation-errors-windows/132497/3 "2025-09-18T22:19:03Z")

</div>

Perhaps try reinstalling v1.11.7. AFAIK there was sadly something wrong with some of the releases in the first few hours or something like that.

---

<div class="post-metadata">

**Author:** ![braamvandyk](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/braamvandyk/32/5086_2.png) [@braamvandyk](https://discourse.julialang.org/u/braamvandyk)\
**Post date:** [September 19, 2025, 3:32am UTC](https://discourse.julialang.org/t/v1-11-7-precompilation-errors-windows/132497/4 "2025-09-19T03:32:25Z")

</div>

That indeed did the job. Thanks!

---

<div class="post-metadata">

**Author:** ![braamvandyk](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/braamvandyk/32/5086_2.png) [@braamvandyk](https://discourse.julialang.org/u/braamvandyk)\
**Post date:** [October 10, 2025, 4:27pm UTC](https://discourse.julialang.org/t/v1-11-7-precompilation-errors-windows/132497/5 "2025-10-10T16:27:26Z")

</div>

For future reference, if someone else should have this problem:

The issue popped up again when updating to Julia 1.12 but has nothing directly to do with Julia. It is a Windows issue. To fix the problem on the Window side, the steps in [this article](https://www.guidingtech.com/fix-dll-not-designed-run-on-windows-error/) might be useful to others too.