Hi ,
Welcome to the Support Portal. How can we help?

Troubleshooting the Local App Launcher

 Table of Contents



Having problems with the Workspace Local App Launcher? Such as not able to open (specific) applications or seeing constant browser pop-up notifications while starting the app? Keep on reading. This article will help you to fix these issues.


The app could not be opened


Explanation: it could happen you are not able to open a local app from your Workspace. You receive the error message "The app couldn't be opened". However, you are able to open the application with the same path used in your XML file via the Windows Run command.


  • Make sure you meet the requirements. Keep in mind that the process we run is x86.
  • Make sure that the id and target in your XML file corresponds with what has been configured for the application in Workspace. The application path (target) is a relative path and needs to be located on the exact same location on each client to which you are deploying the Workspace 365 App Launcher and Instruction file to.
  • For further troubleshooting on why the app couldn't be opened, click "Open logs folder" or navigate to 'AppData\Roaming\Workspace 365 App Launcher\logs' for more information.

Back to top


Constant browser pop-up notification

Explanation (06-01-2020 12:00 CET): since version of Google Chrome 77.0.3865.90, you will get a pop-up notification every time you want to launch a local app. This is due to changes made in Google Chrome. 

Solution: you can prevent this by adding the w365-launcher URL to the URLWhitelist of Chrome by adding this reg file on the local client:

Google Chrome

Windows Registry Editor Version 5.00

Microsoft Edge

Windows Registry Editor Version 5.00

We're looking into ways to add it by default in the installer.

Back to top


Quick Assist cannot be opened

Explanation: it is not possible to open 32-bit version of Quick Assist from your Workspace, or it seems to open but closes directly after. However, you are able to open the application via the Windows RUN command with the same path used in your XML file.

Solution: start the 64-bit version of Quick Assist from your Workspace instead of the 32-bit version. You can do this by starting the 64-bit PowerShell via the Sysnative folder and let Quick Assist start via the following argument:

target="%windir%\sysnative\WindowsPowerShell\v1.0\powershell.exe" args="-WindowStyle Hidden -Command Invoke-Expression C:\Windows\system32\quickassist.exe" />

When starting the 64-bit version from you Workspace, you may see a PowerShell window briefly pop up. However, you will now be able to offer Quick Assist as a tile from your Workspace. 

Back to top