I encrypted my G: partition. When mounted, the partition is Drive N:
With N; mounted, I tried to install "Google Drive for desktop" (the replacement for Google "Backup and Sync") on N;, but as you will see on the attached, the message I received was that; G: was not available, so it the installer moved the "Google Drive for desktop" to D:
Backup and Sync was installed on the N: drive, no problem. In fact,
When I open the "Google Drive for desktop" preferences > settings, it shows the drive letter, G:, that supposedly could not be found, but when you go back to preferences, and select "Open In Explorer", it takes you to a folder with only a shortcut in it to the D: folder the installer chose as my Google Drive location.
However, it has no problem with the "Google Cache Directory" being located on the same drive that ia purportedly unavailable.
I doubt the following is a factor, but before this, my disk tree was represented in the attached image, with G: as the label for N: drive. I renamed it to N, but it didn't help
Note: I'm having trouble attaching more than one image
to me the message seems like it's how it should be. The path is already added... now I'm not familar with Google Drive but to me it seems to be no VC related issue.
To me it seems like Google Drive was first installed onto G:\ which was encrypted afterwards. Now G:\ is not available anymore. Of course this cannot work out.
Have you tried to mount your encrypted partition as G: ? Then it should have back what it wants.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am not suggesting that this problem has anything directly to do with Veracrypt. it seems to be that it an encrypted partition, not necessarily a Veracrypt encrypted partition, combined with the Google account requirements. I even tried using another Google account, but the same thing happened.
For one thing, It recognizes G: as the drive where my previous Google Drive directory resides, but that has never been the case. Even if it was the case, if I disconnect the Google account, and then uninstall "Backup and Sync", should the Google Drive installer still insist that that N: (or G:) cannot be used?
I was hoping that someone in a similar situation could tell me if they experienced some installation challenges and how they sorted it out.
Last edit: kltpzyxmrm 2021-09-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had a look at this and, as I assumed, has absolutely nothing to do with VeraCrypt.
But to the point.
Google Drive needs a drive letter to mount the cloud storage (like a DAV(s) drive). In your initial post, this would be D: because G: (default drive letter) was unavailable/ in use. But this letter can be changed from the settings anytime.
Furthermore, one need to specify a folder for cache files (somewhere in the user directory by default).
To get to the point: Google Drive is always installed to C:\ automatically. The drive letter specified in the settings is just used as a mount point for the cloud Storage. So this drive letter must not be in use already. Via this drive, you can then directly copy files between your computer and your Google cloud storage.
Greets
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Backup and Sync should be able to use the path of a mounted volume. If your mounted volume uses drive letter N, it should be able to be used.
If I find the time, I will try this in a vm.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I encrypted my G: partition. When mounted, the partition is Drive N:
With N; mounted, I tried to install "Google Drive for desktop" (the replacement for Google "Backup and Sync") on N;, but as you will see on the attached, the message I received was that; G: was not available, so it the installer moved the "Google Drive for desktop" to D:
Backup and Sync was installed on the N: drive, no problem. In fact,
When I open the "Google Drive for desktop" preferences > settings, it shows the drive letter, G:, that supposedly could not be found, but when you go back to preferences, and select "Open In Explorer", it takes you to a folder with only a shortcut in it to the D: folder the installer chose as my Google Drive location.
However, it has no problem with the "Google Cache Directory" being located on the same drive that ia purportedly unavailable.
I doubt the following is a factor, but before this, my disk tree was represented in the attached image, with G: as the label for N: drive. I renamed it to N, but it didn't help
Note: I'm having trouble attaching more than one image
I hoping you can offer me some advice. Thanks
Last edit: kltpzyxmrm 2021-08-30
Can't you move the sync folder to N:\ now?
Greets
I tried, but it just generated that same message I posted.
Here's another one
Last edit: kltpzyxmrm 2021-08-31
to me the message seems like it's how it should be. The path is already added... now I'm not familar with Google Drive but to me it seems to be no VC related issue.
To me it seems like Google Drive was first installed onto G:\ which was encrypted afterwards. Now G:\ is not available anymore. Of course this cannot work out.
Have you tried to mount your encrypted partition as G: ? Then it should have back what it wants.
I am not suggesting that this problem has anything directly to do with Veracrypt. it seems to be that it an encrypted partition, not necessarily a Veracrypt encrypted partition, combined with the Google account requirements. I even tried using another Google account, but the same thing happened.
For one thing, It recognizes G: as the drive where my previous Google Drive directory resides, but that has never been the case. Even if it was the case, if I disconnect the Google account, and then uninstall "Backup and Sync", should the Google Drive installer still insist that that N: (or G:) cannot be used?
I was hoping that someone in a similar situation could tell me if they experienced some installation challenges and how they sorted it out.
Last edit: kltpzyxmrm 2021-09-05
I had a look at this and, as I assumed, has absolutely nothing to do with VeraCrypt.
But to the point.
Google Drive needs a drive letter to mount the cloud storage (like a DAV(s) drive). In your initial post, this would be D: because G: (default drive letter) was unavailable/ in use. But this letter can be changed from the settings anytime.
Furthermore, one need to specify a folder for cache files (somewhere in the user directory by default).
To get to the point: Google Drive is always installed to C:\ automatically. The drive letter specified in the settings is just used as a mount point for the cloud Storage. So this drive letter must not be in use already. Via this drive, you can then directly copy files between your computer and your Google cloud storage.
Greets
Backup and Sync should be able to use the path of a mounted volume. If your mounted volume uses drive letter N, it should be able to be used.
If I find the time, I will try this in a vm.
I'm gonna forego upgrading to Google Drive for Desktop until they works out the flaws. There are several keys areas that were left lacking.