P: Ability to disable eject memory card after import

You mean you do not know? Not a suspicion how it happened? A hypothesis: by mistake? 

Okay, cool for you. But then why jump into a discussion about issues with Lightroom CC...?

Indeed, I only use Lightroom Classic, the original. I do not know, and I do not want to know "the modern Lightroom." 

There is no such option. Are you confusing Classic (which had/has the option) with modern Lightroom (which doesn't and is the subject of this thread)?

This was the proper answer: There is a checkobox in the import dialog "eject after import", not the others "there is no way." It is just so that this option is on a "bizarre place", but not in the Presets. This causes the confusion.

when importing from Lightroom, I rename those from a location, import, then go to the next series on the card. To have the card ejected by LR classic is an absolute pain in the ass. I dont believe these software developers actually use a camera in real life situations

Thank You 

hey everybody - took me a while to figure this out but there's a pretty good work around that will prevent auto-eject. instead of selecting the SD or CF or whatever card in the drop down, browse to the image file path and select the folder to review for import. you can also filter your results here because it's finder. E.g. I never import videos into lightroom because all of my video files are 422 and huge. using the browse method, I can filter out the video files. I also like to avoid wiping my SDs unless it's job specific or if it's full. this should keep performance up, marginally, over the lifetime of a card. The browse method allows me to sort by date so I'm not doubly importing. While using this technique doesn't fix the auto-eject feature, you can effect select the SD manually and it will not auto eject. hope this is helpful for those of you who haven't figured this out yet!

It seems so odd to me that Lightroom CC adds so many great features (better UI, auto-settings, etc) over Lightroom Classic, but removes so many other quality of life features that Classic made feel standard.  Auto-ejecting the SD card doesn't even make sense as a default.  If I import the pictures, why would I then immediately want to put the SD card back in my camera?  Surely most people would want to at least clear off the card before their next photoshoot.  Sure, it's great that CC can identify images it's already imported, but I just don't see how that balances being able to clear off the card, or import files into another program (even another Adobe app!).  I would really like to see Adobe pick up the ball they dropped and actually work on making their software nicer to user rather than shoving AI Powered Feature Useful to 5% of the User Base (tm) down our throats.

Make the software have better UI/UX, improve existing features, make it run faster and use less RAM.  In short, polish what's already there before it turns into a turd, because no amount of polishing will save it then.  And it starts with simple things like not forcefully ejecting an SD card at the end of import.

Can't believe that three years later this is still an issue that hasn't been addressed :(.

I recently started doing  a lot of shooting with a drone, and that includes video and photos (I wasn't much into video before), and like others, I don't want my gigabytes of raw 4K video to go into lightroom, so I have a workflow where Hazel.app automatically moved the videos off the mounted SD onto my harddrive. This can take a while, and sometimes I'm impatient to get my photos into Lightroom, but I can't until the videos are copied over, because otherwise, the SD card will be ejected under Hazel's feet while the videos are being moved. Not cool.

This really should not be rocket science to add as an option? I'm a software developer myself, as my main job, and i cannot think of any factors that would make not, literally, a takes-less-than-an-hour fix...