You are welcome, @poornisaran30.. I hope so, too.. Sounds good. You are welcome; we are happy to help. Please let us know if you have any questions or concerns. Thanks! ... View more

Hi @hkkim4, Thank you for your post. You could try the suggestion from Ajay_Ladsaria in the post at the following link: https://community.flexera.com/t5/InstallShield-Forum/Copy-files-into-installer-directory/m-p/53207 Please give this a try. Does this work for you? Please let us know if you have any questions or concerns. Thanks! ... View more

Hi @Christoph  As per windows error look up the error says the password is incorrect, since you are sure its correct password , try to sign your setup.exe using signtool and verify it signs successfully outside of installshield. https://learn.microsoft.com/en-us/dotnet/framework/tools/signtool-exe Are you facing the issue with only 2 dll's (Hardcodet.Wpf.TaskbarNotification.dll, CommonInstaller_dl.dll", ),if yes, then remove this dll's and then try signing and check signing works or If you selected sign files in packages option YES under signing tab, remove that option(meaning set it to NO) and verifying it sign the setup.exe Also try a sample project with your certificate and verify it works or not. and try to add this dll (Hardcodet.Wpf.TaskbarNotification.dll, CommonInstaller_dl.dll) in your sample and again try to build and verify it works or not,  You can also create a new support with active maintenance,  So Could you please navigate to Get Support > Open New Case in the top menu and open a new case to track this issue if you would like to proceed with having this issue addressed? That will allow us to best track this issue in order to best assist you.  ... View more

This is good news.  I'm happy to hear that worked, @FunkyDexter.  You're welcome; we're happy to help. ... View more

Hi @jafarm, Thank you for your post. Please accept our apologies for the delayed response. Our Engineering Team is reviewing this vulnerability and determining whether InstallShield is impacted. We'll keep you posted on our findings. Please let us know if you have any questions or concerns. Thanks! ... View more

Hello Ian, thank you very much for your message. Yes, it is true that the setup contains shared components that are not uninstalled. However, these are components that contain files that are installed into the GlobalAssemblyCache and are shared between different setups. The name of the component whose files are not uninstalled is OpenCascade and it has GUID {51280536-4FCD-47CB-88F3-4F2C7BFC8AFF}. In the log file you can see the following entry for this component: MSI (s) (14:88) [09:58:02:291]: Executing op: UnregisterSharedComponentProvider(Component={51280536-4FCD-47CB-88F3-4F2C7BFC8AFF},ProductCode={EAE4313E-14D2-44C1-82C8-C85A35C7D7FB}) MSI (s) (14:88) [09:58:02:291]: Executing op: ComponentUnregister(ComponentId={51280536-4FCD-47CB-88F3-4F2C7BFC8AFF},,BinaryType=0,) And here the part of the logfile where files are removed: MSI (s) (14:88) [09:58:04:635]: Executing op: SetTargetFolder(Folder=C:\Program Files (x86)\Procad\IntegrationHub\Modules\Operations\) MSI (s) (14:88) [09:58:04:635]: Executing op: FileRemove(,FileName=avcodec-57.dll,,ComponentId={51280536-4FCD-47CB-88F3-4F2C7BFC8AFF}) RemoveFiles: File: avcodec-57.dll, Directory: C:\Program Files (x86)\Procad\IntegrationHub\Modules\Operations\ MSI (s) (14:88) [09:58:04:635]: Note: 1: 2318 2: Here you can see that the directory is not set correctly: It is set by the installer to the value C:\Program Files (x86)\Procad\IntegrationHub\Modules\Operations\ but should have the value C:\Program Files (x86)\Procad\IntegrationHub\Modules\Operations\OpenCascade. For this reason, the files are probably not removed. See also my first post: The directory variable OPENCASCADE1 has a different value during installation than during uninstallation. Best regards Barbara ... View more

Hi @jerrym, Thank you for your post. Here is a link to documentation for InstallShield 2022 Express Edition with more information about how to build a single, compressed setup.exe with the InstallShield Express Edition: https://docs.revenera.com/isxhelp28/Content/helplibrary/IHelpISXBuildSingleFile.htm Please give the suggestions a try. Do they work for you? Please let us know if you have any questions or concerns. Thanks! ... View more

Hi @mauja32  Please try the below registry setting in a machine where Installshield is instaleld. InstallShield capture the COM registry information through a kernel driver, with the option "2" in registry setting. if the driver is corrupted, customer can uninstall the driver by executing below command [InstallShield Installed Location]\System\ISRegSpy.exe -uninstdrv Then reinstall the driver, by executing below command: [InstallShield Installed Location]\System\ISRegSpy.exe -installdrv If the problem persist even after reinstalling the driver, the continue the COM extraction with the registry setting "1". There is no difference, only the method varies UseAPIRegistryHooks registry value located in HKEY_LOCAL_MACHINE\Software\InstallShield\RegSpy key (on 32-bit machines) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\InstallShield\RegSpy key(on 64-bit machines) holds the method configured to extract the COM information. Value Description 0 COM information captured by hooking Windows Registry API, old method. 1 COM information captured through Registry redirection API 2 COM information captured through Kernel mode registry filtering, latest method introduced in InstallShield 2012. Need to execute in Admin cmd prompt https://docs.revenera.com/installshield26helplib/helplibrary/whats_newIS2012.htm?Highlight=UseAPIRegistryHooks%20registry%20value%20located ... View more

You are welcome @bradw0007! Sounds good. Please let us know if you have any questions or concerns. Thank you! ... View more

Hi All, Please give this .prq a try. It should address the problem with .net 7.0 being installed, while still prevent installs when 6.X versions are present. We hope it helps. Thank you. ... View more

Hi Gary (@Dawgzilla), Thank you for your post. No, InstallShield 2016 does not support integration with Visual Studio 2022. So far, only InstallShield 2022 R1 supports integration with Visual Studio 2022, in phases. Here is a link to documentation with more information: https://docs.revenera.com/installshield28helplib/rn/Content/helplibrary/Visual_Studio_2022_Integration.htm#isreleasenotes_3104246582_1259421 So in summary, yes, you would need to upgrade to InstallShield 2022 R1 for support for integration with Visual Studio 2022. Please submit our Contact Us Form at the following link to request more information about upgrading to InstallShield 2022 R1: https://www.revenera.com/about-us/contact-us Please let us know if you have any questions or concerns. Thanks! ... View more

To add some additional information here: As we are dealing with the creation of Installations, access to restricted areas of the machine are required for Installshield to work correctly. Without administrative privileges the following functionality within Installshield would fail: COM Extraction, Redistributable downloading, Ability to specify All Users locations for InstallShield prerequisites, Ability to specify All Users locations for merge modules, Ability to edit the locations for Regasm.exe and InstallUtilLib.dll, Ability to specify the frequency for checking for InstallShield updates In addition mapped drive locations may encounter issues depending on the privilege context they were created and the context Installshield attempted to access them. ... View more

Hi @johnemmatty, Thank you for your post. Do you, perhaps, have more than one major upgrade item, under Releases, that has the same Action Property as another major upgrade item(s)? Please take a look in your project settings and let us know. Please let us know if you have any questions or concerns. Thanks! ... View more