See screen shots below. According to Windows, there are 3657 files in the folder. According to Bridge, there are 5859 files in the folder plus 104 hidden. According to Bridge, the sum of all of the ratings is 3553. Add the 104 hidden files and voila, 3657 files - same as Windows.
Ordinarily, I wouldn't even notice this. But when I'm waiting over 30 seconds for Bridge to simply show a PSD that I've just saved so I can rate it, I have plenty of time on my hands to look around. Of course, Bridge is consuming over 99% of the CPU for hours on end, so I have an hour+ PER DAY to sit and wait for Bridge. NOTHING else is running. Just Bridge and PS.
Meanwhile, editing in PS is painful. Move a slider, wait a few seconds for PS to get some CPU cycles from Bridge, display the change. Too much, move the slider back a bit, wait a few seconds for PS to get some CPU cycles from Bridge to display the change...
I have a reasonably powerful PC.
64GB DDR4 3600 RAM
RTX 3080Ti (latest studio driver)
Windows 10 Pro (latest update)
Bridge cache in the default C:/ location. C: is a 1TB SSD with 64% free.
Files are on a 14TB directly connected drive with 79% free.
I've run numerous benchmarks. All say that the PC is operating better than average for this configuration.
I've been complaining about this for over a year. Adobe just doesn't want to hear it. NOT A SINGLE RESPONSE FROM ANYONE AT ADOBE.
I am not Adobe, just another user like you.
I do not have an answer, just a comment that your screen-clip shows the same Filename at least FOUR times, so something weird is happening for sure.
Have you tried an Un-install, reboot, and Re-install?
Thanks for your reply. Yes, you saw something that I've also brought to Adobe's attention and received no response. Sometimes for long periods (hours), when the newly created PSD does finally show up in Bridge, it's there multiple times. I can't select one of them - selecting one selects all of them.
I have deleted and reinstalled Bridge several times. That only seems to make it worse. I've downgraded to V12 and it's slightly better, but the problem is still there. I guess no one from Adobe cares.