Unable to import selected photos from bridge to lightroom

[exarcade]

I ussually slect the pics that i want to import to lightroom and then just drag in to. So on the importing menu only appears the pics that i previously selected marked to import.
With this last uptade i can do that anymore.

[GoldingD]

What OS? And if Catalina, when did that change?

[Just Shoot Me]

What EXACT version of LR Classic and is it actaully LR Classic you are asking about (and not the newer Cloud Centric Lightroom)?

So both programs are open and you select images from a Folder in Bridge and then Drag those selected images into the LR Classic program?

If that is the case what exactly happens next?

For me the Import dialog window opens and all of the images from the folder those images are in is shown and the ones I had selected are checked for import.

Here are some screen shots of what I see and what happens. Post screen shots of what you see and happens.

[Bojan Živković]

Just to confrm exactly the same is hapening on my Win Machine using Lightroom Classic 9.2 and Bridge 10.0.3.138.

[Cervajz]

I have the same issue since I updated to latest Lightroom (it is possible, that even Bridge was updated at the same time - thing is, both are the latest versions now). Win 10.

Before it worked for me, when I drag selected photos from bridge and drop them into lightroom library window, than "Add" (or "Import") window appeared and photos I have selected in Bridge was checked. This dont work for me anymore, now I drag and drop into Lightroom library,"Add" window appears with any of photos checked, and then I have to drag and drop selected photos from bridge to lightroom again at this moment (into already opened "Add" window), and Lightroom will check selected photos. I think it is some kind of bug.

[Conrad C]

Is this the same problem that has been reported at the Lightroom Feedback site here?

https://feedback.photoshop.com/photoshop_family/topics/drag-drop-no-longer-works-for-import

If it is, Adobe staff in that thread have acknowledged this and logged it as a bug to be fixed.