Participant

P: Bridge 16.0.4 fails to launch on Windows 10 with "EnumResourceNamesA" entry point error

Forum|Forum|1 month ago
July 1, 2026
78 replies
1860 views

Bridge 16.0.4 fails to launch on Windows 10 with "EnumResourceNamesA" entry point error

Windows 10 Pro 22H2 (Build 19045.6466)
Bridge 16.0.3.21 works correctly.
Updating to Bridge 16.0.4 causes Bridge to fail immediately on launch with:

"The procedure entry point EnumResourceNamesA could not be located..."

Photoshop 2026 works normally. Downgrading Bridge back to 16.0.3.21 resolves the issue immediately.

Pinned Reply By Abu25

Hi,

Thank you for reporting this issue.

We sincerely apologise for the inconvenience this has caused.

This launch failure is specific to Windows 10 systems. As a workaround, please uninstall Adobe Bridge 16.0.4 and install Adobe Bridge 16.0.3. This version is not affected by the issue and should launch normally.

We understand that reverting to an earlier version is not ideal, and we appreciate your understanding.

Thank you for your patience.

Thanks,
Bridge Team

Show previous replies

A

aviationphotogal

Participant

before unistalling the 16.04 version that people have issues with, you may want to back up your preferences…

1. Locate the Settings FoldersClose Adobe Bridge, then navigate to the directory for your operating system:Windows: Open File Explorer and paste C:\Users\[Your Username]\AppData\Roaming\Adobe into the address bar. Look for the folder named Bridge [Version] (e.g., Bridge 2026).

some of these files can be manually copied once Bridge is working again. For example, I have a large number of Collection and would hate to loose those contents

Z

zaidisyed

Participant

Same here

K

KYZM

Participating Frequently

I am struggling to resolve this issue for my windows 10 22H2 PC. I can’t locate v16.0.3 to install. Using creative cloud just installs the latest version. Accessing more actions (...) on the app doesn’t display any previous versions to install - just “manage plugins”. I have uninstalled v16.0.4 and cannot seem to revert to a previous version. Adobe website states use creative cloud app! Any suggestions?

P

pankajg6675616

Community Manager

Hi @KYZM,

Thank you for reporting this issue.
We sincerely apologise for the inconvenience this has caused.

Bridge 16.0.5 has been released and is compatible with Windows 11 and later.

If you are using Windows 10 and currently have Bridge 16.0.4 installed, please uninstall it and reinstall Bridge 16.0.3, as version 16.0.5 is not supported on Windows 10.

Thank you for your patience and understanding.

Thanks,
Bridge Team

K

KYZM

Participating Frequently

It would be helpful if you could provide a link where I can access v16.0.3 to download and install?

F

frankb76907269

Known Participant

Same here:

Edition Windows 10 Pro
Version 22H2
Installiert am ‎18.‎07.‎2020
Betriebssystembuild 19045.7417

J

Jim239090900pzf

Participating Frequently

Running Windows 10 Pro 22H2 and I also had the "EnumResourceNamesA" error come up.

Asked DuckDuckGo about it and it came back with a Windows 10 compatibility issue. Back-installed version 16.0.3.21 and it started working again.

Suggestion: if you have Windows 10/10 Pro, DO NOT USE THE LATEST VERSION OF BRIDGE!

So, I wonder if anyone with a Win 11 O/S version is having this issue? 🤔 If it’s ONLY affecting Win 10 users, I doubt Adobe will fix it since Micros💩t had discontinued support/updates for all Windows 10 O/S’s.

S

StefanKlein

Known Participant

Same here on Win 10 Pro 22H2.

D

DigitalScape

Participant

I have experienced the same issue. Reverting to a previous version fixes the issue, and you have to turn off the auto update for Bridge - otherwise you have the same issue all over again. I hope Adobe is looking into this as a priority.

Windows 10 Pro 22H2

32 GB RAM

C

christined7846789

Known Participant

Same problem here: entry point from procedure EnumResourceNamesA not found in DLL-file C:\Program files\Adobe\Adobe Bridge 2026\Adobe Bridge.exe. I have re-installed the previous version 16.03.21, whichs works fine.

I am using Windows10 22H2. Thanks for helping out.