this will probably fix the issue as well, just reverse the reg setting to 03 to force it on and restart, the problem i had was pretty much the same but in reverse where it was enabling it for me even after unchecking it.
It doesn't.
For months (over a year?) I've been reading almost everything Google and Brave Search can find on this issue, and nothing has worked. I've even seen and used your exact suggestion before.
Auto-hide works for a while, regardless of how I enable it, then something just flat-our turns it OFF. I look in the GUI or the Registry, and they show that it's NOT enabled anymore.
That's what most of this thread is about.
I think (almost) everybody here KNOWS how to ENABLE auto-hide.
But no one knows what is DISABLING it and how to prevent that.
Some things I have read seem to relate this issue with a multi-monitor setup. (I use three monitors.) There is another issue that *seems* to be related. When your monitors have been put to sleep, and you come back to your system, you get a strange error message saying something about a toolbar already being enabled. I'm sure if you look back through this thread you may find mention of it. (Since my work-around discussed below, I don't get this anymore, either, so I don't remember the exact message)
In addition, since I got the latest update to 24H2, when the system wakes my monitors up, the resolutions are wrong, even though they are correct in the settings. This of course completely messes up my desktop. I have had to change it so my system no longer puts my monitors to sleep.
But since I installed the version of Explorer Patcher that was released as a response to Windows 11 24H2 and I starting using it's (new) replacement for the Taskbar, taskbar auto-hide STAYS enabled.
I really don't know why this issue bothers me (and others) so much. Maybe because it destroys my work-flow? Maybe it's my software development background and my need to solve problems? Maybe it's because it's such a stupid little issue that should be easy to fix? Maybe it's because MS has so far completely failed to even acknowledge the problem -- let-alone fix it -- update after update after update?
MS has to spend $$$millions on things I just don't want or even care about (Co-Pilot, Recall, etc) instead of actually taking what they already have and making it WORK!!!