Share via

Running setup.exe file from powershell produces different results than CMD

Shaunm001 306 Reputation points
2021-02-01T18:38:07.293+00:00

We're trying to run a setup.exe command (Adobe Acrobat installer) using PowerShell. When we run the command using CMD prompt, it automatically pulls configuration info from a setup.ini file in the same directory (no command switches or anything necessary).

When we run the same setup.exe command from PowerShell, for some reason it doesn't use the information in the setup.ini file, and so it runs the setup.exe process with no parameters.

If i use "Start-Process 'setup.exe'", then it will use the setup.ini file to grab the configuration settings, but when I put "Start-Process 'setup.exe'" into a script (my ultimate goal), I get an error message (see below). Anyone know the trick for running this setup.exe file from a PowerShell script so that it also calls the setup.ini file appropriately?

62627-untitled.jpg

Windows Server PowerShell
Windows Server PowerShell
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.PowerShell: A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
5,576 questions
0 comments
Accepted answer
  1. Shaunm001 306 Reputation points
    2021-02-01T19:21:50.733+00:00

    I figured it out...I'm using PSAppDeployToolkit to run the installer script, they have a custom PowerShell function "Execute-Process" that we're supposed to use in place of the standard "Start-Process" function.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.