P: Allow use of Drive Letters A: and B:

The photos in my catalog are all on my A drive. (It's an internal 16Tb drive and the drive letter and name does not change.)

When importing, this drive *used* to show up in the source list on the left, and the destination list on the right. However, while the other drives still appear, and I can still select the A drive at the top left and right, it no longer shows up on the right (when I am importing photos from another folder on my A drive) or on the right (which was very handy to make sure they were importing in the correct folder structure).

The A drive is still available: it shows up as green in my folder list...

...and I can, in fact import successfully. But it's disconcerting to be doing so effectively "blind", particularly in regards to previewing the destination folder structure. I really miss having the preview folder structure on the right side. Any idea why my A drive isn't showing up in import - and how to get it back?

I'm running 13.1 on Windows 10.

I do not use drives A: or B: in Windows for data, but for YEARS I have been setting up an SSD as drive B: which is where I keep my LrC catalog. Never an issue.

MacOS uses drive names rather than lettters and drives must be renamed precisely when substituting one LrC data drive for another. For example when a larger drive is required for image files.

• I recently added a second SSD to my laptop, running Windows 11 Home.
  • Being a bit persnickety about drive letter assignments, when I partioned it into two drive I assigned the drive letters A & B to the partitions created.
• Photoshop had no problem reading or writing to the A or B drive, however Lightroom Classic is still under the impression that A or B drives belong to floppy drives or some sort of issue like that.
• I reassigned the drive to letters E & F and I now have full access to the drives in both Photoshop and Lightroom Classic. 
• I do not know if this would be an issue with MacOS or not.

@Adobe Support please add this as a note for your Tier 1 tech support because they wanted to monkey around with the permissions and such on my drive when I specifically if drive letter assignment was a known issue. 

Best Regards Y'all.

I have just connected a new SSD (Samsung T7) to my laptop that I have downloaded some images to, I open up LRC, go to import and the drive is not showing, all of my other drives are, just not the new one. 
I have shutdown the computer and restarted with drive attached and then relaunched LRC, but still cannot see the drive (B for drive letter). I can see the drive in file explorer and add and delete from it, security settings are turned off.
Never had this issue before with SanDisk SSD, just plug and play, or even with my old Samsung T5
Any ideas gratefully recived

it's a work around, not the solution.

It's a crazy limitation and silly the things apologists in this thread have come up with over the years to try to defend the status quo.  Even after you override and get your desired drive to the 'To' destination at the top right, Lightroom refuses to show your selected destination amongst the expanded Destination list at the right.  Adobe should be embarassed. 

Does the answer marked "correct" not work for you?

I posted about this yesterday, having not found another thread on the topic... because the thread was so old!!
12 years later and it's still not resolved. 
In a couple of years, this thread will be ready for school leaving exams

hi, it's really simple.

I'd like to simply navigate to my B: Drive when looking to import files into lightroom.

I realise that it's just a legacy concept that A and B drive were portable (floppy) drives only, but times have moved on.

I used a high speed SSD labelled as B: drive for all sorts of tasks.

I can get there by "selecting a source" but it would be simpler if the B drive was listed along side all of my other drives.

thanks

Problem z importem do Lightroom.

W przypadku pracy na dysku A (kiedyś to była dyskietka) - LRC nie widzi tego dysku w źródłach. Dopiero w wyborze WYBIERZ ŹRÓDŁO i poszukaniem tego dysku jest on dostępny. Dlaczego, skoro to normalny fizyczny dysk program go nie widzi?