"Show taskbar buttons on: All Taskbars" setting keeps resetting on sleep

Anonymous
2024-09-10T17:18:21+00:00

I have 2 monitors, and I want to keep my full taskbar persistently-visible on both of them. This was working fine until about a week ago. Now, it behaves as though "Main taskbar and taskbar where window is open" is selected even though "All taskbars" is still selected, until I toggle the setting myself.

My workaround is manually setting it to "Main taskbar and taskbar where window is open," then back to "All taskbars." This fixes the issue until the next time my PC sleeps.

I have tried resetting my PC and I have tried SFC /scannow as an admin in case of settings file corruption. Neither have resolved the issue.


Taskbar Settings

Lock the taskbar | ON

Automatically hide the taskbar in desktop mode | OFF

Automatically hide the taskbar in tablet mode | OFF

Use small taskbar buttons | OFF

Use Peek to preview the desktop when you move your mouse to the Show desktop button at the end of the taskbar | OFF

Replace Command Prompt with Windows PowerShell in the menu when I right-click the start button or press Windows key+X | ON

Show badges on taskbar buttons | ON

Taskbar location on screen | Bottom

Combine taskbar buttons | Always, hide labels

MULTIPLE DISPLAYS

Show taskbar on all displays | ON

Show taskbar buttons on | All taskbars

Combine buttons on other taskbars | Always, hide labels


Device

Processor AMD Ryzen 7 3700X 8-Core Processor 3.60 GHz

System type 64-bit operating system, x64-based processor

Windows

Edition Windows 10 Home

Version 22H2

Installed on ‎8/‎11/‎2020

OS build 19045.4780

Experience Windows Feature Experience Pack 1000.19060.1000.0

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

52 answers

Sort by: Newest
  1. Anonymous
    2024-09-21T15:56:14+00:00

    I found the registry key to this setting, but changing it doesn’t solve the problem.

    path: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced

    set MMTaskbarMode to

    0: All taskbars

    1: Main taskbar and taskbar where window is open

    2: Taskbar where window is open

    Even when set to 0, It’s like the explorer doesn’t know that it needs to show the window icon on all taskbars on first time load.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-09-21T15:19:09+00:00

    Just adding a +1. RTX 3090 on latest official drivers with two active displays on Windows 10 latest updates. If the displays goes into sleep, when you wake the displays, the Always display all icons on both taskbars setting needs to be reset. Turning it on/off fixes it. Pretty annoying. I also think it started happening recently but not 100% sure as I recently discovered the option.

    Was this answer helpful?

    10 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-09-21T10:21:12+00:00

    I'm having this same issue and I'm just wondering if you've found a permanent fix yet.

    Thanks.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-09-16T14:26:50+00:00

    I'm having the same issue as well. It's driving me crazy as I often use those buttons on secondary monitor and I keep thinking the app must be closed.

    It started from an update around last month or so.

    currently on windows 10 pro 22H2 19045.4894

    Was this answer helpful?

    10 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-09-14T19:07:53+00:00

    Hey Kyo,

    I have never messed with my startup or power settings, so I don't think that is the cause. I can test booting up in safe mode to see if it reproduces the bug or not.

    My best guess is that this is being caused by a recent update. I ruled out file corruption because SFC /scannow did not resolve the issue, leading me to believe it was some sort of update from MSFT that caused it (BIOS, firmware, etc). I did not note a specific update or point in time where the issue began, though it was sometime in the last 3-4 weeks.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments