Hi @Liang, Ming ,
Thanks for reaching out.
When the system sleeps and the user is required to sign in again, Shell Launcher v2 launches the kiosk app again as part of the logon process. In some cases the previous taskbar registration isn’t fully cleaned up by the shell, so when the new instance starts, the shell creates another taskbar entry instead of reusing the existing one, which is why the icons accumulate until a full sign-out or system restart resets the shell state.
Unfortunately, there isn’t a supported Windows API that allows an application to directly force the taskbar to refresh or remove stale icons. The taskbar is managed by Windows Explorer, and applications generally don’t have a way to programmatically clear or rebuild those entries.
That said, there are a couple of things worth checking on the application side that can sometimes prevent duplicate icons from appearing:
- Ensure the app uses a consistent AppUserModelID across launches. Windows groups taskbar buttons based on this ID, and if it changes between launches the shell may treat each restart as a separate application.
- Confirm the app is not unintentionally creating multiple windows during initialization (which can also result in multiple taskbar buttons).
- If possible, ensure only a single instance of the application is allowed to run.
If you found my response helpful or informative in any way, I would greatly appreciate it if you could follow this guidance provide feedback.
Thank you.