deco_32.dll Missing: Repair the Old App Behind the Error

deco_32.dll is not a normal Windows system file; it is an old 32-bit decompression library installed by certain image and reference applications. The safest fix is to identify the program requesting it, then reinstall that program or remove its obsolete plug-in instead of downloading a loose DLL.

What this file actually does

deco_32.dll was made for decoding Fractal Image Format files, also known as FIF images. It is associated with old 32-bit software rather than Windows itself, including:

As an Amazon Associate I earn from qualifying purchases.

• Genuine Fractals Photoshop plug-ins
• Older Photoshop CS and CS2 installations using Genuine Fractals
• Microsoft Bookshelf ’95 and ’96
• Microsoft Works-era reference software
• Historical full plug-in packages for XnView Classic
• Other older image applications that supported FIF files

The name does not identify a Visual C++ runtime, DirectX component, .NET file, graphics driver, or Windows feature. Windows 10 and Windows 11 may still display the error when an old program, shortcut, startup item, or Photoshop plug-in tries to load it.

Public file catalogs commonly list a version, size, or checksum for this DLL, but those records do not establish one authoritative build. Do not use a matching-looking number from a download page as proof that a replacement file is safe or correct.

Causes and symptoms

What you see	Most likely cause	Correct direction
Photoshop reports that DECO_32.dll was not found	A Genuine Fractals plug-in is incomplete or orphaned	Reinstall Genuine Fractals or remove the old plug-in
Bookshelf reports several missing files, including deco_32.dll	Damaged or partial Bookshelf installation	Repair or reinstall Bookshelf from its original media
XnView fails while opening an old image	A minimal or incomplete plug-in installation	Install the complete official XnView Classic package
The error appeared after antivirus activity	The DLL was quarantined	Check Protection history and reinstall if necessary
“The application was unable to start” appears immediately	A 32-bit application cannot load the file, or the file is damaged	Confirm the calling program’s architecture and reinstall it
The message appears after uninstalling software	A shortcut, plug-in, or startup entry still points to the removed program	Remove the stale plug-in or startup entry
Several unrelated programs show DLL errors	Windows or application files may be damaged	Repair the affected application first, then check Windows components

Fix 1: Identify the program that owns the error

Do this before copying files or running repair commands.

Check the error window

Read the title bar and the text around the missing-file message. The program name may be Photoshop, Bookshelf, Works, XnView, or another image utility.

If the message appears while opening a particular document, note which application opened that document. If it appears during startup, the caller may be a plug-in or an old startup entry rather than the main application.

Check the shortcut

1. Right-click the shortcut that produces the error.
2. Select Properties.
3. On the Shortcut tab, inspect Target and Start in.
4. Note the executable path and its parent program folder.
5. Select Cancel without changing the shortcut.

For a desktop application, the folder containing the executable is usually the right place to look for the application’s own DLLs. Do not move the file yet.

Check Photoshop plug-ins

If Photoshop is involved:

1. Close Photoshop.
2. Open the Photoshop installation folder.
3. Look for a Plug-ins folder and any subfolder named for Genuine Fractals or another image plug-in.
4. Temporarily move the suspected third-party plug-in folder to the desktop.
5. Start Photoshop again.

If Photoshop now opens without the error, the plug-in is the caller. Reinstall its matching version from legitimate installation media, or leave it removed if you no longer use it.

Check startup entries

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Select Startup apps.
3. Look for an entry belonging to an old image, reference, or plug-in application.
4. Right-click a suspicious entry and choose Open file location if available.
5. Do not delete unknown entries. Disable only the entry clearly associated with the obsolete program, then restart Windows.

You can also check Settings → Apps → Startup for the same type of entry.

Fix 2: Reinstall or remove the Genuine Fractals plug-in

This is the strongest match when Photoshop displays the error.

Reinstall it

1. Close Photoshop.
2. Open Settings → Apps → Installed apps.
3. Search for Genuine Fractals or a related image plug-in.
4. If it is listed, select the three-dot menu and choose Uninstall or Modify.
5. Restart Windows if requested.
6. Run the original licensed installer or a trusted vendor-provided installer for the same plug-in generation.
7. Start Photoshop and test the affected image.

