Microsoft Edge blocked after reboot in Windows multi-app kiosk modeSolved

Hi @im_dany,

This behavior is usually seen when Microsoft Edge updates in the background and the Windows kiosk configuration is allowing Edge using a version-specific executable path.

In Windows Assigned Access / kiosk mode, the allowed app rules are strict. If Edge was added using a path that points to a specific Edge version folder, the rule may work until Edge updates. After a reboot, Windows re-evaluates the kiosk rules and Edge may also apply a pending update. If the executable path changes due to the update, the existing kiosk rule no longer matches and Edge is blocked.

To fix this, update the Windows kiosk policy so that Edge is added using the static executable path instead of a version-specific path.

Recommended steps:

1. Go to Manage and open one affected Windows kiosk device.
2. In the Policies tab, remove the existing kiosk policy from that test device.
3. Confirm that the Remove Device Policy action is marked as Success in the device action history.
4. Clone the existing Windows kiosk policy.
5. In the cloned policy, go to the Windows kiosk app configuration and add Edge as a Desktop app.
6. Set the Edge file path to:
   C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
7. Associate the updated kiosk policy with one affected test device.
8. Confirm that the Associate Device action is successful.
9. Reboot or sign in to the kiosk session and try launching Edge again.

Once Edge opens correctly on the test device, apply the updated policy to the rest of the kiosk devices.

Regards,
Sienna Carter
Hexnode UEM