# New version "Julia v1.10.3 has been released" and #52272 not fixed?

**URL:** <https://discourse.julialang.org/t/new-version-julia-v1-10-3-has-been-released-and-52272-not-fixed/113668>\
**Category:** General Usage\
**Created:** [April 30, 2024, 7:07pm UTC](https://discourse.julialang.org/t/new-version-julia-v1-10-3-has-been-released-and-52272-not-fixed/113668 "2024-04-30T19:07:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [April 30, 2024, 7:07pm UTC](https://discourse.julialang.org/t/new-version-julia-v1-10-3-has-been-released-and-52272-not-fixed/113668/1 "2024-04-30T19:07:48Z")

</div>

It is a serious bug for some Windows users.

> <https://github.com/JuliaLang/julia/issues/52272>
>
> This is a somewhat speculative issue without a reproducer - I'm filing this as I…'ve run into this a few times now and have had sporadic interactions with people on Discourse/Slack seeing this as well, so hopefully this consolidates things by giving those who experience this issue something to search for. 
> 
> What prompted me to file today was seeing this in one of my environments:
> 
> \`\`\`
> 64 dependencies successfully precompiled in 360 seconds. 266 already precompiled.
> 1 dependency had output during precompilation:
> ┌ GR
> │ ERROR: LoadError: InitError: could not load library "C:\\Users\\ngudat\\.julia\\artifacts\\52bbefbea6a9098fa5c57208812d3868fac90841\\bin\\libxml2-2.dll"
> │ Access is denied.
> │ Stacktrace:
> │ \[1\] dlopen(s::String, flags::UInt32; throw\_error::Bool)
> │ @ Base.Libc.Libdl .\\libdl.jl:117
> \`\`\`
> 
> I had previously posted on Discourse about this here:
> 
> https://discourse.julialang.org/t/windows-artifact-issue-access-denied-when-installing-plots-makie/103734/4
> 
> with others chiming in reporting the same issue. There's also an issue reported with Yggdrasil here:
> 
> https://github.com/JuliaPackaging/Yggdrasil/issues/7625
> 
> All of this is a bit of a throwback to this old issue from 1.5 days:
> 
> https://github.com/JuliaLang/julia/issues/38411
> 
> (and again with what I've seen on 1.10 again starting Julia as admin was fine, but then required to always run as admin when wanting to use any packages loading artifacts).
> 
> If anything changed in how artifacts get handled on Windows it might be worth looking into. Equally if no one else chimes in here reporting any issues I might just be seeing a hangover effect from artifacts installed earlier and the problem is solved on rc1 already.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [April 30, 2024, 7:49pm UTC](https://discourse.julialang.org/t/new-version-julia-v1-10-3-has-been-released-and-52272-not-fixed/113668/2 "2024-04-30T19:49:24Z")

</div>

Patch versions get released with the fixes that are available. That issue isn’t fixed, nor is it entirely clear to me what the appropriate fix is, nor even what the root problem is. If you have thoughts on what should be done, feel free to chime in. It’s the usual thing where it’s a Windows-specific problem and there’s not that much technical help coming from any Windows users…