You are here

how to fix libgdk-win32-2.0-0.dll missing error when trying to run UF raw

Thank you for your help! I have GIMP 2.6.2. and am attempting to use UF raw to open and edit RAW photos. I downloaded UF Raw from 2 different places, and both have resulted with the libgdk-win32-2.0-0.dll missing error message. I've uninstalled and re-installed. Is there a plug-in I need, if so, where can I find it? I read somewhere about creating a path, but I think there is a simpler solution. Thank you!!!


to see if you have that dll file.
You say you use 2.6.2. Try updating to Gimp-2.6.12 so you have that dll file then install ufraw again.


I'm not sure if ya'll prefer we make new threads for duplicate issues. But, in attempt to limit clutter, Ill post here.

I em experiencing the exact same issue as op.

I have Win7 x64 running Gimp 2.8.0 and I'm trying to install UFRaw-0.18.

It installs fine, but when I go to execute it I get the libgdk-win32-2.0-0.dll missing error.

I only have one copy of this dll and its inside Gimp's bin folder.

I've attempted re-installations of UFRaw and Gimp to no avail.

Any thoughts on what could be causing this?

folks are not seeing the "customize" button in gimp-2.8 installer to be able to make older plugins compatible.
UFRAW is an older plugin.
I believe this allows the installer to install the correct dynamic link library when you install the program.

On another note, the Windows 7 platform seems to be the one with most of the dll problems.

Have any of you tried to reinstall using customize and check the older plugin compatibility option?


I honestly hadn't seen the customize button before.

I have attempted re-installation with through the customize button but still no luck.

I also made sure afterward that there was only one copy of the libgdk-win32-2.0-0.dll present in the bin folder. There are no copies present in System nor System 32.

I get this error too when I install GIMP 2.8.0 and then UFraw 0.18. With GIMP 2.6.11 installed, UFraw 0.18 installs and runs fine. This is on Win 7 64-bit.

I see that GIMP 2.8.0 installs in C:\Program Files\GIMP 2, and then UFraw installs in C:\Program Files (x86)\UFRaw. In other words, GIMP is installing in the 64-bit Program Files, and UFraw is installing in the 32-bit. This would seem to violate the requirement noted in one of the UFraw install windows that says "UFRaw should be installed in the GIMP directory. Hopefully the wizard will guess your GIMP directory correctly." Well, it appears the wizard is NOT guessing correctly.

It looks like GIMP 2.8.0 has broken the UFraw 0.18 install.

Here is what you do:

(These instructions are assuming GIMP 2.8.0 is already installed.)
1.) Install UFRaw. (I installed it to C:\Program Files not the x86, I don't know if this makes a difference.)
2.) Go to C:\Program Files\UFRaw
3.) Copy all the files and folders there. (bin, lib, share, unins000.dat, unins000)
4.) Go to C:Program Files\GIMP 2
5.) Paste the files you copied from UFRaw. When it asks you if you want to merge, say yes. When it asks you to copy or replace a file say no. Just say don't copy or replace, leave the file it's trying to overwrite alone.

You're done, the plugin is installed in GIMP 2.8.0.
You can't open the program as a standalone. You must open GIMP and select File->Open and then open a RAW file. It will automatically open it in UFRaw.

I have the following setup. GIMP 2.8.0 + UFRaw 0.18. In order to make UFRaw work independently copy all the DLLs from GIMP 2\bin folder to the UFRaw\bin folder. Try not to replace any existing DLL in UFRaw\bin only copy the additional files.

This will let you open UFRaw Standalone

Weird as may sound often the message about missing dll is not caused by a missed dll but by more then 1 copies of the same dll

that is very frequent so before try to install /reinstall etc make a search (in gimp and in the place where Windows hide dll, "System" and System 32 and if you found clones delete the clone(s)


I also had this problem on the 32 bit version of Windows 7.

I solved that with this definitly dirty solution, but it worked: Just copied all the .dll files from the "C:\Program Files\GIMP 2\bin" directory to the "C:\Program Files\UFRaw\bin" directory, and didn't overwrote anything.

UFRaw worked, but could not send the files to gimp from the program, neither GIMP was able to open raw files.

Will try later to install GIMP to a directory with the same name as the one created with GIMP 2.6 (C:\Program Files\GIMP 2.0\) and change the command on the configuration of UFRaw, according to this post on UFRaw help.

Did not try yet this lengthy version of the instalation, if someone try in Win7, please post it here.

Will post my experience later.

And if someone can make it work, please post it here too...

did you get it figured out with windows seven with a win 32bit? I am still trying to get it to work, I got it to work, but then it didn't want to save it right, also it didn't want to open up in gimp. I got the photos to open in Gimp but they were really tiny. :( Please help if you were able to figure it out..

I remember that was a bit tricky to set it up correctly but no much the details

If may help you may found pre-installed on Partha portable 32bit build ( on Samj ( )and on mine ( file on more info )

I would like help more then just say installation was a "bit tricky" but honestly i don't remember more except that i have to try twice to set it up correctly.

That was also one of the reason why i preinstalled on my customized version, the other was that in my vision a graphic editor focused on photo edit and manipulation MUST be able to open photo from camera( at least from most camera) out of the box.

Tried about everything in this thread, but.....

Try to open ufraw standalone I get "the application was unable to start correctly (0xc000007b)" If I try to open the RAW file from Gimp I get a bucn of TIFF errors.

and to no avail.. not working for me.. I have duplicate folders.. in each program files. The Reg one and The (x86) one, Should I delete these duplicate folders... And How can I tell what folder I installed gimp 2.8 in?

see my reply to your question here

I don't think anyone here is trying to boost his own ego. by answering questions, especially considering that one takes the risk to be proved wrong if he isn't completely right. Not even mentioning that statistically there is only one chance out of three to get any kind of feedback on the answer.

So, step in the shoes of those who answer... there is usually not enough information in the original post. This is a fact of life. If there were enough information, the OP would have usually found the problem by himself and never posted ("and my SoAndSo.DLL is in... oops... can't find it..."). In some cases there is even wrong information... So there is a huge amount of guesswork at play here.

Of course you could suggest the admins to implement a grade system like on StackOverflow... or you could ask your questions on StackOverflow directly if you are so addicted to definitive answers.

1) This is the problem: the plugin creator isn't a part of the GIMP developing team so, naturally, he updates it on a do-when-I-can, not due-before-the-date-of-the-next-release basis;
2) These are the possible causes: a) open source software - the developers don't get paid for their work b) the developers having a hard time trying to catch up with changing graphic tools API's (GIMP) and/or changing OS's environments c) they just sometimes abandon the project and get on with their lives;
3) Possible solutions to overcome the problem: a) try to follow I-did-so-and-so directions from those people who made it work b) hire a programmer who will create a new or maintain the existing plugin c) use proprietary $oftware d) knock your head against the wall. One of these eventually is going to work.

