@Leo Wang Thanks for posting in our Q&A.
For this issue, it seems a default behavior. If you want to avoid AppLocker popping up, it is suggested to try to find the background processes that need to be called for the foreground app and then add the background process path to the list allowed by the kiosk profile.
Step 1: Find the background processes that need to be called for all foreground apps. (Take Adobe for example)
Install process monitor in kiosk mode, open each foreground app, collect procmon log, and check the corresponding "Access Denied" records in the log. Then add the corresponding paths to the kiosk profile as the Win32 apps. In this way, the blocked processes can be located more accurately.
Step 2: Add allow lists to the kiosk profile.
We can use the default UI, for example, Adobe needs to call a background process: C:\Program Files\Adobe\Acrobat DC\Acrobat\acrobat_sl.exe. So, we need to add this path to the allow list as a win32 app.
Honestly, I'm not sure if single app kiosk will get rid off AppLocker. It is suggested to try and check if it works differently with Multi App Kiosk.
Thanks for your understanding.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.