how do I permanently unpin an app from the taskbar

Question

how do I permanently unpin an app from the taskbar

Kari Forrester 0

I know that I can right click on an app and then unpin from the taskbar, however, next time I turn my computer on, the app is back on the taskbar. How do I permanently unpin an app?

0 comments

2 answers

Your answer

Answer 1

Hi Kari Forrester,

If the app reappears on the taskbar after every restart, it may be getting re-pinned automatically rather than simply remaining cached. This can happen when a taskbar layout policy or profile setting is reapplying pinned apps at sign-in.

You can try this quick check by creating a temporary local user account and sign in to test.

Unpin the app there and restart.
If the app stays unpinned, the issue is likely specific to your current profile.

If this is a work or school-managed device, check with your IT administrator whether a taskbar layout or pinning policy is being applied at sign-in as suggested by the Independent Advisor.

If the issue continues, please let us know which app keeps returning and whether the PC is personally owned or managed by an organization. That information can help narrow down the cause. Hope this points you in the right direction!

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.

Hendrix-V 18,605 Reputation points Microsoft External Staff Moderator

2026-06-25T06:50:13.9933333+00:00

Hi Kari Forrester,

If you have any further questions or updates regarding this issue, please feel free to let me know in the Comments section. I'd be happy to assist you.

Answer 2

John Jefferson Doyon 86,980 Independent Advisor

Hi, I'm John! I will help you with this.

If the app comes back after a restart, it usually means something is adding it back automatically. This can happen because of a work/school policy, a manufacturer app, or the app itself after an update.

In the meantime, if you haven’t already already:

Press Win + R, paste this, then press Enter: %AppData%\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar
Look for the shortcut of that app and delete it.
Then open Task Manager > find Windows Explorer > right-click it > Restart.
After that, restart the PC and check if the app stays removed.

If it still comes back, please tell me:

What app keeps returning to the taskbar?
Is this a personal PC, or is it connected to a work/school account?
Does it return right after restart, or only after opening that app?

Gritsnich 0 Reputation points

2026-08-16T15:46:20.7866667+00:00

I tried this but immediately after restart the Task Manager is opening. It doesn't show as an open app on the task bar but if I left click, it shows Task Manager is open along with the Task Bar. I tried the above & it still is popping up. It seems to be reacting to something because the longer I use the computer, my mouse will start flickering & eventually I won't be able to type without it jumping away from where I'm typing.

This is a personal laptop.
Gritsnich 0 Reputation points

2026-08-16T15:49:31.6533333+00:00

For clarification. The Task Manager doesn't show as an open app on the Task Bar but if I RIGHT click on the Task Bar, a display box opens right above the Task Bar showing the Task Manager & Task Bar. I click on the name Task Manager to open the app, click the X to exit but it keeps reappearing. I also tried ending the Task Manager app from the Task Manager by right clicking & clicking the "end task" function.

It seems the app will not stay closed, no matter what I do.
Gritsnich 0 Reputation points

2026-08-16T15:51:24.4933333+00:00

Also, I have switched my mouse, unplugged the USB & replugged. I've made sure my keyboard has fresh batteries. Those actions haven't changed anything.
Gritsnich 0 Reputation points

2026-08-16T15:53:10.3633333+00:00

Sorry for the multiple posts. I also did an update about 4 days ago. I didn't have the problem prior to this. I did find some posts from late 2025 that noted there was an issue with an update that had caused the same problem, if I was reading it correctly.