If the plug-in was supplied on original media, use that media rather than a loose DLL. The installer places the DLL beside the files that depend on it and restores the required plug-in structure.

Remove an obsolete plug-in

If you no longer need Genuine Fractals:

1. Close Photoshop.
2. Open its Plug-ins folder.
3. Move the Genuine Fractals plug-in folder or file to a backup folder outside Photoshop.
4. Restart Photoshop.
5. Test the program without opening the old image.

If the error disappears, the orphaned plug-in was responsible. Do not delete the backup immediately in case another application still depends on it.

Modern Photoshop versions may not support a plug-in built for older Photoshop releases. In that case, repeatedly copying deco_32.dll will not make the plug-in compatible. Retire the plug-in or use a current image application that supports the required format.

Fix 3: Repair Bookshelf or Works

Older Microsoft Bookshelf installations can request deco_32.dll along with other Bookshelf files. A single DLL replacement is not sufficient because the program also needs its executables, databases, help files, and installation data.

1. Open Settings → Apps → Installed apps.
2. Search for Bookshelf, Microsoft Works, or the relevant reference program.
3. Select the three-dot menu.
4. Choose Modify, Change, Repair, or Uninstall, depending on what is available.
5. If a repair option appears, run it.
6. If repair is unavailable, uninstall the damaged installation.
7. Restart Windows.
8. Reinstall the application from its original legitimate CD or installation media.
9. Launch the program from its new shortcut and test the feature that previously failed.

If the installer does not run on modern Windows, right-click the installer, choose Properties → Compatibility, select a suitable older Windows mode, and run it as administrator. Compatibility mode cannot guarantee that the application will work, but it is safer than manually placing an unverified DLL in a Windows folder.

Fix 4: Repair an incomplete XnView Classic installation

Historical full XnView plug-in packages included support for files associated with deco_32.dll. If XnView is the caller, the installation may be a minimal package without the required plug-ins.

1. Close XnView.
2. Open Settings → Apps → Installed apps.
3. Select XnView and choose Uninstall if the installation is clearly incomplete.
4. Restart Windows.
5. Obtain the current XnView Classic package from the official XnView publisher.
6. Choose the package that includes the complete plug-in set rather than a minimal installation.
7. Install it, then test the image or file type again.

If the current program does not support the old plug-in or format, use a maintained image application instead of forcing the historical DLL into the new installation.

Fix 5: Check antivirus quarantine

Windows Security may have removed or quarantined the file, especially if the application is old and no longer maintained.

1. Open Windows Security.
2. Select Virus & threat protection.
3. Choose Protection history.
4. Expand any event that names deco_32.dll or the application that uses it.
5. Check the file path, detection name, and source.
6. Restore it only when the file came from the original trusted application installation and the expected path is clear.

Microsoft’s guidance on Protection history explains how these decisions work. If the source is unknown, leave the file quarantined and reinstall the application from legitimate media instead. Restoring a detected threat can cause Windows Security to quarantine it again.

Fix 6: Confirm 32-bit and 64-bit compatibility

deco_32.dll is a 32-bit library. A 64-bit process cannot load a 32-bit DLL. A 64-bit edition of Windows can run many 32-bit applications through WOW64, but that does not make a 32-bit plug-in valid inside a 64-bit host application.

Check the application rather than Windows alone:

1. Right-click the application shortcut.
2. Select Properties.
3. Open the Compatibility tab and check whether compatibility settings are already being used.
4. Look in the application’s documentation or installation folder for whether it is a 32-bit build.
5. If the host is 64-bit, install a supported 32-bit version of the host where available, or replace the obsolete plug-in.

Microsoft explains the distinction in its documentation about running 32-bit applications on 64-bit Windows.

A message saying that the application is “not designed to run on Windows” is not proof of a specific deco_32.dll defect. It can indicate a damaged file, wrong architecture, or an application that is no longer compatible.

Fix 7: Repair Windows components only when Windows itself is damaged

Windows repair commands do not normally recreate this third-party application DLL. Use them when Windows has broader corruption, such as multiple built-in programs failing, not as the first response to a single legacy-app error.

