mirror of
https://github.com/reactos/reactos.git
synced 2025-05-18 16:51:18 +00:00
[MOUNTMGR] Fix interpretation of QueryDeviceInformation GptDriveLetter
Being TRUE doesn't mean the device is GPT and has a drive letter. It just means that it's not a GPT device with GPT_BASIC_DATA_ATTRIBUTE_NO_DRIVE_LETTER attribute. In short, if TRUE, it means that the device can receive a drive letter mount point. This fixes MountMgrNextDriveLetterWorker bailing out for any attempt to assign a drive letter to a device.
This commit is contained in:
parent
961693f060
commit
e359a3c888
1 changed files with 3 additions and 2 deletions
|
@ -524,11 +524,12 @@ MountMgrNextDriveLetterWorker(IN PDEVICE_EXTENSION DeviceExtension,
|
|||
}
|
||||
|
||||
/* If we didn't find a drive letter online
|
||||
* ensure there's no GPT drive letter nor no drive entry
|
||||
* ensure this is not a no drive entry
|
||||
* by querying GPT attributes & database
|
||||
*/
|
||||
if (NextEntry == &(DeviceInformation->SymbolicLinksListHead))
|
||||
{
|
||||
if (GptDriveLetter || HasNoDriveLetterEntry(DeviceInformation->UniqueId))
|
||||
if (!GptDriveLetter || HasNoDriveLetterEntry(DeviceInformation->UniqueId))
|
||||
{
|
||||
DriveLetterInfo->DriveLetterWasAssigned = FALSE;
|
||||
DriveLetterInfo->CurrentDriveLetter = 0;
|
||||
|
|
Loading…
Reference in a new issue