Uninstall application with original MSI

I'm trying to create a package to uninstall an application that was "cleaned up" when installed, so using the GUID to uninstall isn't an option. How would I set up a package to use the original MSI installer to uninstall the application?

 

Using PDQ Deploy 12 Pro Mode

0

Comments

16 comments
Date Votes
  • It's the same as using the GUID.

    msiexec /x application.msi /qn /norestart

    If you run "msiexec /?" it will pop open a mini help window.



    0
  • I guess I should've elaborated a bit more. The original MSI doesn't reside on the target machine anymore, so I need to be able to push it out to the target to use in the uninstall command. That's where I'm having issues. I keep receiving error code 1612:

    “C:\Windows\AdminArsenal\PDQDeployRunner\service-1\exec>MsiExec.exe /qn /norestart /X "application.msi"

    The installation source for this product is not available. Verify that the source exists and that you can access it.”

    0
  • Do you have the original msi file? If you do, use an install step with that MSI file, and specify an /X not an /I. Pain in the butt, I know, but that might be how it needs to be done.

    0
  • Yeah, I do. That's what I was starting to think was going to be the solution. I'll try that. Thanks

    0
  • Hmm...I'm still getting the same error even when using an install step with /x instead of /i. I'm using this custom command in the install step:

    msiexec.exe /x "application.msi" /qn /norestart

    I still receive error 1612 back.

    0
  • Post a picture of your install step please.

    0

  •  

    0
  • Is that installer looking for additional files? Some products like Microsoft Office require the "Include Entire Directory" option.

    0
  • Not that I'm aware of. That's the only file that was ever provided to us. It's a browser plugin to interface with credit card readers.

    0
  • Hmm, it looks like it should work. How about installing first?

    0
  • I'm thinking there might be something else going on with this particular version of the plugin. I can't even install it. Still getting the MSI 1612 error.

    0
  • Hi Rob, you might check the "Fix problems that block programs from being installed or removed" article and FixIt tool from Microsoft.

    0
  • Have you made any headway on this?
    I have a PowerShelly suggestion if the msi hasn't cooperated yet.

    0
  • Yep, still no luck.

    0
  • If you have PDQ Inventory and a test environment, you could use the remote command tool to send out the Get-Package PowerShell cmdlet. (To make the results more readable in Inventory's results pane, you might want to use "Get-Package | ft name,version" to avoid excessively long summaries of MS packages.)

    If the plugin shows up in the list, you should be able to target it with the Uninstall-Package cmdlet. (Uninstall-Package -Name "Application Name"). I'd recommend setting the Scan-After setting to "Applications" as long as the plugin shows up in the PC's Applications list in Inventory.

    If it does show up in Get-Package and can uninstall correctly with Uninstall-Package, you could build a Deploy package with the Uninstall-Package line as a PowerShell step.

    However, Uninstall-Package can be hit or miss so it might not work--I've used it with mixed results in the past.

    0
  • Well, I think I just discovered the reason why none of these methods are working. Looks like the original installer doesn't actually work. I'll have to get with our vendor to see if they have another version that does work.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post