PartnerNonImmediateDialStrings
Note Starting with Windows 10, version 1703, this setting can no longer be used in provisioning packages. For more information on changes to the Windows Provisioning Framework, see Windows Provisioning Framework. This setting may have a Configuration Service Provider (CSP) equivalent that can be used instead. To determine if a CSP for this setting exists, see the description below.
Dialer codes that will be accepted and passed as a parameter to the primary OEM dialer application, for apps that start after the <Call> button is pressed.
You can add additional dialer codes so that they will be accepted and passed as a parameter to the primary OEM dialer application. You can provide any number of additional diagnostic codes that you want to use. Each dialer code should begin with ##.
Set PartnerNonImmediateDialStrings to a list of dialer codes. You can use multiple values by separating them with a semicolon ";". The dialer string should not end with #. For example, "##3282;##2539;##33284;##2539;##786;##778;##33284".
Note
To define dialer codes that start the app immediately after the last # button is pressed, see PartnerImmediateDialStrings.
| Edition | x86-based devices | x64-based devices | ARM-based devices |
|---|---|---|---|
| Windows 10 Mobile | N/A |
N/A |
Supported |