1. Right-click Start.
2. Select Terminal (Admin) or Command Prompt (Admin).
3. Select Yes at the User Account Control prompt.
4. Run this command and wait for it to finish:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Then run:

sfc /scannow

1. Restart Windows.
2. Test the original application again.

Microsoft specifies running DISM before SFC in its System File Checker guidance. If both commands complete successfully but the same program still requests deco_32.dll, return to the application or plug-in reinstall.

If manually repeating SFC and DISM leaves you unsure what changed, Outbyte PC Repair provides a free scan that shows what it identifies, while repair is handled by the full version; reinstalling the program that owns deco_32.dll remains the definitive fix.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 8: Do not register or copy this DLL blindly

regsvr32 is for self-registering OLE and ActiveX DLLs that provide a DllRegisterServer entry point. A decompression library normally does not need registration.

Running a command such as this is therefore not a normal repair:

regsvr32 deco_32.dll

It may produce an error saying that the entry point was not found. Microsoft describes the proper scope of the command in its regsvr32 documentation.

Do not copy the file indiscriminately into:

C:WindowsSystem32
C:WindowsSysWOW64

Those folders have different roles under 64-bit Windows, and the application may require the DLL in its own directory or inside its plug-in folder. The installer should determine the correct location.

Also avoid reinstalling Visual C++, DirectX, .NET, drivers, or Windows Update solely because this filename is missing. Those components do not normally contain this library.

Fix 9: Update drivers only for a separate graphics problem

A driver update is not a direct repair for deco_32.dll. Consider it only if the same application also has display corruption, crashes, or a Device Manager error.

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if prompted.

If Device Manager reports an error, visit the computer or graphics-device manufacturer’s official support page and install the driver for the exact model.

If identifying the correct driver manually is the difficult part, Outbyte Driver Updater can scan and show what it finds for free, while driver installation is handled by the full version; this still will not replace the legacy application that owns deco_32.dll.

Fix 10: Try Windows Features only when the application requires them

Some legacy programs require an older Windows feature, but enabling one does not supply deco_32.dll.

1. Press Windows key + R.
2. Type optionalfeatures.
3. Press Enter.
4. Review the available features, such as .NET Framework 3.5.
5. Enable a feature only when the application’s installer or documentation specifically requires it.
6. Select OK and allow Windows to complete the installation.
7. Restart the application.

Do not enable random features to resolve this filename. If the program still reports the missing DLL, repair the program itself.

If nothing works

Use the application’s own repair path:

1. Open Settings → Apps → Installed apps.
2. Select the affected program.
3. Choose Advanced options.
4. Select Repair when available.

For older desktop programs, open Control Panel → Programs and Features, select the application, and choose Repair or Change.

If the error clearly began after a recent installation or removal:

1. Press Windows key + R.
2. Type rstrui.exe.
3. Press Enter.
4. Choose a restore point created before the problem.
5. Review the affected programs before confirming.

Use System Restore only when the timing is clear. It will not supply a legitimate standalone copy of the DLL, and it may remove recently installed applications.

Frequently asked questions

Is deco_32.dll a Windows file?

No evidence identifies it as a Windows system component. It is an old third-party application library associated with FIF image decompression.

Can I download just deco_32.dll?

Do not use random DLL download sites. The file may contain malware, belong to the wrong application, use the wrong architecture, or omit other files the program needs. Use the original application media or the software publisher’s official installer.

Why does Photoshop ask for it?

An old Genuine Fractals plug-in may still be installed or partially removed. Reinstall the matching plug-in or remove the obsolete plug-in from Photoshop’s plug-in directory.

Will Visual C++, DirectX, or Windows Update fix it?

Usually not. Those are not the normal source of this application-specific library.

Should I run regsvr32?

No, not normally. This is a decompression library, not typically a self-registering ActiveX or OLE component.

Can 64-bit Windows use it?

A 32-bit application can often run on 64-bit Windows, but a 64-bit process cannot load a 32-bit DLL. The host application and plug-in must use compatible architectures.

What if I no longer need the old program?

Remove the orphaned plug-in, startup entry, or application that requests the file. A clean removal is safer than keeping a loose DLL in a Windows system folder.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.