Summary
This article discusses preventing shortcuts created during installation from being pinned to the target system's Start screen.Synopsis
This article discusses preventing shortcuts created during installation from being pinned to the target system's Start screen.
Discussion
InstallShield 2013 & Later
InstallShield 2013 and later versions of InstallShield includes a predefined shortcut property which can be used to sepecify whether or not the shortcut is pinned to the Start screen. Please see the Help topic Specifying Whether a Shortcut Should Be Pinned to the Windows 8 Start Screen.
InstallShield 2012 Spring
Microsoft introduced the Start screen with Windows 8. The Start screen consists of application shortcuts. If a MSI based installation creates shortcuts, some shortcuts are automatically pinned to the Start screen.To prevent the shortcut from being pinned during installation, the shortcut attribute represented by the System.AppUserModel.StartPinOption Shell property can be set to 1.
To make this setting in the InstallShield project, please perform the following steps:
- In the View List under System Configuration, click Shortcuts.
- In the Shortcuts explorer, select the shortcut that you want to configure. The shortcut settings are displayed in the right pane.
- In the General section, on the far right of the Shell Properties row, click the Add new Shell Shortcut Property button. InstallShield adds a new Key Name setting
- Expand the Key Name setting
-
Enter the following information for the Property Setting: {9F4C2855-9F79-4B39-A8D0-E1D42DE1D5F3},12
-
Enter the following information for the Value Setting: 1
Additional Information
For more information on the Shortcut Shell property, please refer to the msdn article:
Note: This property setting will suppress the shortcut from being pinned the first time a given shortcut is installed on a target system. When an installation package is installed a subsequent time on the same target system, instead of using the shortcut attribute setting in the installation package, Windows will use the last known state of a given shortcut, since the state persists across uninstallation and reinstallation.
Note: When the property name System.AppUserModel.NoPinToStartOnInstall is used to set a shortcut, windows installer Warning 1946 message is seen. The workaround is to use the property?s GUID, instead of the property name, as documented in the following Microsoft Knowledge Base article:
Was this helpful?
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
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.
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.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Case id: 00001065
Activity: Status change: 2 hours ago