silent unisntall with st6unst then silent install a setup bootstrap for visual basic setup toolkit FAIL

What I am trying to acheive is fairly simple,

Ideally in 1 deployment, but could be done in 2 steps,

Have an old software that runs on vb6. And I want to do a Silent uninstall first with this "Visual Basic 6 Setup Packages" on all computers that have them installed.

This works fine, locally. I have tried as a batch file, and as an elevated command promp string.

This is the line I use on my computer:

%systemroot%\st6unst.exe -n "C:\Program Files (x86)\xxx\st6unst.log" -f -q

Works perfectly fine!

Thi stakes about 3 seconds to uninstall everything. (as a batch file or as cmd prompt).

But as soon as I create a deployment, add a command step, using the "deploy user", It hangs, and have to abort the deployment.

Tested after to run it with the "logged on user" and it forks fine, on my computer, as I am the admin of it.

But Am trying to push this to users that aren't admin, using the "deploy user".

And the deploy user is installed as an admin on all of our machines...

Once uninstalled, during the samne deployment, I would put a pause of 5-10 seconds, and then run the installation of the new version of this software using command prompt aswell.

Again, this works fine locally to install this Visual Basic 6 Setup Packages.

I use this line either as a batch file or in an elevated command prompt:

C:\Users\xxx\Desktop\xxx\setup.exe /sc:\abcd.log

And again, takes about 30 seconds to install silently. But fails using PDQ deploy.

I read both of the articles in your forum that touch this, but there is no clear answer as if this is feasable or not.

Coudl you please halp me out with this issue ??

Again, thanks for your collaboration !!



Date Votes
  • Please post screenshots of your package steps. This should work.


  • 0
  • Try separating your parameters

    /s c:\eesinstall.log
  • Typically writing to the root of C:\ requires you to enter admin credentials in an UAC prompt if the user isn't an admin of the machine. Is there another directory you could write that logfile too?

  • @Colby, tried with and without space, all run as modes, don'T work

    @Stephen, all of my computer have the deploy user as a domain admin on the machine.


    Like I explained in the original post, it works flawlessly with the run as admin cmd prompt running those 2 line :

    install silently : C:\Users\xxx\Desktop\xxx\setup.exe /sc:\abcd.log
    uninstall silently : %systemroot%\st6unst.exe -n "C:\Program Files (x86)\xxx\st6unst.log" -f -q



  • Okay, found a solution that worked like a charm...

    With the help of the PDQ Support team, decided to try and script this instead and see if the results were different.

    So, created a package that copies over the installation files to some directory like C:\Temp\xxx\ on the target machines.

    Next, created a simple batch script that runs the commands :

    @echo off
    c:\temp\xxx\setup.exe /sc:\temp\ees\123456.log

    This worked like a charm.

    After, I created a step for uninstallation, before the 2 other steps.

    It failed at first, but tried to do a batch file with the line of code:

    @echo off
    %systemroot%\st6unst.exe -n "C:\Program Files (x86)\xxx\st6unst.log" -f -q

    This failed with error code 1.

    Added code 1 to the success codes and now have a working uninstall and installation deployment!

    Thanks again for your help!!!! We did it !!!


Please sign in to leave a comment.

Didn't find what you were looking for?

New post