Bug: Drive is not being recognized

[KremmenUK]

Description

I have one drive G:\Dashcam that is not being displayed. Looking through the debug.log it is showing "|Warning|Invalid path: G:\My Drive"
This is a Simple NTFS parttion on a SSD where the other partitions are OK

Steps To Reproduce

Just opening Files 3.7

Requirements

No requirements

Files Version

3.7.0.0

Windows Version

Windows 11 Home 22631.4037

Log File

debug.log

[KremmenUK]

Just for info:

Windows File Explorer, Windows Drive Manager and a host of other programs recognise the drive OK

Windows File Explorer:

Files 3.7:

Disk Manager breakdown 👍

[yaira2]

It might be a permissions issue where Files is having trouble accessing the drive. Further investigation is required.

[KremmenUK]

Thanks I've used every program I have on the PC and they all show the G:/ and it's contents I've scanned the drive with Samsung Magician, Minitool Partition Manager and CHKDSK and none can find any issues The G:/ has about 30 folders all containing very large dashcam video files of about 600Mb each file I also have a program I wrote in VB.Net and that shows the G:\ Definitely an odd one I am PC literate so any guidance would be understood

…

On Tue, 10 Sept 2024, 16:24 Yair, ***@***.***> wrote: It might be a permissions issue where Files is having trouble accessing the drive. Further investigation is required. — Reply to this email directly, view it on GitHub <#16149 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BLDQFKDCZG4YRRJE26MIOPDZV4FJDAVCNFSM6AAAAABN2VUXTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGI2DINRZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[0x5bfa]

Have you ever installed Google Drive mapping to G drive?
If so, could you check HKEY_CURRENT_USER\Software\Google\DriveFS in Windows Registry (Windows+R > regedit.exe)?

---

G is probably registered as a google drive before in Windows registry and the app trying to validate here:

Files/src/Files.App/Utils/Cloud/Detector/GoogleDriveCloudDetector.cs

Line 282 in 6270935

return ValidatePath(path);

Files/src/Files.App/Utils/Cloud/Detector/GoogleDriveCloudDetector.cs

Line 245 in 6270935

_logger.LogWarning($"Invalid path: {path}");

This method is called by the drive enumeration service method and if the drive matched the drive will be skipped. So that's why I assume.

Files/src/Files.App/Services/Storage/StorageDevicesService.cs

Line 25 in 6270935

var googleDrivePath = GoogleDriveCloudDetector.GetRegistryBasePath();

Files/src/Files.App/Services/Storage/StorageDevicesService.cs

Lines 32 to 34 in 6270935

	// We don't want cloud drives to appear in a plain "Drives" section.
	if (drive.Name.Equals(googleDrivePath) || drive.Name.Equals(pCloudDrivePath))
	continue;

[KremmenUK]

Very likely, I did have Google Drive for a very short time, years ago Sorry for the delay, I'm on UK time Give me an hour as I've just got up, it's 04:30 here Thanks for the quick response Update - Good call - 'PerAccountPreferences in the DriveFS Key {"per_account_preferences":[{"key":"116089142547656472241","value":{"mount_point_path":"G","disable_realtime_presence":true}}]} Do you want me to leave this key alone so I can test any fix ? There is also a duplicate key at "\HKEY_USERS\S-1-5-21-4094688386-2051550529-204182734-1003\Software\Google\DriveFS" I've changed the key from "G" to "Y" and my G:\ is now showing I'm happy to change it back to G if you intend making a program change so I can test it

…

On Tue, 10 Sept 2024, 23:04 0x5BFA, ***@***.***> wrote: Have you ever installed Google Drive mapping to G drive? If so you check, HKEY_CURRENT_USER/Software\Google\DriveFS in windows registry? ------------------------------ G is registered as a google drive in Windows registry and the app trying to validate here: https://github.com/files-community/Files/blob/62709351a3513da5d6f4a6653e195307c6a6673c/src/Files.App/Utils/Cloud/Detector/GoogleDriveCloudDetector.cs#L282 https://github.com/files-community/Files/blob/62709351a3513da5d6f4a6653e195307c6a6673c/src/Files.App/Utils/Cloud/Detector/GoogleDriveCloudDetector.cs#L245 This method is called by the drive enumeration service method and if the drive matched the drive will be skipped. So that's why I assume. — Reply to this email directly, view it on GitHub <#16149 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BLDQFKAI3K3XZDQLLCB3JJDZV5UGLAVCNFSM6AAAAABN2VUXTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBSGA4DKNRUGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[0x5bfa]

Do you want me to leave this key alone so I can test any fix ?

If you no longer use Google Drive you can delete. Otherwise, I have no idea how this key affects on Google Drive client app.

There is also a duplicate key

Yeah. HKEY_USERS\S-1-5-21-4094688386-2051550529-204182734-1003 the same as HKEY_CURRENT_USER. It's kinda shortcut. (S-1-5-21-4094688386-2051550529-204182734-1003 is ID of your current user, so if you login with another user the value changes and content of HKEY_CU will be different.)

---

@yaira2 I think we maybe should not skip without any checking if it's really a cloud drive. It'd be better to see if it's physical drive.

[KremmenUK]

Thanks

I no longer have Google Drive. I will leave the key in place for now just in case you want me to test any fix in the future.

Thanks again for the advice

[0x5bfa]

@wharvex Fyi. This case somehow Google Drives client didn't uninstall appropriately. Do you think we should add a check if the drive is really a cloud drive instead of skipping without?

[wharvex]

Interesting, thanks for letting me know about this. I'll look into it today.