Hi everyone. I’m setting up a Windows multi-app kiosk policy in Hexnode. The policy association shows as successful in the portal, and the application is already installed on the target PC. However, when trying to launch the app from kiosk mode, it fails to open and displays a blocked/error state.
Is the PC itself blocking the application, or is there a specific setting in the kiosk policy I need to check to get this launching correctly?
44 Views
Hello,
Thank you for reaching out to Hexnode Connect!
In this scenario, it is usually not the PC blocking the app directly. When configuring a Windows multi-app kiosk, the policy restricts execution strictly to the binary paths defined within the policy. A successful policy association confirms that the policy reached the device, but if the configured App location path is incomplete or incorrect, the kiosk environment will fail to launch the permitted application.
This typically occurs if the App location was set to a generic installation folder path rather than the explicit executable file.
To resolve this, update your policy using the following steps:
(Note: Keep in mind that if the application is updated in the future and its installation directory changes, you will need to update the App location path in your kiosk policy accordingly.)
Best regards,
George
Hexnode UEM.
Don't have an account? Sign up
What's new 
