InstallShield Knowledge Base

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Summary FLEXnet Connect is a solution that Flexera Software sells to software vendors that is designed to help you stay connected with your customers after they install your applications. Synopsis FLEXnet Connect is a solution that Flexera Software sells to software vendors that is designed to help you stay connected with your customers after they install your applications. Keeping software updated is one of the many benefits of FLEXnet Connect, but Flexera Software also recommends that software vendors build in an option to disable automatic update checking. If you are using an application that uses FLEXnet Connect, your application may have a configuration option to disable update checking. Please check your application?s menu options. If your application does not have this option, Flexera Software has created a tool called the Software Manager that can disable automatic update checking. The Software Manager utility lists all applications currently using FLEXnet Connect on your computer and the FLEXnet Connect's status with that application. Discussion You may already have the Software Manager installed. If the Software Updates or Program Updates shortcut is listed in your Start menu, then the Software Manager is installed. If you do not have the Software Manager installed, follow these instructions to download and install it: Download and install the Software Manager: Download the latest FLEXnet Connect 6.1 Software Manager and save it to your Desktop. The latest FLEXnet Connect Software Manager can be downloaded here. 2. Double click on the FLEXnet connect executable and follow the instructions to install the Software Manager. Once installed, you can run the Software Updatesshortcut to start the Software Manager. Download and install the uninstall for Software Manager: Download the Update Manager uninstaller and save it to your Desktop. 2. Double click SoftwareManagerUninstall.exe and follow the instructions to uninstall the Software Manager. Note: The SoftwareManagerUninstall.exe only removes entries from the Windows registry which are responsible for starting the common software manager after a reboot. No files are actually removed.
View full article
Summary This error message is a system-specific error and can be caused by a system-specific setting. This article attempts to list all the possible steps that have known to resolve this error. Symptoms When running an installation created with an InstallShield product, the following error occurs at the beginning of the installation: Error -1607: Unable to Install InstallShield Scripting Runtime This error message is a system-specific error and can be caused by a system-specific setting. This article attempts to list all the possible steps that have known to resolve this error. Depending on your system, you may need to try some or all of the listed solutions. Cause This does not occur with InstallShield 12 and later. The architecture in InstallShield 12 and later has several advantages over the earlier architecture. End users no longer encounter error 1607, error 1608, or other COM/DCOM run-time errors that are related to finding the running IDriver.exe file. When these errors occurred under the earlier model, they were difficult to resolve, often requiring changes to DCOM settings. Also, the reliance on the running object table made the model brittle across the spectrum of usage scenarios, including Fast User Switching and Windows Terminal Services. Resolution Update the ISScript engine on your computer by downloading the latest one. For more information, see Setup Is Unable To Find or Update ISScript.msi. Make sure that the Installer folder in the Windows directory has full access privileges. The Installer folder may be hidden on your computer, so you will have to set your computer to see hidden files and folders and then set the proper permissions to the <WINDOWSFOLDER>\Installer folder: A. Show Hidden Files and Folder Launch Windows Explorer by pressing the Windows key + E or select Start > Run and typeexplorer. Select Tools > Folder in the Windows Explorer window. Select the View tab. In the Advanced Settings pane, select Show hidden files and folder. B. Set the Installer folder attributes Locate the folder <WINDOWSFOLDER>\Installer: Windows NT and 2000: C:\WINNT\Installer Windows 95/98/Me/ XP: C:\Windows\Installer Note: In some instances this directory doesn't appear on Windows XP machines. Follow these steps to view the folder: a. In Windows Explorer select View > Toolbars and select Address Bar if there isn't a check box next to it. b. In the Address Bar type in the full path: C:\WINDOWS\Installer. 2. Right-click on the Installer folder and choose Properties. 3. Select the Security tab. 4. Make sure the System, Administrators and the specific user have Full Control of this folder. C. Repeat the instructions in Step B for the Temp directory. To locate the Temp directory on your machine, refer to the article Clean the Temp Directory. 3. Make sure that the InstallShield registry key in the Windows registry has full access privileges. Select Start > Run and type regedt32. Browse to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield Check the permissions of this key: Windows XP users can right click and select Permissions. Windows 2000 and NT users navigate to the Security menu and select Permissions. 4. Assign both the Administrators and System group Full Control if they don't already have it. For an idea of what the permissions property dialog will look like, see step 2B-4. 4. If the installation is located on a network drive, copy all of the files to the local hard drive (i.e., Desktop or Temp directory) and attempt to run the installation again. 5. Install the Windows Installer engine on your computer to make sure that it is not corrupt and that it is properly registered on your computer. For more information, see How Do I Install the Windows Installer Engine on My Computer Using InstallShield. 6. Make sure you have full administrative privileges on your computer. This does not apply to Windows 95, 98, and ME. 7. Make sure no other applications, installations, or processes are running in the background. For more information, see Manually Detect and End Previously Running Installation Process and Close Applications Running in the Background . 8. Make sure to check the location from where the installation is being run. If the downloaded installation files are stored in a directory path that contains special characters, such as "&", "-", ".", etc, change the path to something that does not contain these characters. Bad path: C:\downloads\Palm\palm desktop & hotsync\x\setup.exe Good path: C:\downloads\Palm\palm desktop hotsync\x\setup.exe Does Your Issue Still Exist? If after following these instructions your product failed to install, you'll need to contact your vendor. See the Who to Contact page for more information. Related KB Articles Q108353 Q108373 Q108351 Q108345 Q108213 Q111114
View full article
Summary: Setting DSN info for a SQL ODBC connection.   Description: Creating a new DSN will populate some base Properties and Values in Installshield's ODBC Resources view for the DSN. However, you will likely want to setup the ODBC to use certain attributes, such as Server. Those Attributes would be ODBC specific attributes not Installshield specific. Information on such attributes may be found externally.   Additional Information: Such as these for SQL ODBC connections: https://docs.microsoft.com/en-us/sql/connect/odbc/dsn-connection-string-attribute?view=sql-server-ver15  
View full article
Symptoms: When you are building an InstallShield MSIX project, the following warning may occur: warning -9583: Restricted capabilities like localSystemServices and packagedServices are only needed if your MSIX project is configured with windows.service extension. Diagnosis: This build warning occurs when above capabilities are selected in Capabilities view and windows.service extension is not included in the package. Solution: Check if windows.service is configured in the package and try one or more of the following steps to resolve the issue: If no service is added in the MSIX package, manually unselect above mentioned restricted capabilities from Capabilities view. If service declaration is added, then make sure corresponding declaration set is selected for a given application entry in the Applications View. Additional Information The restricted capabilities localSystemServices and packagedServices allows applications that are created by Microsoft partners and enterprises to declare the windows.service extension in its package manifest so that it can install one or more services along with the app. These services can be configured to run under the Local Service, Network Service, or Local System accounts. Local Service and Network Service services only require the packagedServices capability. Local System services require the packagedServices and localSystemServices capabilities.
View full article
Symptoms: When you are building an InstallShield MSIX project, the following error may occur: error -9582: MSIX services configured to run under the Local Service or Network Service accounts require the packagedServices restricted capability. Diagnosis: This build error occurs when windows.service extension is configured with Local Service or Network Service as startup account type and does not have packagedServices capability included in the package. Solution: To fix above error, select 'Packaged Services' restricted capability from MSIX project Capabilities view.
View full article
Symptoms: When you are building an InstallShield MSIX project, the following error may occur: error -9581:  MSIX services configured to run under the Local System account require the packagedServices and localSystemServices restricted capabilities. Diagnosis: This build error occurs when windows.service extension is configured with LocalSystem account as startup account type, and does not have the following capabilities included in the package: packagedServices localSystemServices Solution: To fix this error, select above restricted capabilities from MSIX project Capabilities view.
View full article
Symptoms: When you are building an InstallShield MSIX project, the following error may occur: warning -9580: This package has services configured. Hence, updating TargetDeviceFamily versions to minimum supported operating system version (Windows 10, version 2004, build number 19041). Diagnosis: Windows 10, version 2004, introduces support for running an MSIX package that includes services. Hence Target Device versions will be updated automatically by InstallShield if MSIX package contains NT service (windows.service extension).  Solution: This warning can be ignored if no changes are required for TargetDeviceFamily versions defined in the manifest file. To override default behavior, configure ‘Include Desktop Extensions’ property in Releases view as required.
View full article
Symptoms: Error -9579: MSIX packages with services support is available starting with Windows 10, Version 2004 (build number 19041). Hence, Target Device versions need to be configured accordingly. Packages targeting MSIX features that are not available in specified TargetDeviceFamily versions may not work as expected. App Installer may throw the error. Diagnosis: Windows 10, version 2004, introduces support for running an MSIX package that includes services. Hence Target Device versions need to be configured accordingly if MSIX package contains NT services (windows.service extension). Solution: Configure ‘Include Desktop Extensions’ property in Releases view to have right values or leave these values as blank to let InstallShield automatically configure these values while creating MSIX manifest file.
View full article
Symptoms: ISDEV : warning -9578:  Services configured with dependencies outside the MSIX package are not currently supported by Microsoft. '%1' is not a valid Dependency Service. %1 is a placeholder that contains the dependency name (referred as part of windows.service extension) causes this warning. App Installer may throw weird error if definitions for dependency service names are not included as part of MSIX package.  Diagnosis: This build warning is shown when Dependency Services are configured in windows.service extension and the same is not included as part of the MSIX package. Windows 10, version 2004, introduces support for running an MSIX package that includes services and this release currently does not support services with dependencies outside the package. Solution: One or more of the following steps resolve the issue: Remove either dependency names or create new windows.service extension for referred dependency service name. Check Microsoft latest documentation on MSIX services and see if this limitation is addressed in the latest release.
View full article
Symptoms: During a build, you receive the following build error: ISDEV : error -9577: Error building Modification Package. Base Package Name in General Information view is empty. Diagnosis: This build error has been triggered when building modification package project with base package name is empty. Base Package name is mandatory when you create a modification package that has a strict binding to the main app. Solution: To resolve this build error, set the main package identity name as Base Package Name in General Information view.
View full article
Summary The FilesInUse dialog can be disabled with the addition of a MSI property and light changes to MSI tables. Synopsis The FilesInUse dialog can be disabled with the addition of a MSI property and light changes to MSI tables. Discussion In order to disable the FilesInUse Dialog you will need to make a couple changes to your project. 1. Add a MSIRESTARTMANAGERCONTROL property to the Property Manager and set its value to Disable 2. Go to the Direct Editor View in Installation Designer and navigate to the Dialog Table. 3. Find the FilesInUse Row and clear out the Attributes column for it. It should be empty. These steps should disable the Restart Manager and set it to use the FilesInUse dialog. And clearing the Attributes column should prevent the FilesInUse dialog from displaying. Note: If the applications that are in use have a UI still open, a Restart Manager dialog may still appear when using the Uninstall button from Programs and Features. But the Restart Manager dialog may not appear on install or using Maintenance and the Remove Radio button. Additional Information MSIRESTARTMANAGERCONTROL property (MSDN)
View full article
  InstallShield MSIX Bundle Utility helps to create the MSIX Bundle package, it lets you specify the payload MSIX packages and the signing information through the graphical interface and creates the MSIX bundle package from the configured MSIX packages. During the build, it validates MSIX packages for their consistency across the Package identity such as name, publisher, and version. If any mismatch found during the MSIX bundle build, then the build ends with the appropriate error information. Apart from the Package identity, it validates the package architecture like there is only one MSIX package belongs to one specific architecture and checks if there any MSIX package with architecture “Neutral” configured with other architecture packages. In case of “Neutral” package, it is not allowed to bundle with other architecture packages. If any violations found, then the MSIX bundle build ends with the appropriate error information.   InstallShield MSIX Bundle Utility Errors and Resolutions   “Failed to create MSIX Bundle. All Packages to build a MSIX bundle should have the same Package name” InstallShield MSIX Bundle Utility does not bundle the MSIX packages when the Package name is inconsistent. For example, the MSIX package identity ‘Name’ should be same across all the payload MSIX packages to bundle the MSIX packages by the MSIX Bundle Utility. In case if the ‘Name’ is inconsistent across the payload, it must be fixed. To fix this error, reconfigure the payload MSIX packages or modify the MSIX packages to have the same Identity Name.   “Failed to create MSIX Bundle. MSIX Package publisher name should be the same to create an MSIX bundle.” InstallShield MSIX Bundle Utility does not bundle the MSIX packages when the Package publisher name is inconsistent. For example, the MSIX package identity ‘Publisher’ should be same across all the payload MSIX packages to bundle the MSIX packages by the MSIX Bundle Utility. In case if the ‘Publisher’ is inconsistent across the payload, it must be fixed. To fix this error, reconfigure the payload MSIX packages or modify the MSIX packages to have the same Identity Publisher.   Failed to create MSIX Bundle. MSIX Package versions should be the same to create an MSIX bundle. InstallShield MSIX Bundle Utility does not bundle the MSIX packages when the Package version is inconsistent. For example, the MSIX package identity ‘Version’ should be same across all the payload MSIX packages to bundle the MSIX packages by the MSIX Bundle Utility. In case if the ‘Version’ is inconsistent across the payload, it must be fixed. To fix this error, reconfigure the payload MSIX packages or modify the MSIX packages to have the same Identity Version.   Failed to create MSIX Bundle. The packages selected are targeting the same architecture. InstallShield MSIX Bundle Utility throws this error only if multiple payload MSIX packages targets one specific architecture. MSIX bundle is not supported to add multiple packages targets same architecture inside the bundle. To fix this error, add only one specific architecture package in the payload MSIX packages.   Failed to create MSIX Bundle. Package [Package Name] has architecture set as [Architecture] which is not supported for building MSIX Bundle with ‘Neutral’ architecture Package. InstallShield MSIX Bundle Utility throws this error only if the payload MSIX packages contain packages targeting “Neutral” architecture and other architecture specific packages. MSIX bundle is not supported to add “Neutral” architecture package with other architecture specific packages inside the bundle. To fix this error, add only “Neutral” architecture package or other architecture specific packages in the payload. Mix of “Neutral” and other architecture specific packages are not supported.   Failed to create MSIX Bundle. The minimum version of target device for building MSIX Bundle is '10.0.17763.0'. InstallShield MSIX Bundle Utility throws this error if anyone of the payload MSIX package target device family min version is less than '10.0.17763.0'. MSIX bundle is not supported to add packages with target device family min version less than '10.0.17763.0'. To fix this error, ensure all the pay load packages target device family min version is configured to '10.0.17763.0' and above.   Failed to Sign MSIX Bundle with Error code  InstallShield MSIX Bundle Utility throws this error if the MSIX bundle package failed to sign after the successful build. Signing errors come due to the invalid signing information, such as invalid password or invalid certificate info. So, reconfiguring the signing information with valid info resolve the signing error.  Error code also point the root cause of the signing error, which is Microsoft standard signing error code.  
