Haha jbm007.  My post was for the OP.  I'm with you.  I've never seen it behave as the OP insists.   ... View more

Well, I wait with great anticipation that you will post the solution when you regain this function.  🙂 ... View more

Make sure it's the Contents Panel you double-click on too.  Doing it in the Preview Panel will get you nowhere. ... View more

Double-click on the folder in the contents panel. ... View more

Just to eliminate another possibility, I changed to those settings and relaunched Bridge.  Here's my Windows Task Manager.  It will run like this for days on end if I let it, but the CPU gets over 90 degrees Celsius, and that is not good, plus you can't use the PC for anything else while it's getting hammered by Bridge. ... View more

I need monitor-sized previews for my workflow.  Other than that I have tried those settings and it doesn't work for me.   ... View more

Oh, and the latest version of 2021 does not finish a batch rename, instead leaving the dialog box on screen.  It does not move all selected files either, nor does it delete all selected files.  In short, it is not fit for purpose. ... View more

Yes, I have this same problem.  Have had it for the previous two versions.  Strangely, my machine's specs are very similar to yours ie high end.  I have 64gb of RAM and a GTX1070 with 8GB of RAM, and two SSD drives - one for the system and the other holds the Bridge Cache as well as the PS Scratchdisk.  Generating screen-sized previews takes forever and when I have over a few hundred RAW files in a folder, Bridge will crash and I'll have to log back in to open it again only for the same process to happen again and again.  Adobe have screwed the pooch. ... View more

This should not be news to you guys at Adobe.  I've been reporting the same issue for over two years!  Three releases later and the problem is still there. Good luck to the OP.  The issue is related to the rendering of previews and writing to the Cache.  ... View more

I've noticed the Move Command in Bridge leaves files behind in the original location.  This has been happening swince before the latest version.  It should have been fixed before rolling out the latest release.,  In fact lots of bugs should have bveen fixed before rolling out the next release.  We all seem to be Adobe's beta-testers.  Deleting files also sometimes leaves files undeleted.  Adobe must have outsourced development to the monkeys who no longer have typewriters. ... View more

I ended up rolling back to Bridge 2018.  I'm running the latest RAW version 12.4 with that and the latest version of Photoshop 2020.  Huge improvement over both Bridge 2020 and Bridge 2019.  It's a workaround if you have no other solutions being offered by Adobe. ... View more

I've been struggling to get any meaningful workflow from CC 2020 for months now.  I get looged out and have to enter my email address and password every five minutes or so.  It shuts down.  It won't remember ratings or labels.  When it does run, I can't even use the keyboard in other applications.  My cursor disappears and other apps start shutting down. However that is not why I am posting.  I know that no-one here has an answer, but I have found a solution that works for me.  I have rolled back Bridge and Photoshop to CC 2018 which was the last version I had no problems with.  I am still able to use ACR 12.3 over the top of those two apps.  In fact I'm currently running 19,240 RAW images through a batch using this setup and not a problem.  In order to roll back to Bridge 8.1.0.383 and Photoshop 2018, you'll need to get onto a download site to get CC2018.  There are sites offering genuine CC 2018 which onbce installed you log in using YOUR Adobe account details.  You need Photoshop CC 2018 to be opened before Bridge 2018 will let you use the RAW editing features as it is the ''qualifying product'' you need. Now this worked for me.  It may or may not work for you.  However as someone once said ''If something is not working for you, try ANYTHING else''. ... View more

I sympathize with you, but Adobe have placed you in this position.  The software directly links customers with issues to this site.  Nowhere does it tell people (nowhere that I saw anyway) that you are not employees on a help line.  You've been set up as a room where people come to bang their heads against the wall.  I'm sorry, but I very much doubt that anyone who does not know anything about the underlying code is going to be able to help solve the problems with how cache is generated and used by Bridge, no matter how keen or seasoned a user they may be.  That's not your fault.  I DO feel that Adobe is trying to filter its interactions with customers in the same way that banks and telcos do.  I have been an Adobe customer for 20 years.  I'm appreciate the complexity and mostly good performance of the product or I wouldn't still be a customer.  What I'm not 100% happy about is their approach to dealing with customer concerns.  Anyway, I'll leave you to it and battle on.  Deleting the entire Cache and starting afresh will take a week or more of my time that I will never get back. ... View more

Thanks for the suggestion Jaap, but I already do that.  I have to, to get the images into Cache.  It hammers the CPU for many hours to cache 2 or 3 thousand RAW files I may shoot in a day.  The annoying part is that this was not the case with Bridge 2017.  It was fast.  Adobe changed the code in some way that has caused its performance to suffer.  This latest iteration also fails when renaming.  It leaves files behind when moving images from one location to another as well.  It fails to delete images.  I can't help feeling that all of these issues are related to way it generates its Cache. ... View more

All of my software is up to date.  I've checked the drivers on my devices too.  This was happening before the latest Windows 10 updates anyway.  I've run sfc /scannow too and it fixed some corrupt files.  Made no difference to the Bridge issues.  I'm now running Bridge again without keeping 100% previews in cache, but producing screen-sized previews instead.  The problem persists.  By the way, why would Bridge create 100% previews of JPEG files?  Isn't that just unnecessary duplicatrion?  I use Bridge primarily as a Digital Asset Manager.  I keyword my files and tag the IPTC EXIF fields.  My basic editing is in ACR and I only go to Photoshop when I want to produce client work.  At this time, I'm having to Use Photo Mechanic to do my importing, culling, and keywording because Bridge is just a bottleneck. ... View more

