Launching local apps (registry)

Table of Contents



We recommend using a newer method for launching local apps from your Workspace: Local App Launcher.

In this article will explain how you can launch local applications with some Windows Registry edits. We make use of the URI handlers within the OS. Local apps are only accessible via Workspace on the device which they are installed to. In order to enable local applications from the Workspace, please follow the steps below.

For the Workspace 365 App Launcher (newer method for launching local apps), we make use of the same protocol. But for administrators it's much easier to create and deploy these instructions to launch local applications including parameters.



Step 1. Create protocol

First, the protocol has to be created in a .txt file.

  1. Open a new .txt file using Notepad.
  2. Copy the content from one of the examples below.
  3. Paste it into the .txt file.
  4. Save the file.

    In case of preventing any registry conflicts, we advise you to use a unique application name at the “HKEY_CLASSES_ROOT\ “positions in the protocol as we also did in the example above (not “notepad”, but “notepadapp” for example).

    The app name specified in “@=URL: notepad” and "FriendlyTypeName"="Notepad" can be the app name of your choice and does not have to be unique.
  5. The path of the .exe file in the protocol should match with the exact path of that .exe file on your local disk. Locate your .exe file and make sure the path is correctly stated in the protocol.
  6. The .txt file must now be changed to a .reg file. Please rename the file to a .reg file.
  7. Save the .reg file.
  8. Open the registry editor on your PC (regedit.exe).
  9. Import the created .reg file in the Registry.


Create .reg file

First, a protocol must be created in the Windows registry for the local application. In this case, we use the Notepad application as example:

Windows Registry Editor Version 5.00
"URL Protocol"=""
@="\"C:\\Program Files (x86)\\Notepad++\\notepad++.exe\""


Or e.g. "Windows Lock"

Windows Registry Editor Version 5.00
"URL Protocol"=""


@="C:\\Windows\\System32\\rundll32.exe user32.dll,LockWorkStation"


Or e.g. "Internet Explorer with specific page"

Windows Registry Editor Version 5.00

  "URL Protocol"=""


  @="\"C:\\Program Files\\internet explorer\\iexplore.exe\""


Or e.g. "Start RDP with mstsc"

Windows Registry Editor Version 5.00
@="URL:Remote Desktop Protocol <URL:Remote%20Desktop%20Protocol> "
"URL Protocol"=""


@="cmd /V:ON /c setlocal && set url=%1 && set url=!url:rdp:=! && set url=!url:,= ! && start mstsc !url!"

Back to top


Step 2. Activate the app

  1. Go to the App store (or click on "+ Add tiles").
  2. Click Create tile.
  3. Create a Shortcut.


  4. Fill in the app name of your choice.
  5. Select an icon for the tile.
  6. Fill in the following at the Webpage field.
    • To connect to a server via gateway and hostname. For example:
    • Or fill in the pad to your rdp file to connect. For example:
      Spaces in the path are not allowed.

      Note: change "Applicationname" to the name you have given the application.
      In our example application, it should be "Notepadapp:open".


      A unique name must be used behind [HKEY_CLASSES_ROOT\ in the protocol.

  7. When all the information has been filled in correctly, you can add the shortcut to your Workspace.

You can now launch the local app from the shortcut app you just created. App permissions, such as who has access can be managed from the App store.


Back to top

Launching local Office applications on MAC

Launching local Office applications on MAC works a bit differently then launching it on Windows.
The best way to launch an Office application locally is by using Office URI Schemes.

Example scheme:


Back to top