Summary
Discussion of a variable representing the Update.exe name during initialization.Synopsis
Trying to obtain the equivalent of SETUPEXENAME for the Update.exe for a Patch Update is not nativly supported. Furthermore, the variable SETUPEXEDIR returns blank when running a MSI based patch.Discussion
SETUPEXEDIR is an alternative to the directory identifier SourceDir. A potential problem with using SourceDir is that it points to the location of the running .msi package. In the case of a compressed installation, the .msi package is streamed to a temporary location and run from there. Because of this, the value of SourceDir will be some temporary location on the end user?s machine, which might not be the value that you want.The CURRENTDIRECTORY property will likely return the directory where the Update.exe is but not its name.
Workaround
Use custom .Net to examine every process to look for a process name of "msiexec" and then into their Command Line parameter to check for SETUPEXENAME and SETUPEXEDIR which are used to start the process.Find the current process using the System.Diagnostics Namespace yields the msiexec.exe process which is fired from the setup.exe. This is not expected to yield the SETUPEXENAME or the SETUPEXEDIR.
Related KB Articles
Please reference:SETUPEXEDIR
Was this helpful?
Related Articles
InstallScript MSI Major Upgrade Results in "Setup Launcher Unicode Has Stopped Working" 10Number of Views An Error 1601 or 1719 May Occur After Installing the MSI 3.1 Engine with InstallScript MSI Projects 3Number of Views Windows Installer Property PATCH - Working With Conditions in a Basic MSI Specific to a Patch Install 3Number of Views Perform Major Upgrade of InstallScript MSI Project with Basic MSI 3Number of Views Warning-7065 Windows Installer 3.1 Engine could not be found, while creating a patch and "Error reading setup initializati… 11Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago