Some common situations are mentioned below. There are a lot of issues with Google Drive File Stream that usually users suffer while using it. Common Reasons When Google Drive File Stream Not Working
#WINDOWS GOOGLE DRIVE NOT SYNCING 2015 WINDOWS#
So, let’s start the article with these safe techniques to fix “Google drive file stream not working Windows 10”. Users have to just go through these lines carefully so that they can avoid data loss. These techniques are quite beneficial for users in solving this issue. Therefore, to know more about these techniques just read this article up to the bottom. This workaround does not compromise the end client security and data because the certificate bypass is done between the FGT and client, when FortiGate has decrypted the data and it is in the process to deliver it to the client.But as with others, it also has some issues that can be solved by using some techniques.Google has provided an option to bypass the certificate validation by using a switch “-unsafe_network”.With SSL decryption enabled, the Google Drive client receives an untrusted certificate from the FortiGate device and the connection ultimately fails. When the Google Drive client software, installed on a desktop, attempts to connect to the Google server, it expects to receive a valid certificate from the Google server.This is because when SSL Decryption is enabled, the FortiGate device receives the external site's certificate and sends its own self-signed certificate to the end client.Google Sync and Backup desktop application was waiting for google certificate instead of FortiGate certificate. If the FortiGate does not have a valid certificate, the application will not work. This issue occurs due the site having SSL Decryption enabled, so the Google secure connection for Google Drive app will detect an invalid security certificate. Application did not work due a certificate error.So, what actually is the purpose of the 'Google Drive' SSL deep packet exemption entry that I see there ? i.e. If it did, then there would be no need to run the Google Drive app in 'HTTP' mode. Hello, this is fine, but I would like to understand why the SSL deep packet exemption for 'Google Drive' doesn't seem to work. "C:\Program Files (x86)\Google\Drive\googledrivesync.exe" -unsafe_network Īdd the value -unsafe_network after the quote as shown below. You can also push out a registry entry change if Drive Sync is auto starting Open a command prompt and navigate to the folder where Google Drive is installed.Īt a prompt, run googledrivesync.exe -unsafe_networkģ. Edit the shortcut for the Google Drive and add the switch at the end:Ĭhange C:\Program Files\Google\Drive\googledrivesync.exe to C:\Program Files\Google\Drive\googledrivesync.exe" -unsafe_networkĢ. Use any of the following three methods to activate the switch.ġ. The methods below have been tested and seem to be viable. The invalid certificate can be ignored by adding a switch when running the app. The work around, however, is fairly simple. There is no way to modify the certificate or add certificates in the app itself. Unfortunately, the app uses its own certificate instead of sharing the browser’s certificate store. When SSL Decryption is enabled for a site like, the secure connection in the Google Drive app will break due to an invalid security certificate. I found this to be a workaround but it appears you will be setting the application to http instead of https so if it's secure data it wouldn't be a wise idea.