View full article
Summary ?????????????InstallShield ???????????????????? Synopsis InstallShield ?????????????????InstallShield ???????????????????????????????????????? ?????InstallShield ???????????????????????? ????????????????????????????????? InstallShield ??????????????????????????? ????????????????? ??Related KB Articles ??????????? [The English version of this KB article can be found in the Related KB Articles section below .]   Discussion InstallShield ????????????????????????? InstallShield ?????????? ? ????? 14 ????? InstallShield ?????????? 14 ???? InstallShield ???????????????????????????? InstallShield ??????????? InstallShield ?????????????????????????????????????????????? ???????????InstallShield ? [???????] ????? ???????????? [???????] ????? ??????????????InstallShield ? [???] ????? [???????] ????????? InstallShield ????????????????????????? ? InstallShield ???????????????????????????? 5 ????????? ????????????????????????????????????? InstallShield ??????????????????????????????? ?????????????????????? 5 ??????? ?????????????????????????????? ?????????? ? InstallShield ??????? Setup.exe ??????????????????????????????????????? Windows Installer ???????????????.msi ????????? Setup.exe ?????????????? ??????????????????????????????????????????????????????InstallShield ???? -7211: ?????????? ???? Setup.exe ????????????????????????? ????????????InstallShield ???????????????? ??? ??????? ? ??????InstallShield Premier Edition ? [????] ??????????? [????] ???????? "????????" ????????? ?????????????????????????????InstallShield ??????????????????????????: ?? -7211: ?????: ??????? ??????????????? ????????????? InstallShield Premier Edition ??????????? InstallShield ? .msi ???????? .cab ???????????????????????????? ??????? .cab ????? .msi ????????????????.msi ????????????????? Setup.exe ????????????????????? ????????? MSI ??? InstallScript MSI ?????????????? ??? InstallShield 2011 ????????????????????????????? Setup.exe ?????????? ? /a ??????? ???????InstallShield ?????????? Setup.exe ???????????????????? ??????????? Setup.exe ??????????????????? InstallShield ????????????????????????????????? MSI ???????????????????????InstallShield ????????????????InstallShield ????????? Q200900 ??????????????????????????? ???????????? InstallShield ? /a ????????????Setup.exe ??????????????? ????????????? ??????????????????????????????????? ??? ?????? QuickPatch ???????? ? ??????InstallShield ?????????? Setup.exe ?????????????? QuickPatch ?????????????????? InstallShield ?????????? Setup.exe ???????????????????? ???????????????????? * [????????] ??? (InstallShield Premier ??? Express Edition) * ?? QuickPatch ??????? (InstallShield Premier?Professional???? Express Edition) ????????: ?????????? InstallShield ????????????????????????????????? MSI ???????????????????????InstallShield ????????????????InstallShield ????????? Q200900 ??????????? ??: InstallShield ??????????????????????????????????????? InstallShield ??????????????????????????????????? Related KB Articles Q200900
View full article
Summary InstallShield 2010 以降のノードロック型のライセンス機能は、旧バージョンの InstallShield で使用されていたノードロック型のライセンス機能の比べ、より高い柔軟性があります。 Synopsis InstallShield 2010 以降のノードロック型のライセンス機能は、旧バージョンの InstallShield で使用されていたノードロック型のライセンス機能の比べ、より高い柔軟性があります。 InstallShield 2010 以降では、ライセンスは特定のマシンに完全に固定されないため、ユーザーは、ハードウェアおよび InstallShield がインストールされているマシンを定期的に更新したり取替えたりすることができます。 この記事では、アクティベーションに関する概念および用語が説明されています。 また、InstallShield 2010 以降のノードロック型のライセンスのアクティベーションに関する具体的な時間枠およびその他の情報も提示されています。 Discussion アクティベーションに関する概念および用語の定義は次の通りです:   ノードロック型ライセンス   モデル   — このモデルでは、製品ライセンスは特定のユーザーとマシンに固定されています。 このモデルは従来型のオプションで、最も頻繁に購入されています。 ノードロック型のライセンスを使用している場合、マシンに保存されている個人のライセンスは、ユーザーの責任で管理してください。 複数のユーザー間でこの種類のライセンスを共有することは、 InstallShield エンドユーザー使用許諾契約書 (EULA) に違反します。   同時使用ライセンス   モデル   — このモデルを使用すると、 InstallShield のライセンスを複数のユーザーと共有したり、浮動状態にしたりできます。このモデルは、浮動ライセンスとも呼ばれます。 同時使用ライセンス機能は、従来型のノードロック型ライセンス機能にくらべ、より高い柔軟性と費用対効果を提供します。 組織で購入された InstallShield のライセンスが同時使用ライセンスの場合、 InstallShield をマシンにインストールするとき、使用するライセンス サーバーの情報が必要になります。 この後、 InstallShield を自分のマシンで起動するたびに、サーバーが呼び出され、必要なライセンスが使用可能であることがクエリされます。 ライセンスが使用可能な場合、 InstallShield へのアクセスが許可されます。 同時使用ライセンス機能では、製品のアクティベーションは必要ありません。 このライセンス機能モデルに関する情報と、ニーズに一番適したライセンスの選び方については、 InstallShield セールス担当者にお問い合わせください。   アクティベーション   — アクティベーションとは、使用中のソフトウェアが正規のものであることを確認するプロセスです。 このプロセスは、不正にコピーされたソフトウェアがもたらす悪影響からお客様を守るために行われます。 プロセスでは、 InstallShield が InstallShield のエンドユーザー使用許諾契約書 (EULA) で許可されている数を超えるマシンでアクティベートされていないかどうかも検証されます。 InstallShield が初回で起動されたとき、アクティベーション ウィザードが開きます。 数秒後に、何もクリックされなかった場合、アクティベーション ウィザードは閉じ、 InstallShield が完全に機能するトライアル製品として起動します。 InstallShield をすぐにアクティベートする場合、 [InstallShield をアクティベートまたは購入する ] オプションを選択して、 [ 次へ ] ボタンをクリックします。 ウィザードの案内に沿ってアクティベーション プロセスを完了すると、数秒で InstallShield がアクティベートされます。 インターネットの接続がない場合、またはオンラインで検証を実行するのが困難な場合、電子メールを使ってオフラインでアクティベートするオプションがアクティベーション ウィザードで提供されます。   再アクティベーション   — 再アクティベーションは、アクティベート済みの製品が InstallShield の EULA に従ってインストールされているか、また、アクティベーションの実行が許可されている数を超えていないかを確認するプロセスです。 再アクティベーションは、 InstallShield が正常にインストールおよびアクティベートされているすべてのマシンで必要になります。再アクティベーションを忘れた場合、 InstallShield は動作しなくなります。 再アクティベーションは、再アクティベーションを必要としないライセンス機能モデルにくらべ、より高い柔軟性を持ちます。 InstallShield に使用されている再アクティベーション モデルでは、ライセンスは特定のマシンに完全に固定されません。これにより、ユーザーは、ハードウェアおよび InstallShield がインストールされているマシンを定期的に更新したり取替えたりすることができます。 再アクティベーションは通常、自動的に実行され、ユーザー側の操作は必要ありません。 再アクティベーションが必要になる数週間前になると、アクティベーション ウィザードはサイレントで、シリアル番号を求める再アクティベーションの要求をアクティベーション サーバーに送信します ( ユーザー インターフェイスの表示は発生しません ) 。 サーバーは、再アクティベーションの要求を受け取ると、その要求を検証します。 再アクティベーションの要求が有効な場合、サーバーはアクティベーション ウィザードに状態を自動的に通知し、 InstallShield の再アクティベーションを可能にします。 再アクティベーションが必要な時に、その自動実行が不可能な場合 ( たとえば、ネットワークが使用不可能など ) 、アクティベーション ウィザードは InstallShield が起動されたときに表示されます。 InstallShield の再アクティベーションは、アクティベーションに使用されたウィザードを使って実行することができます。 ウィザードによって、まず、オンラインの再アクティベーションが試みられます。 オンラインの再アクティベーションが不成功に終わった場合、オフライン手続きが利用可能になります。 再アクティベーションのオフライン アクティベーション プロセスは、アクティベーションのプロセスと同じです。   ライセンスの移動   — ライセンスの移動とは、あるマシン上にあるライセンスを一度返還してから、同じシリアル番号を使って、異なるマシン上で製品をアクティベートするプロセスを意味します。 このプロセスは、マシンを新しいマシンに取り替えるとき必要になることがあります。 使用中のライセンスを新しいマシンに移す場合、まずそのライセンスをアクティベーション サーバーのアカウントへ返還する必要があります。 このプロセスは、アクティベーションの解除と呼ばれることもあります。 ライセンスを返還すると、そのライセンスが再度使用可能になり、別のマシンで、自分のシリアル番号を使ってアクティベートできるようになります。 ライセンスを返還するには、 [ バージョン情報 ] ダイアログ ボックス ( [ ヘルプ ] メニューにある [ バージョン情報 ] をクリックしたときに表示されます ) で表示される [ ライセンスの返還 ] ボタンをクリックします。 一旦ライセンスが返還されると、同じシリアル番号を使って、新しいマシン上で製品をアクティベートすることができます。   ライセンスの完全移譲   — ライセンスの完全移譲は、ライセンスを組織内の別のユーザーに再割り当てするプロセスを意味します。 たとえば、職務が変わり、別のユーザーが InstallShield でインストールを作成することになった場合、状況によって、使用中のライセンスをその担当者に譲渡する必要が発生することがあります。 使用中のライセンスを新しいマシンに譲渡する場合、まずそのライセンスをアクティベーション サーバーのアカウントへ返還する必要があります。 ライセンスを返還すると、そのライセンスが再度使用可能になり、新しいユーザーが別のマシンで、今使用中のシリアル番号を使ってアクティベートできるようになります。 新しいユーザーは、インストールが完了した後、 InstallShield を使用中のマシンでアクティベートする必要があります。 ライセンスが他のユーザーから自分に完全に移譲された場合、 InstallShield のセールスまたはサポート担当者に連絡し、ライセンスの更新登録情報を知らせてください。 登録情報の更新は、適切なサービス、製品のアップデートやプロモーションに関する通知を受け取るために必要です。   ライセンスの返還   — ライセンスの返還は、ライセンスをライセンス サーバー上の自分のアカウントに返還するプロセスを意味します。 InstallShield がアクティベートされているマシンがあり、ある時点から、そのマシンでアクティベートしないことになった場合、使用中のライセンスをアクティベーション サーバーにあるアカウントに返還することができます。 ただし、 InstallShield をアンインストールせずに、これを行うと、トライアル期間がまだ残っている場合、 InstallShield はトライアル モードに戻ります。 トライアル期間が終了すると、 InstallShield は動作しなくなります。   シリアル番号の登録   — シリアル番号を登録するとき、製品のアップデートやプロモーションの案内を受け取ることができるように、基本的な組織の連絡先情報を入力してください。 InstallShield をフレクセラ・ソフトウェアから直接購入された場合、製品の登録は通常必要ありません。 ライセンスを組織内の別のユーザーに完全に移譲する場合、または、合併、買収、会社の分割など組織的な理由によりライセンスを移譲しなければならない場合、必ず事前に InstallShield のセールス担当者またはサポート担当者へご連絡ください。更新されたライセンスの登録情報を再度発行いたします。 InstallShield を代理店から購入された場合、シリアル番号の登録が必要になります。 シリアル番号の登録は、製品の登録ページにアクセスしてください。   ライセンスの違反   — アクティベーションまたは再アクティベーションが正常に実行されないことあります。 失敗の最も一般的な理由は、シリアル番号が既に他のマシン上にある InstallShield のアクティベートに使用された場合です。 このような場合、アクティベーション ウィザードはライセンスを保護するために、ユーザーが EULA で許可されている数を超えるマシンで InstallShield をアクティベートできないようにします。 次の表には、InstallShield のノードロック型のライセンスのアクティベーションに関する具体的な時間枠およびその他の情報が提示されています。   分類 詳細 評価期間 14 日 InstallShield を初回で起動してから 14 日以内に InstallShield をアクティベートしなかった場合、トライアル期間が終了した時点で InstallShield は動作しなくなります。 InstallShield のアクティベーションは、トライアル期間の終了、未終了にかかわらずいつでも行うことができます。 評価期間の残り日数は、 InstallShield の [ バージョン情報 ] ダイアログ ボックスで表示されます。 [ バージョン情報 ] ダイアログ ボックスにアクセスするには、 InstallShield の [ ヘルプ ] メニューで [ バージョン情報 ] をクリックします。 再アクティベーションの必要頻度 最後のアクティベーションから 12 ヶ月後。 ライセンスをあるマシンから他のマシンに移動できる回数 年に 4 回 ライセンスを、あるユーザーが使用しているあるマシンから他のユーザーが使用している別のマシンに完全に移譲できる回数 年に 1 回 (InstallShield EULA にて規定) 担当者の交代や再割り当てが理由の場合、この種の移譲は一年に1 回以上発生しないという条件で許可されます。 組織内の複数ユーザー間で同一のライセンスの共有が必要な場合、ノードロック方のライセンスよりも、同時使用ライセンスの方がニーズにより適している場合があります。 同時使用ライセンスについての詳しい情報は、 InstallShield のセールス担当者までお問い合わせください。 InstallShield が自動的に再アクティベーションを開始するタイミング 再アクティベーションが必要になる 14 日前 注:InstallShield 2012 Spring より、ノードロック型ライセンスは単一のコンピューターまたは仮想イメージ上における単一のユーザーによる使用に限られています。各ユーザーがそれぞれに ライセンスを所有していても、共有マシン上にこれをインストールすることはできません。 InstallShield 2012 以前のバージョンの場合、InstallShield を共有マシン上にインストールして、1 ユーザーのシリアル番号を使ってアクティベートすることが可能です。この状況では、各ユーザーがそれぞれに有効なライセンスを所有している限り、複数の ユーザーが InstallShield の同じインスタンスにアクセスおよび共有することができます。各ユーザーが有効なライセンスを所有していることが前提ですが、InstallShield 2012 以前を個別にインストールおよびアクティベートする必要はありません。 Additional Information 詳細については、「InstallShield EULA」を参照してください。   詳しい情報については、InstallShield と共にインストールされている InstallShield ヘルプ ライブラリの次のヘルプ トピックを参照してください:   ノードロック型ライセンスのライフ サイクルについての概要 ライセンス機能のオプション アクティベーション FAQ InstallShield のアンインストールと再インストール ライセンスをアクティベーション サーバーのアカウントへ返還する
View full article
Summary The node-locked licensing of InstallShield 2010 and later offers more flexibility than the node-locked licensing that was used for earlier versions of InstallShield. Synopsis The node-locked licensing of InstallShield 2010 and later offers more flexibility than the node-locked licensing that was used for earlier versions of InstallShield. For InstallShield 2010 and later, a license is not permanently tied to a specific machine; this allows users to periodically update and replace hardware and the machines on which InstallShield is installed. This article explains activation-related concepts and terms. It also presents specific timeframes and other details for activation of node-locked licenses of InstallShield 2010 and later. [The Japanese version of this KB article can be found here.]   Discussion Following are definitions of common activation-related terms and concepts:   Node-locked license model?With this model, the product license is tied to a specific user and machine. This model is the traditional option and the one that is most often purchased. If you are using the node-locked type of license, it is your responsibility to maintain your license on your machine. Sharing this type of license between multiple users does not comply with the InstallShield End-User License Agreement (EULA). Concurrent license model?This model enables sharing of InstallShield licenses between multiple users; it is also sometimes called floating licensing. Concurrent licensing can provide you with greater flexibility and cost efficiency than the traditional node-locked licensing. If your organization purchased concurrent licenses for InstallShield, you need to identify the license server that you are using when you install InstallShield on your machine. Subsequently, every time that you start InstallShield on your machine, the server is queried to verify that the required license is available. If the license is available, you are granted access to InstallShield. No product activation is required with concurrent licensing. To learn more this licensing model and determine whether it fits your requirements, contact your InstallShield sales representative. Activation?Activation is a process that confirms the authenticity of your software. This is done to protect you from the adverse effects of pirated software. The process also verifies that InstallShield has not been activated on more machines than allowed by the InstallShield End-User License Agreement (EULA). After you first launch InstallShield, the activation wizard opens. After a few seconds, the activation wizard disappears if you have not clicked on it, and InstallShield is launched as a trial product. If you want to activate InstallShield right away, you can select the Activate or Purchase InstallShield option, and then click the Next button. The wizard guides you through the activation process, and in seconds, InstallShield is activated. If you do not have an Internet connection or if you are having problems completing the online activation process, the activation wizard gives you the option of performing offline activation. If you are using InstallShield 2014, you can process your offline request code at our self-service webpage. If you are using an earlier version, you will need to email the request code to oactivations@flexerasoftware.com. Reactivation?Reactivation is the process by which an activated product is checked to verify that it is still installed according to the InstallShield EULA, and that it has not been activated on more machines than allowed. Reactivation is required on each machine on which InstallShield has been successfully installed and activated; otherwise, InstallShield stops working. Reactivation offers more flexibility than licensing models that do not require it. With the reactivation model that is used for InstallShield, a license is not permanently tied to a specific machine; this allows users to periodically update and replace hardware and the machines on which InstallShield is installed. Reactivation typically occurs automatically, without any interaction on your part. Several weeks before reactivation is required, the activation wizard sends a reactivation request for your serial number to the activation server silently (that is, without displaying any user interface). The server receives the reactivation request, and it validates the request. If the reactivation request is valid, the server automatically notifies the activation wizard about the status, enabling the wizard to reactivate InstallShield for you. If reactivation cannot be automatically performed when needed (for example, if you do not have an Internet connection), the activation wizard is displayed when you launch InstallShield. At that point, the activation wizard lets you reactivate InstallShield using the same wizard that is used for activation. The wizard first attempts an online reactivation. If online reactivation is unsuccessful, the wizard enables you to use the offline method. The offline activation process for reactivation is the same as that for activation. Moving a license?Moving a license is the process of returning a license on one machine and using the same serial number to activate the product on a different machine. This may be necessary if you obtain a new replacement machine. In order to move your license to your new machine, you must first return your license to your account on the activation server. This process is sometimes referred to as deactivation. Returning the license makes it available again so that you can use your serial number for activation on a different machine. You can return your license by clicking the Return License button, which is available on the About InstallShield dialog box (which is displayed when you click About InstallShield on the Help menu). Once you have returned your license, you can use the same serial number to activate the product on your new machine. Permanently transferring a license?Permanently transferring a license refers to the process of reassigning a license to a different user in an organization. For example, if your responsibilities are changing and someone else will be creating installations in InstallShield, you may need to transfer your license to that employee. In order to transfer your license, you must first return your license to your account on the activation server. Returning the license makes it available again so that the new user can use your serial number for activation on a different machine. Note that the new user will need to activate InstallShield on their machine after they have installed it. If a license is being permanently transferred to you, ensure that you contact your InstallShield sales or support representative and give them the updated registration information for the license. The registration information update is required in order to best serve you and to notify you about product updates and special offers. Returning a license?Returning a license is the process of giving a license back to your account on the license server. If you have activated InstallShield on a machine but you no longer want it to be activated on that particular machine, you can return your license to your account on the activation server. Note that if you do this without uninstalling InstallShield, InstallShield reverts back to trial mode if any days remain in your trial period. If the trial period has ended, InstallShield will stop working. Registering a serial number?When you register a serial number, you provide basic contact information about your company so that you can be notified about product updates and special offers. If you purchase InstallShield directly from Flexera Software, product registration is not ordinarily required. If you permanently transfer your license to a different user in your organization, or if you transfer your license as a result of a merger, acquisition, or other corporate action (such as a divestiture), ensure that you contact your InstallShield sales or support representative and give them the updated registration information for the license. If you purchase InstallShield from a reseller, serial number registration is required. To register a serial number, visit the product registration page. License violation?Sometimes activation or reactivation is not successful. The most common reason is that the serial number was used to activate InstallShield on another machine. The activation wizard protects the license in this case, preventing users from activating InstallShield on more machines than allowed by the EULA. The following table presents specific timeframes and other details for activation of node-locked licenses of InstallShield:   Category Details Length of evaluation period 14 days If you do not activate InstallShield within 14 days after the first launch, InstallShield will stop working when the evaluation period has ended. You can activate InstallShield at any time before or after the trial period has ended. The About dialog box in InstallShield shows the number of days remaining in your evaluation period. To access the About dialog box: On the Help menu in InstallShield, click About InstallShield. How often reactivation is required 12 months after the most-recent activation Number of times that a license can be returned and then activated 4 times per year Number of times that a license can be permanently transferred from one machine for one user to another machine for a different user 1 time per year, as noted in the InstallShield EULA. Transfers that are the result of employee turnover or reassignment are allowed, provided that such transfers do not occur more than frequently than annually. If multiple users in your organization need to be able to share the same license, concurrent licensing may better meet your needs than node-locked licenses. To learn more about concurrent licensing, contact your InstallShield sales representative. When InstallShield attempts to automatically reactivate About 14 days before reactivation is required   Note: Beginning with InstallShield 2012 Spring, a node-locked license is limited to use by a single individual on a single computer or virtual image; you may not install this on a shared machine, regardless of whether each user has their own license.   For InstallShield 2012 and earlier versions, you can install InstallShield on a shared machine and activate it using one user?s serial number. In this scenario, other users can share and access that instance of InstallShield, as long as each user has their own valid license. While each user must have a valid license, they will not need to separately install and activate InstallShield 2012 or earlier.   Additional Information For more information, see the InstallShield EULA. For additional details, see: Overview of the Life Cycle of a Node-Locked License Licensing Options Activation FAQs Uninstalling and Reinstalling InstallShield Returning a License to Your Account on the Activation Server   Related KB Articles InstallShield 2010 ???????????? Troubleshooting InstallShield 2010 and Later Activation Issues
View full article
Summary This article provides some troubleshooting tips for the activation process. Synopsis InstallShield requires activation within 14 days of first launching it. Activation is a process that needs to be performed periodically. This article provides some troubleshooting tips for the activation process.   For an explanation of activation-related concepts and terms, as well as specific time frames and other details for activation of node-locked licenses of InstallShield, see Knowledge Base article: Licensing Information for InstallShield 2010 and Later   Here are the steps to activate InstallShield:   1. After InstallShield is installed, launch the program. 2. When the InstallShield Splash screen is displayed, click on the ?Own? or "activate/purchase" link. 3. Enter your product serial number and make sure to include the hyphens (format as follows: XXXXXXX-XXX-XXXXXXXXXX or XXXX-XXXX-XXXX-XXXX and does not start with the letters ISMTK; There are zeros in the serial number, not the letter ?O?). Note: failure to enter the serial number following this format may result in the "serial not registered" browser popping up. 4. Click on the ?Verify? button. If the online activation is successful, a dialog will appear stating that the verification is complete.If the online verification fails, proceed with step 5. 5. Click the "Proceed with offline verification" button. Click the Save button, save the License.request file and email the License.request file to oactivations@flexerasoftware.com . We need the License.request file to generate a License.response file that should allow you to complete the activation process.     Discussion General Troubleshooting Tips The following tips may help you resolve issues that may occur during the activation process. If you try to activate InstallShield but your serial number has not been registered, the activation wizard that is displayed when you launch InstallShield prompts you to register online. To register your serial number, visit the Product Registration Page. Ensure that you are entering the product serial number correctly. If you are entering the serial number by copying and pasting, make sure that you are not copying an extra space before or after the serial number. A product serial number does not begin with the letters ISMTK. If you purchased a maintenance plan (i.e. support contract), the serial number beginning with ISMTK is your maintenance plan serial number. This maintenance plan serial number identifies your maintenance plan, but cannot be used to activate the product--a product serial number must be used to activate the product. If you previously activated InstallShield on another machine, you must first return the InstallShield license on that machine through a full uninstallation before it can be activated on a new machine. For the return to be successful, the machine must have an active connection to the Internet during the uninstallation. To learn more, see Uninstalling and Reinstalling InstallShield. Email Activation If you are unable to activate InstallShield through the automatic online method, email activation is required. For more information, see Activating Through Email. Activation Errors   The following table contains tips on how to resolve errors that may occur while attempting to activate InstallShield using your InstallShield product serial number.   Error Number Description Troubleshooting Information 20653 The number of activations allowed for this account has been exceeded. The InstallShield end-user license agreement allows you to install and activate InstallShield a limited number of times. This error occurs if that limit has been exceeded. To resolve this error, try one of the following solutions:   Uninstall InstallShield on one machine; doing so returns your license to your account on the activation server, allowing you to activate on a different machine. Contact your InstallShield sales representative to purchase an additional InstallShield license, or to purchase concurrent licensing. Ensure that no one else in your organization is already using the same serial number for their activated copy of InstallShield. For details such as how many times and how often you can activate InstallShield, see Knowledge Base article: Licensing Information for InstallShield 2010 and Later. 20660 The Serial Number that you entered has been disabled. The serial number that you entered has been disabled. One example of when this may occur is if you returned your copy of InstallShield and then later tried to use your serial number to activate InstallShield. If you encounter this error, ensure that you entered the serial number correctly. If you did enter it correctly, please complete and submit a Support Contact Form to InstallShield Support so that your serial number can be re-enabled if it is allowed. Once the serial number has been re-enabled, you can proceed with activation. 20661 The serial number you purchased requires product registration prior to serial number activation. If you try to activate InstallShield but your serial number has not been registered, the activation wizard that is displayed when you launch InstallShield prompts you to register online. To register your serial number, visit the Product Registration page. If you did not purchase InstallShield through a reseller, ensure that you entered the serial number correctly. 20676 The license has been transferred between computers more times than is allowed. There is a limit to the number of times that you can transfer your InstallShield license from one machine to another in your organization. This error occurs if that limit has been exceeded. To resolve this error, contact your InstallShield sales representative to purchase an additional InstallShield license, or to purchase concurrent licensing. For details on the number of times that you can transfer your license, see Knowledge Base article: Licensing Information for InstallShield 2010 and Later. 50020 The response text you entered is invalid. This error occurs if you are attempting offline (e-mail) activation and the response text that you entered in the activation wizard is incorrect. Ensure that you correctly entered the response text. The response text starts with the following string: <?xml version The following string marks the end of the response text: </Response> 50040 An unexpected error occurred. This error may occur if an online activation attempt fails. For example, if your machine does not have an Internet connection, online activation cannot occur. If you do not have an Internet connection or if you are having problems completing the online activation process, the activation wizard gives you the option of performing offline activation through email. For information on how to activate offline through email, see Activating Through Email.     Additional Information For frequently asked questions and answers about activation, see Activation FAQs. If you have tried all of the aforementioned suggestions and you still have not been able to activate InstallShield, please complete and submit a Support Contact Form to our Technical Support Team for additional assistance.   Related KB Articles Search and Download User Guides, Installation Guides and Product Release Notes Deactivation of InstallShield, AdminStudio and WiseScript Editor InstallShield 2018 InstallShield 2018 Known Issues InstallShield 2016 InstallShield 2016 Known Issues InstallShield 2016 Express Edition Known Issues InstallShield 2015 InstallShield 2015 Known Issues InstallShield 2014 InstallShield 2014 Known Issues InstallShield 2013 Service Pack 1 for InstallShield 2013 (Q213736) InstallShield 2013 Reactivation Problems Hotfix InstallShield 2012 Spring Service Pack 1 for InstallShield 2012 Spring (Q208466) InstallShield 2012 Spring Known Issues (Q204469) InstallShield 2012 Service Pack 1 for InstallShield 2012 (Q201298) InstallShield 2012 Known Issues (Q211162) InstallShield 2011 InstallShield 2011 Known Issues (Q208912) InstallShield 2011 Express Edition Known Issues (Q208915) InstallShield 2010 InstallShield 2010/InstallShield 2010 SP1/InstallShield 2010 Expansion Pack Release Notes (Q200329) InstallShield 2010 Known Issues (Q200331) InstallShield 2010 Express Edition Known Issues (Q200853)  
View full article
Summary This KB explains evaluation-mode limitations. Synopsis If you have not purchased a license for InstallShield, you can install it and use it for a limited number of days without activating it. When you are using InstallShield in this scenario, it operates in evaluation mode, and some of its functionality is not available. This KB explains those evaluation-mode limitations. When you activate InstallShield, the evaluation limitations are removed.     Discussion Following is a list of the limitations in the evaluation version of InstallShield. Time limit for running InstallShield?The length of the evaluation period is 14 days. If you do not activate InstallShield within 14 days after the first launch, InstallShield will stop working when the evaluation period has ended. You can activate InstallShield at any time before or after the trial period has ended. The About dialog box in InstallShield shows the number of days remaining in your evaluation period. To access the About dialog box: On the Help menu in InstallShield, click About InstallShield. Time limit for running setups that were created in the evaluation version of InstallShield?If you build an installation in the evaluation version of InstallShield, your installation will stop working after 5 days. If you try to launch your installation after that time period, a message such as the following one is displayed: This setup was created with an EVALUATION VERSION of InstallShield. Evaluation setups work for only 5 days after they were built. Please rebuild the setup to run it again. Release type limitations?The evaluation version of InstallShield includes support for building compressed Setup.exe files, but no other release types. If you are creating a Windows Installer?based release, the .msi database is always embedded in the Setup.exe file. If you configure a release to be uncompressed and then try to build that release in the evaluation version, the uncompressed option is ignored, and InstallShield displays the following build warning: Warning -7211: Building a compressed Network Image Setup.exe. All other build types are not allowed in the evaluation mode of InstallShield. Build event limitation?The evaluation version ignores the Precompression Event setting, which is displayed in the InstallShield Premier Edition on the Events tab for a release in the Releases view. If you use this setting to specify a command that you want to be run at build time, InstallShield ignores the command and displays the following build warning: Warning -7211: Evaluation mode: skipping precompression build events... In the full activated version of InstallShield Premier Edition, you can use this setting to specify the command that you want to be run after InstallShield has built the .msi package and the .cab files. This event occurs after .cab files are streamed into the .msi package, but before the .msi package has been digitally signed and streamed into the Setup.exe file. This setting is applicable to Basic MSI and InstallScript MSI projects. This functionality was introduced in InstallShield 2011. It is not available in earlier versions. Setup.exe command-line limitation?The /a command-line parameter does not work with Setup.exe files that are built in the evaluation version of InstallShield. If you try to pass this parameter to an evaluation Setup.exe file, the following message is displayed: This setup was created with an evaluation version of InstallShield, which does not support extraction of the internal MSI file. The full version of InstallShield supports this functionality. For more information, see InstallShield KB article Q200900. In the full activated versions of InstallShield, the /a option causes Setup.exe to perform an administrative installation. An administrative installation copies (and uncompresses) your data files to a directory that is specified by the user. Limitations for patches and QuickPatch packages?The evaluation version does not let you create patches or QuickPatch packages that are based on Setup.exe files that are created in the evaluation version of InstallShield. If you try to select an evaluation Setup.exe file in one of the following areas of InstallShield, a message box is displayed: *Patch Design view (in the Premier or Professional editions of InstallShield) * Create New QuickPatch Wizard (in the Premier, Professional, or Express editions of InstallShield) The message box states: This setup was created with an evaluation version of InstallShield, which does not support extraction of the internal MSI file. The full version of InstallShield supports this functionality. For more information, see InstallShield KB article Q200900. Note: You can use the evaluation version of InstallShield to create an upgrade that updates an earlier version of your product. Limitations for .msi and .mst files?If you open an .msi or .mst file in the evaluation version of the Premier or Professional edition of InstallShield, the ability to save changes to the file is disabled. When you activate InstallShield, the aforementioned limitations are removed.
View full article
Summary Support can provide extensions to the evaluations of AdminStudio, InstallShield, and InstallAnywhere. Synopsis After the 21 day evaluation period has ended for AdminStudio, or InstallShield (14 day evaluation) has ended a evaluation extension activation code can be used to extend the evaluation for an extra 7 days. After the 21 day evaluation period has ended for InstallAnywhere has ended a password can be used to add 7 days to the evaluation. The password input will appear after the evaluation has ended. Each of these codes or password can only be used once per installation. For a longer extension the product must be installed on a new machine.
View full article
Summary: You may want to read info from an existing .msi at times. This can be done with powershell.   Description: The powershell may use a COM Windows installer object. Open the .MSI as a database, use a view to execute a query and fetch the data. Below is an example of powershell querying the shortcut table of an .msi for values. Other tables can be queried by changing the select statement in line: $ShortcutsView = $MSI.OpenView("select * from Shortcut")   Column values can be retrieved from other columns by changing number value in the line: Write-Output (Get-Property $Shortcuts StringData 1)   Example: $windowsInstaller = New-Object -ComObject WindowsInstaller.Installer function Get-Property ($Object, $PropertyName, [object[]]$ArgumentList) { return $Object.GetType().InvokeMember($PropertyName, 'Public, Instance, GetProperty', $null, $Object, $ArgumentList) } $MSI = $windowsInstaller.OpenDatabase("C:\InstallShield 2019 Projects\My Project Name-1\Product Configuration 1\Release 1\DiskImages\DISK1\My Project Name-1.msi", 0) $ShortcutsView = $MSI.OpenView("select * from Shortcut") $ShortcutsView.Execute() $Shortcuts = $ShortcutsView.Fetch() write-host "First 5 fields of Shortcut table" -ForegroundColor Green if ($Shortcuts) { Write-Output (Get-Property $Shortcuts StringData 1) Write-Output (Get-Property $Shortcuts StringData 2) Write-Output (Get-Property $Shortcuts StringData 3) Write-Output (Get-Property $Shortcuts StringData 4) Write-Output (Get-Property $Shortcuts StringData 5) } $ShortcutsView.Close() $MSI.Commit() $MSI = $null [system.gc]::Collect() [System.gc]::waitforpendingfinalizers()   Additional Information: Here is a link to documentation on the COM Windows installer object. https://docs.microsoft.com/en-us/windows/win32/msi/installer-object
View full article
Summary: You may want to pass variables to the .exe application you are launching from the installed .msix. This can be done with the Package Support Framework. Some of those features are supported out of the box with Installshield. You will find some information on how to do this from Installshield below:   Description: In the MSIX Project, you'll go under Package Payload->Applications->Package Support Framework, and add a Custom Fixup. Point the JSON Path to your custom config.json.  A n example of how the config.json would look is like: { "applications": [ { "id": "ID_FROM_APPLICATION_ENTRYPOINT", "executable": "VFS/ProgramFilesX86/My Company Name/My Product Name/YOURAPP.exe", "arguments": "ARGUMENTPASSED", "workingDirectory": "" } ] }   Note for example:  ID_FROM_APPLICATION_ENTRYPOINT should match Key Name. Which should match the Id in the AppxManifest.xml contained in the .MSIX.   Please NOTE: Evaluation versions of Installshield do not enable the use of Custom Fixups until activated.   Additional Information: Package Support Framework information may be found here: https://docs.microsoft.com/en-us/windows/msix/psf/package-support-framework-overview
View full article