Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

PDQdeploy + AutoIt Problem


i have a problem with pdqdeploy. I want to use it to deploy a certain software. Therefore i have build a autoit-scrip. The script itself works perfectly, the software installs with the correct parameters. Now i want to deploy the software to many clients using PDQdeploy (i can't use group policy, because its not within a domain). Problem is, when it deploy it, on the target-pc the script starts, then also the installer starts, I can see all that in the task manager. But i can't see anything happening on the screen, the GUI of the installer does not show up. An the threads don't finish, so the software won't install. That's weird because when i run the script manually on the target, it works without any problem.

I also tried to deploy with a batch file, that copies script and the Installer to a certain location and the runs it - same problem.

Then i created a self-extracting Archive with the script and the installer, that extracts the script and the Installer to a certain location and the runs it - same problem.

Do you have a solution fo this? can you tell me why the autoit-script doesn't work only in case it is deployed via PDQdeploy, not even with the batchfiles or the SFX-Archive?

Has anyone tried or managed to use these both softwares combined?

Thank you very much for your feedback.

Greets Simon



Date Votes
  • AutoIT scripts are becoming more popular as of recent. They do pose some challenges when attempting to run via an remote solution. Are you using the same account to install via PDQ Deploy that you are using when running manually? Will you please email your autoit script to and we'll see what we can do. In the email to support please provide info on the application that you are running/configuring via your script so that we can try and replicate in our lab.


  • Software that is run remotely, like with PDQ Deploy, runs in the background and won't be visible on the screen.  This is a security limitation of Windows.  If the software displays a window and is expecting some user input (such as to click on a button) then the software will appear to hang as it won't be possible for a user to respond.  It's the most common cause of hanging installers with PDQ Deploy.

    The solution therefore is to determine the silent method of installing the software that you are deploying.

  • Simon,

    What's most likely happening is that the Divxinstaller is displaying differently when run in the background, so that the script is stuck waiting for a window to appear that never does.

    You can add some tracing lines to the script to see where it's failing, for example:

    ConsoleWrite("Start" & @CRLF) 
    Opt("WinTitleMatchMode", 2)
    ConsoleWrite("DivXInstaller.exe" & @CRLF)
    ConsoleWrite("Sleep" & @CRLF)
    WinWait("Sprachenauswahl", "Wählen Sie Ihre Sprache.") 
    ConsoleWrite("WinWait 1" & @CRLF)

    ... etc ...

    Then capture the output from the script:

    autoit3.exe DivX.au3 > c:\trace.txt

    This will tell you where the script is failing, which should help to pinpoint what change needs to be made.