MDT & Google Drive client

[synaesthesia]

Afternoon good folks!

Come across an anomaly which I'm struggling to get past.

Using MDT which has Just Worked (tm) since day dot. Recently started getting WIndows 11 24H2 builds going, however they all now fall over when installed the Google Drive client (googledrivesetup.exe). No errors, nothing in event viewer, nothing. The installer client is running in taskmanager, and killing it then completes the build.

I've recreated the application in MDT to no avail. I suspect, but alas cannot prove this is only since the most recent version. It also does it when just running it as an app install via litetouch with windows already installed, however the exact same command line to install it just works.

All other applications install absolutely fine.

Installing via litetouch on one of the older Windows 10 machines also fails in the same way (well it doesn't fail, it just sits running googledrivesetup.exe and doing precisely nothing)

Command line being used is googledrivesetup.exe --silent --skip_launch_new and have also tried just --silent to rule out an issue there. 

PDQ Deploy installs it just fine - using exactly the same source file.

I'm at a loss on this, is there something I'm missing? MDT seems to be the sticking point!

[flipthebit]

Is Chrome installed? Is it updated to the latest version before googledrivesetup is run?

[synaesthesia]

It's installed at that point yes; however wouldn't think it's the issue if it works when installing manually but not when installing via litetouch after the windows install is complete.

[andy_nic]

i had this with installing office it would just sit there until you cancelled it, but running it manually after the build works fine.  Still hit and miss when i update the application in MDT, have your tried a restart task before installing the application? i've had application not install as something which installed before it made it crash out.

Edited June 20, 2025 by andy_nic

[flipthebit]

I mention Chrome as we install a specific version of it on build but it would update itself with the latest version automatically afterwards. I was wondering if it had enough time to update itself to the latest version which might be required by the google drive installer. Just a guess though.

[timbo343]

We often have it with ImperoClient but never the Google Drive for Desktop app, that always installs as part of the apps / task sequence.

 

We are currently pushing out GoogleDriveforDesktop 109.0.3.0

[synaesthesia]

Yeah, same version here. Impero does it now and then, but it's usually an oddity. Drive seems to have a paddy every time now!

Playing with chrome versions, as the app install task sequence even when run on an already deployed system tries to reinstall that, so worth a shout!

[synaesthesia]

Hit a bit of a blank with this, it seems to be heavily linked to the BDD process running it. The user running it, filtering levels etc don't have any effect (I checked filtering, HTTPS inspection etc as running without the silent flags & checking the google folder in programfiles86 showed it was stalling at the "updates" stage).

Instead I've just taken it out the application installer and just installed it as a command line in the task sequence which just works

[timbo343]

Update to this 109.0.3.0 fails for us too. I thought we were pushing the latest version earlier but obviously not. We were pushing 103.0.3.0 which worked fine, yet 109 doesn't and getting the same issue as @synaesthesia

[timbo343]

@synaesthesia Google Drive for Desktop 110.0.2.0 is now out, wonder if that fails during install via MDT task sequence - i'm yet to try.

[synaesthesia]

Ooh I'll give that a go at some point soon @timbo343 cheers  Will report back.

[timbo343]

On 15/07/2025 at 07:40, synaesthesia said:

Ooh I'll give that a go at some point soon @timbo343 cheers  Will report back.

Still doesn't work 🙃

[synaesthesia]

Joy Sorry, didn't get a chance to give it a go yet, but that's not a good sign. Thankfully installing directly via the task sequence is working for us, seems odd that it's necessary though!

[Techyboy19]

I had a similar issue with newer version hanging once installed and MDT therefore getting stuck. 
 

I installed the older version and hoped it would auto update. It installed but seems the update did not work and when a user logged into drive it told them they needed to upgrade. 
 

I have being using the below script to install. Create DriveInstall.bat and place it in the MDT Google Drive application folder and then in the Drive Install command on MDT point to DriveInstall.bat. 
 

@echo off
REM Silent install of Google Drive for Desktop for MDT
REM No desktop or G Suite shortcuts

SET INSTALLER=GoogleDriveSetup.exe

IF EXIST "%~dp0%INSTALLER%" (
    echo Installing Google Drive silently...
    "%~dp0%INSTALLER%" --silent --desktop_shortcut=false --gsuite_shortcuts=false

    REM Write date and time to C:\DriveInstalled.txt
    echo Google Drive installed on %DATE% at %TIME% > C:\DriveInstalled.txt

    EXIT /B 0
) ELSE (
    echo ERROR: %INSTALLER% not found in script directory.
    EXIT /B 1
)