Too late
Never been done before so the likely harm is very low - just a few additional write cycles, but at least it is another elimination of possible causes box ticked.
Nope: CHKDSK, clear space on drive (now 40% empty), Defrag, same result on a clean install:
Faulting application name: ART.exe, version: 0.0.0.0, time stamp: 0x63c578ed
Faulting module name: libwinpthread-1.dll, version: 1.0.0.0, time stamp: 0x634b0014
Exception code: 0xc0000005
Fault offset: 0x0000000000002cc8
Faulting process id: 0x1040
Faulting application start time: 0x01d92c115f70b4b9
Faulting application path: C:\Program Files\ART\1.18.1\ART.exe
Faulting module path: C:\Program Files\ART\1.18.1\libwinpthread-1.dll
Report Id: 4b791e55-8bdb-4e66-9f53-a930a4cfe54b
Faulting package full name:
Faulting package-relative application ID:
Windows 10 Home, Version|10.0.19044 Build 19044|
Hi Alberto
Latest versions still don’t run on my WIndows system, I’m stuck on version 1.18.0, the last version which will run. Is there a debug/logging build I can drop into the latest version to see what happens when I try to run Art? At the moment it just fails to launch - nothing appears. I don’t want to be left by the wayside at v 1.18.0 ![]()
Many thanks
Barry
Hi,
I’m afraid the best thing to do would be to try and build it yourself. Installing the needed dependencies is a bit tedious, but you should be able to follow the procedure as documented in rawpedia (but you need to additionally install exiv2 and the latest version of libraw)
HTH
You could look at gaaneds builds:
https://drive.google.com/drive/folders/1PiiTzfY1uSD8nV3bzgKDAR4o2aVZUJMS
They ship with gdb.
Thanks Alberto but my dev days are waay behind me, I’m just a user now ![]()
Interesting, this runs perfectly
I thank you. Does anyone know any difference in the builds which might cause one to fail and the other run?
From the technical point of view you can see the build settings and their differences in the respective AboutThisBuild.txt. But as I’m just an end user, this stuff won’t tell my anything. Maybe Alberto can narrow something down with this info. At least you can have some fun in ART again.
Glad that the problem is solved!
I don’t know what might be the problem, but I’ll try to investigate. I’m not very familiar with windows though so I might not be able to sort this out…
It seems to be something to do with 1.19.x being in a folder alongside older versions…
- ART
--Art 1.17.0 etc << runs
--Art 1.18.0 << runs
--Art 1.19.x << doesn't run
But I renamed all that as OLD, put gaaned’s build into \ART and it runs fine. I’ll see if I can narrow it down further, but yes, I am now back up to the current release ![]()
Happy Easter ![]()
Barry
So you are installing without uninstalling previous versions, and all in the same folder?
Folder called Art, in which there are folders for each version, 1.xx.x etc. Handy for rolling back to a previous version. Worked perfectly until 1.18.1.
Ok, I must admit I never tested with multiple installed versions in parallel on windows, although I can’t think of a reason why it shouldn’t work…
Have you ever tried using a clean AppData\ART folder? I suspect all official builds will use the same ART and gaaned’s builds probably create their own ART-dev folder.
That’s indeed a good suggestion
I use multiple versions of ART in following directory structure in Windows, but no launching problem was found so far.

I think writing new version over old version may cause Dll conflicts…