On Windows 7 and Vista, and with the User Account Control (UAC) enabled, the PADS9.3 and PADS9.3.1 installations can take upwards of a few minutes to scan the ~1.5GB installation executable, before the UAC prompt appears. The delay can be even greater when installing over the network or from DVD.
You can tell it’s the UAC causing the delay (and the installation has not stopped or hung), when you can see a “consent.exe” process running in Task Manager (processes tab) and the amount of CPU it is using is greater than 0.
Workarounds to speed up the start of the PADS9.3 and PADS9.3.1 installations:
- Create a VBScript wrapper script which first elevates the UAC and then runs the PADS installation executable.
- Below is a sample script where the PADS executable resides on a server (\\myserver)
- Edit the full path to the executable inside the double quotes after "filePath = ".
- The path shown in the example below is a UNC (network) path. However, it could also be a location on the local hard drive such as "C:\temp\PADS9.3.1_mib.exe"
- Save the file with a .vbs extension so that Windows understands it is a VBScript.
filePath = "\\myserver\installs\PADS\PADS9.3.1_mib.exe"
Set objShell = CreateObject("Shell.Application")
objShell.ShellExecute "cmd.exe", "/c " & filePath, "", "runas", 1
- If you are installing from a network location or DVD, copy the file to a hard drive that is local to your machine, and execute from there.
- Right mouse click on the “Command Prompt” icon in the Start Menu (under "Accessories") and select “Run as Administrator”. Run the “PADS9.3.1_mib.exe” from the command line.