Summary
1603 Error occurs with a powershell custom action after upgrading to InstallShield 2015 or above.Synopsis
InstallShield allows you to create a powershell custom action and launch it from your installation. If you migrate an older project into InstallShield 2015 or above, your previously working powershell custom actions may now fail with a 1603 error. This knowledge base article will explain a possible cause as to why this behavior is occurring and how you can resolve it.Discussion
If your powershell script contains a Write-host command, this was ignored in previous versions of InstallShield. However in InstallShield 2015 and later, the Write-host call will cause an error since it is for hosts that support user interaction (...Basic MSI or Suite-hosted powershell scripts are not meant for user interaction, since both Basic MSI and Suite projects have their own preferred methods for user interaction).Workaround
If you can simply remove your calls to Write-host in your powershell script, this alone should resolve the error. However if you have a number of Write-host calls in your powershell script, then you can workaround this by overriding Write-Host with functions that do nothing. For example, this can be done once at the top of your powershell script...function Write-Host {}
# optionally others such as: function Write-Verbose { }
...
Write-Host "Blah" # does nothing
...
Was this helpful?
Related Articles
Passing Argument To Powershell Custom Action 6Number of Views Use PowerShell to Create a Project and Add a PowerShell Custom Action Using the InstallShield Automation Interface 14Number of Views Update the Progress Bar from a Custom Action at Runtime 5Number of Views PowerShell Custom Action Quotation Marks 5Number of Views Passing Parameters to a Powershell Custom Action 3Number 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