Summary
Information on how to debug deferred ca in system contextSynopsis
The InstallScript Debugger checks the value of the ISSCRIPTDEBUG property to determine whether to debug the InstallScript in an installation. However, deferred, commit, and rollback InstallScript custom actions cannot access this property (or most of the Windows Installer properties). Therefore, the InstallScript Debugger ignores deferred, commit, and rollback InstallScript custom actions.This Knowledge Base article will show how you can debug these InstallScript custom actions, as well as custom actions running deferred in system context.
Discussion
In order to be able to use the InstallScript Debugger to debug deferred, commit, or rollback InstallScript custom actions, you will need to create a registry keys, based on the version of InstallShield you are using to build your setup.You will want to use 'regedit.exe' to create the following registry key...
For InstallShield 2015:
HKEY_CURRENT_USER\Software\InstallShield\ISEngine22.0
For InstallShield 2014:
HKEY_CURRENT_USER\Software\InstallShield\ISEngine21.0
NOTE: For earlier versions of InstallShield you can reference Knowledge Base article Q112187, which is linked at the end of this article.
In addition, a DWORD value called DebugISCustomActions with data 00000001 should be created under the key. This value enables you to use the InstallScript Debugger to debug deferred, commit, and rollback InstallScript custom actions.
NOTE: Even without this registry change, you can use the InstallScript Debugger to debug immediate InstallScript custom actions. If you do apply this registry change, the InstallScript Debugger launches for all InstallScript custom actions, regardless of what you have set for the ISSCRIPTDEBUG property.
Workaround
So the above changes to the registry will allow you to debug your InstallScript custom action in deferred, commit or rollback mode. However if you try to debug a InstallScript custom action running deferred in system context, the action will be run but the debugger won't appear.To fix this, you will have to make a modification to the registry by setting the debug registry key under a SYSTEM account. To do this, you can perform the following steps...
- Launch a command prompt as SYSTEM using psexec. You can take a look at PsExec v2.11 for more information on this.
- From that command prompt, run the command 'regedit' like so...
"C:\PSTools\psexec.exe" -i -d -s c:\windows\regedit.exe
- In the Registry editor that opens, set the debug registry key/value...
HKEY_CURRENT_USER\Software\InstallShield\ISEngine22.0
DebugISCustomActions(REG_DWORD) set to 1.
Now run your installation in debug mode and the debugger will appear for your custom action.
Related KB Articles
Q112187Was this helpful?
Related Articles
InstallScript Debugger Does Not Debug Deferred, Commit, or Rollback InstallScript Custom Actions 4Number of Views Difference Between Deferred Execution and Deferred Execution in System Context 9Number of Views Access SUPPORTDIR from an InstallScript Custom Action 6Number of Views Access SUPPORTDIR from a Deferred, Rollback, or Commit Custom Action 5Number of Views Create a 64-bit Windows Registry Entry via an InstallScript Custom Action 9Number of Views
Revenera Assistant - Beta
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