IIRC the problem is simply the changed directory structure of 64 bit Windows systems.

I'm pretty sure that the solution is already mentioned in numerous threads. Unfortunately, users of the windows platforms are more likely to start guessing than researching, maybe because they don't know about the tools to use for that (has anyone tried to check where UFRaw is searching for its DLL files with the Process Monitor tool by Microsoft, for example?)

I can't speak for others, but after a while, the constant "why, oh why don't they at least try to research problems" feeling is getting quite annoying and causes me to skip lots of questions from Windows users even if I know or would be able research the cause and solution...

AFAIK 64-bit Windows systems are having an issue launching UFRaw standalone and batch, but GIMP still opens RAW files if they (Win users) copied the right files to the right folders. The problem is, they try to launch UFRaw by clicking an application icon, and if it didn't open they think it's not working at all. This has been pointed out in multiple threads, but what can I say, it turns out most people just hate reading these days, never mind searching for the solution to a problem.
BTW, I can see more and more confused Linux users too who cannot compile or install UFRaw on their systems, probably newb's for Linux but it doesn't matter.
The fact is, working with RAW camera files is a much needed feature for high-end image processing software. Not just for the pro photographers. With full-scale GEGL implementation in 2.10 version of GIMP and color depths way beyond 8-bit it would make more sense to have RAW files support out of the box feature. You are a part of the GIMP team, Michael, and I'm wondering if the team is even considering to do something about it. I suppose, it takes no less than a dedicated developer of the plugin (I know they're shorthanded already). Will they decide to go on with 3rd party stuff?

Everyone reading this thread try this, worked for me.

My first and probably last comment here:
I find it frustrating how high and mighty people keep bashing on people looking for answers without giving the slightest hint. Not everyone compiles on a daily basis, and not everyone knows the in's and out's of software creation.

The solution is a actually a mix of some hints here.

1) Start to Install Gimp --> Make sure you choose the "Customize" Button in the lower left hand corner
2) Full Install in the top drop down should be selected, if not, choose all supports possible and go on intalling
3) Start UFRaw installation
4) As Installation directory navigate to the Gimp directory (leave UFRAW as final Path)
5) Install
6) Within the Gimp directory, there now is a 32 directory --> Copy the dlls into the bin directory of UFRaw

UFRaw works.
What still does not work (and that is due to calling a 64bit Application from a 32 bit one) is sending Modified Pictures from UFRaw to GIMP.

Solution (if you deem it sensible): Install 32bit GIMP.

I just wanted to say thank you very much Gon667, your solution worked like a charm, thanks for pointing out that the 32 bit dlls were stored in seperate location from the 64 bit ones =)

P.S. this is why OSS software rules, its supported by the best people on the planet, the community that loves it.

1) Find the UFRaw icon on the start menu.
2) Do right-click menu to Properties
3) In the "Start in:" dialog, type in the path to the directory containing libgdk-win32-2.0-0.dll. On my computer this is "C:\Program Files\GIMP 2\bin" (be certain to include the quotes '"').
4) Apply
5) OK

The icon should now bring up the standalone. Basically this adds the GIMP "bin" directory to the Windows execution path for this icon.

Tried everything on this page. Uninstalled GIMP and UFRAW and reinstalled both (GIMP 2.8.2). Told UFRAW to 'start in' the folder "C:\Program Files\GIMP 2\bin" where the libgdk is found.

Still get the message that it is missing.

Friends, here is a solution that worked for me. I simply put the path of Gimp's DLL (C:\Program Files\GIMP 2\32\bin\) in variable PATH of Win7, in this way:
Right-click on My Computer; properties; advanced configurations; enviroment variables (first menu; on the end); look for PATH; select edit; DO NOT ERASE THE VALUE; on the end of present value, insert GIMP path (C:\Program Files\GIMP 2\32\bin\). That is it.
In my case (Win7-64), the UFraw started to work stand-alone and when double-click RAW files.
Remember to put the actual filename of your version of GIMP on the "options" of Ufraw, so GIMP can get the files provided by Ufraw.
Please, tell me if this solution works for you too.

Thanks Luis Fernandes, this solution you pointed out worked for me!! I'm running Gimp 2.8.6 on Win7-64 and tried your solution and it worked!


Subscribe to Comments for "how to fix libgdk-win32-2.0-0.dll missing error when trying to run UF raw"