This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I switched to Windows 11 a few weeks ago, and ever since then, the taskbar auto-hide quits working when the computer comes out of Sleep mode. I have to be away from the computer for a while before it will happen, and I believe it has something to do with me running dual monitors. When I wake my computer, my secondary monitor appears to come up faster than my primary by just a fraction. Once my primary is on, there is a message saying something about the taskbar already being hidden (I think) and the taskbar on my primary monitor has the taskbar up. When I go to Taskbar Behaviors, 'Automatically hide the taskbar' is no longer checked. I'll select it again, and it will work fine until the system goes back into Sleep mode for a while, again.
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.
I have been away from this forum for a while, using Win 10, which has no issue keeping the Windows 11 taskbar auto-hide setting stable.
Has a resolution been found?
Has there been a recent update that fixed the issue?
Thanks to all...
Will
Yup, for the past 3-1/2 hours, since Costco Technical and Warranty Services led me to (KB5039302), I've been able to let my PC put itself to sleep while leaving the Auto-Hide of the taskbar enabled.
youTube also seems to be able to keep the PC awake, but GoogleVoice still does not. Or, rather, leaving a phone call on hold causes the PC to turn off the display, and then turn the display back on, which cleared the Auto-Hide setting, once.
But other than the GoogleVoice-on-hold snafu, the Auto-Hide setting seems to be stable.
The maddening thing, which goes without saying, is that power management should never, ever have anything to do with any data whatsoever -- not user data, not even a single solitary binary bit of system data that has been user-configured. It's potentially threatening to have had this snafu.
Anyway, I play music on youTube to keep my stock market trading charting services awake, and pause the music to put my PC to sleep.
No thanks to Dell Technical Support, who refused to acknowledge all you guys' complaining and tinkering.
Thanks, I'll give it a shot!
Well don't be too hard on Costco - they have no control over Microsoft's "solutions,." :)
It's not a question of being hard on Costco. I bought this Dell desktop PC from Costco, Inspiron 3020, for a great reduced price in the second half of last year.
Part and parcel of this purchase was so-called Dell Technical Support. When they (Dell) consistently, persistently lied about all the difficulties all you good people were having with this feature, always denying that it was a known problem, even AFTER I forwarded this very link from Microsoft Community, and drove them to acknowledge the receiving of this link and its 30 pages of complaints and dialogs, I gradually came to the realization that Dell Technical Support was not being provided, despite my having paid for it.
There is a difference between being disappointed and being lied to. At least there used to be, 800 million years ago, like in 2018. There used to be a difference between not having expectations met, and being cheated.
I'm a software engineer, not a lawyer, but since I bought this hardware/software system from Costco, they ought to be held accountable for not delivering on Dell Tech Support.
The Costco Warranty Service made up for it, thankfully, by stumbling upon the Cumulative Preview update (HEY, what kind of double talk is that??) that made the problem go away.
Oh, by the way, you have to set the PC timeout equal to the display timeout. If the display turns itself off before the PC puts itself to sleep, the taskbar's autohide gets disabled as usual.
This kind of bug in general cannot be solved with full-blown debugging, because of the power management going on. It can normally be solved by inserting a bunch of "printf" statements into the code, so as to slash the area of code in question almost in half per iterative run. "Never say it can't be in that part of the code" and "Play the ball where it lies" is the essence of effective, efficient debugging, with or without the aid of a debugger.