And this is the problem Gary.  No-one at Adobe wants to touch these reports.  How did you get the label Adobe Community Professional Gary?  Reply to a set number of posts?  I'm just interested.  It's not an attack on you. ... View more

Go to Camera RAW Preferences in Bridge.  Under File Handling you'll find a box for DNG.  Choose your options there. ... View more

I agree.  The same applies to the crop tool as to the brush tool.  Obviously no-one had this beta-tested with real world volume photographers. ... View more

Yep, let me join the chorus.  I've been reporting this iussue since before Bridge 2019.  It all went pear-shaped for me after 2017.  Rendering previews of RAW files smashes the CPU.  Doesn't use any GPU resources.  Like others here I have a high range specification PC with 8gb video card, 64gb RAM and a six-core processor.  Apps are iunstalled on SSD as well as a separate SSD for the Bridge Cache.  My keyboard even takes ten seconds to render a keystroke when Bridge is hoigging all the resources.  It even worse now since the latest updates.  Now it hogs RAM too and crashes the computer. ... View more

Looks like a video card issue to me.  Try going into your Bridge Preferences and swithching off the Use GPU option, then get out of Bridsge and re-open it.  Turn the GPU option back on latewr if the problem has gone away.  Check for an upgrade in your GPU driver first though. ... View more

Mine does this too.  It has being doing it since CC2018.  It does it when it is creating full res previews from RAW files.  The computer becomes unusable while it does this.  When previewing PSD files, the CPU gets used to around 50% maximum.  When previewing JPEG files it gets used to around 24%.  Previewing around 120 5D Mk IV RAW images takes as long as previewing 24,000 JPEG images.  Something is not right in the code.  I've reported this before for three years now.  Nada from Adobe.  The folks here are not Adobe programmers.  They want to offer workarounds, but I'd prefer my software to be bug-free. ... View more

Yes I hate that too, but I found that if you didn't double-click on the crop, when you clicked on the next image the crop was there in the previously selected ratio.  I have no idea why Adobe let the developers loose to change everything around.  They obviously did not check with users who had a workflow, but one-off amateurs who process their images one at a time.  I guess when you outsource your programming to the cheapest bidders, you get the cheapest result. ... View more

I've reverted to CC2018.  Bridge is happily rendering full sized previews for nearly 200,000 RAW files from my 7DMkII.  It is not taxing the computer at all, and it is a hell of a lot quicker than cc2019.  It hasn't crashed yet either.  About time Adobe fixed their crappy programming job. ... View more

I have a folder with 15,000 PSD files in it.  Bridge does not go over about 30% CPU usage generating previews from these very large files.  The problem only occurs with RAW files on my computer. ... View more

What do I want you to do?  Stop throwing mud in the water.  If you don't know the answer, don't make one up.  Do what I do.  If you don't have an answer, then don't comment.  As I said, that is just throwing more mud in the water. ... View more

It seems there's been precious little that HAS BEEN helpful here, apart from Brainbug's contribution.  Let's be clear here.  I'm not looking for a work-around.  I can figure those out myself thanks.  I'm looking for working software from a company that seems to have a real problem with catering to customers.  I resisted the contribution model after I'd paid for upgrades all the way from Photoshop 6 nearly 20 years ago.  Eventually I had to go to CC.  Then when Updates to CC2019 appeared on CC, I installed those only to be told by Adobe that I would have to upgrade from the perfectly good Windows 7 to Windows 10.  I did that, and now I find that CC2019, or the Bridge component anyway, is not fit for purpose.  Then all I get from those around here with their pretty ACP badges is that I need to make changes to a workflow I've been using since CS3 and that there is nothing wrong with CC2019.  I'm paying for up-to-date working software from Adobe, and you're telling to go back to an earlier version? Really? Adobe should look at how quickly a software vendor can go backwards into oblivion when customers vote with their feet.  Look up WordPerfect and Lotus1-2-3, or Netscape. ... View more

What rubbish Lumigraphics.  Using 100% of the CPU and stopping everything else from functioning is NOT a good thing.  How do you get an ACP badge, just from participating?  Mate you have no solutions to offer, just excuses and the suggestion to work around a dud system.  Adobe introduced this problem with CC2019.  They need to fix it. ... View more

Quite right Brainbug.  I think some here think that the more files you attempt to process, the more intensive the CPU must work.  It just runs longer, not harder.  Even smaller numbers of files, a few hundred gets the CPU at 100%, but it doesn't stay there as long because the processing finishes more quickly.  Try this too.  When your CPU is getting hammered at 100% creating a cache, attempt to rename the files.  You'll notice something curious.  The CPU load drops into the 20% range whilst the rename is occurring, then shoots back up to 100% when it returns to just creating previews/cache.  There's clearly something wrong with the coding. ... View more

Lumigraphics,  Bridge CC2018 can and DID handle this.  Why not Bridge CC2019?  Thankfully you're not a programmer or we'd all still need our abacas. ... View more