The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

LauncherOptions.FallbackUri | fallbackUri property

Gets or sets a value that represents a URI that the user should be taken to in the browser if no app exists to handle the file type or URI.


var fallbackUri = launcherOptions.fallbackUri;
launcherOptions.fallbackUri = fallbackUri;

Property value

Type: Windows.Foundation.Uri [JavaScript] | System.Uri [.NET] | Windows::Foundation::Uri [C++]

URI that the user should be taken to in the browser.


You can only set the fallback URI property with http:// or https:// URI. If this property is set and there is no app installed to handle the file or URI being launched, the user's default browser is launched automatically and navigated to the specified URI. The user will not see an Open With dialog asking to choose an option in this case. You should only use the fallback URI when directing the user to the Windows Store is not appropriate, such as the case when the file or URI is only supported by a desktop app that is not listed on the Store. In all cases where there is an app on the Windows Store that supports the file or URI that you are launching, you should use the PreferredApplicationPackageFamilyName and PreferredApplicationDisplayName to recommend that app to the user.

You cannot set the preferred application properties and the fallback URI at the same time, since only one fallback may be used. The Launcher API will fail if both fallbacks are set.

Windows 8.1:  In Windows 8.1 only, this property also accepts Windows Store URIs. These URIs can be used as an alternative to the PreferredApplicationPackageFamilyName and PreferredApplicationDisplayName properties to send the user to a specific app in the Store without popping an Open With dialog. This functionality is not supported on Windows Phone 8.1 or converged Windows 10 apps, and its use is not recommended.


Call the Launcher.LaunchFileAsync(IStorageFile, LauncherOptions) | launchFileAsync(IStorageFile, LauncherOptions) method with fallbackUri set to the fallback URI.

// The URI to launch
var uriToLaunch = "contoso:somearguments";

// Create a Uri object from a URI string 
var uri = new Windows.Foundation.Uri(uriToLaunch);

// The fallback URI
var uriFallback = "";

// Create a Uri object from a URI string 
var fallbackURI = new Windows.Foundation.Uri(uriFallback);

// Set the fallback URI
var options = new Windows.System.LauncherOptions();
options.fallbackUri = fallbackURI;

Windows.System.Launcher.launchUriAsync(uri, options).then(
   function (success) {
      if (success) {
         // URI launched
      } else {
         // URI launch failed

Requirements (Windows 10 device family)

Device family

Universal, introduced version 10.0.10240.0

API contract

Windows.Foundation.UniversalApiContract, introduced version 1.0


Windows::System [C++]



Requirements (Windows 8.x and Windows Phone 8.x)

Minimum supported client

Windows 8

Minimum supported server

Windows Server 2012

Minimum supported phone

Windows Phone 8.1 [Windows Phone Silverlight 8.1 and Windows Runtime apps]


Windows::System [C++]



See also

Association launching sample
How to launch the default app for a file (JavaScript)
Launch the default app for a file
How to launch the default app for a URI (JavaScript)
Launch the default app for a URI
Guidelines for file types and URIs
Launcher.LaunchFileAsync(IStorageFile, LauncherOptions)
Launcher.LaunchUriAsync(Uri, LauncherOptions)