The installation file can't display drive labels because it lacks the necessary permissions or configuration settings.
The installation file can't display drive labels because it lacks the necessary permissions or configuration settings.
The installer provides only 'Drive # Partition #' details for each drive and partition. It was hard to distinguish them since both were 1TB. I had to keep both drives active during installation because Dell’s laptops behave oddly and don’t automatically recognize additional internal drives unless they’re installed during the Windows setup.
Drive letter refers to a Windows idea (actually more like DOS), not a standard setting. Windows doesn't assign drive letters for use; instead, it designates the letter based on installation. When you have multiple drives and Windows is running on each, both may show C as the letter, but they conflict in how you perceive them. Typically, from the motherboard side, drives start at 0, while partitions begin at 0 as well.
They're asking why Windows installer wouldn't recognize the drives when BIOS can see them. The SSD is set as default (drive 0) and the HDD as secondary. It's puzzling that the installer swapped them despite the BIOS settings. I'm curious if, with a strange BIOS configuration, Windows could have detected the drives if they were disabled during setup. Updated January 31, 2023 by tddk25 (missed last sentence).
You might attempt to recover files that haven’t been replaced by the latest setup. Use PhotoRec - CGSecurity to look through available free storage for previously saved data.