Make sure only the right processes can access the profile path.

chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index b222a5668ad2346b7c608be22f0f3838cfbb1872..218a161f661d2648d5b0c12e7729eb447ee9a4fd 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -9728,6 +9728,11 @@ Some features may be unavailable.  Please check that the profile exists and you
       <message name="IDS_REFUSE_TO_RUN_AS_ROOT_2" desc="Detailed message in the error dialog when the user tries to start chrome as root">
         Please start <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> as a normal user. To run as root, you must specify an alternate --user-data-dir for storage of profile information.
       </message>
+      <message name="IDS_PROFILE_ON_NETWORK_WARNING" desc="Warning shown to the user in a dialog box when he is running Chrome on Windows with a profile located on a network share.">
+Your browser is running with a profile located on a non-local drive. This configuration is not fully supported and might not work reliably. 
+        
+Consider switching to profile stored on a local drive for optimal experience.
+      </message>
 
       <!-- Can't write to user data directory dialog -->
       <message name="IDS_CANT_WRITE_USER_DIRECTORY_TITLE" desc="Title of dialog that is displayed when we can't create a directory for this user.">