Taskbar Auto-Hide Broken » Forum Post by trparky

Uninstalled Start11 V2 (non beta) deleted settings.

Rebooted

Installed Start11 V2 beta 2.0.5

Rebooted

Still having task bar auto hide issues.

Note: If I disable autohide in Start11 and enable it in Windows settings, it works fine. But I loos the taskbar height and rounded corners features from Start11.

Successfully updated karma reason!

Quoting johnson0508,

reply 76

Uninstalled Start11 V2 (non beta) deleted settings.

Rebooted

Installed Start11 V2 beta 2.0.5

Rebooted

Still having task bar auto hide issues.

Note: If I disable autohide in Start11 and enable it in Windows settings, it works fine. But I loos the taskbar height and rounded corners features from Start11.

Unfortunately that might be all we can do for you as it continues to work just fine on test boxes. The changes were made assuming what could cause it but it is almost certainly something interfering with it.

Successfully updated karma reason!

Quoting Neil Banfield,

reply 75

Quoting Vipe-Ness,

reply 71

Quoting basj,

reply 70

Start11 V2.05 Beta just released. And there is some new development on Autohide issue. Please test it and report back.

https://forums.stardock.com/524909

Thank you,

Basj,
Stardock Community Assistant

Thank you. I have installed the latest beta version and so far no issues with the autohide feature. I will keep an eye on it over the next few days.

However, the Vertically centre the taskbar buttons on the taskbar under Enhanced Taskbar Settings isn't working; they are staying left justified on the taskbar. It was working before turning on Enhanced Taskbar Settings.

That setting is purely for vertical alignment so that would be normal. Based on your other bug reports I would recommend you disable that option.

If you want to centre horizontally this is a setting on the start button page.

You are correct that, that option had no effect on the centering of the buttons. The user would think that under the Taskbar menu that it was related to that option. I have untoggled that and went under "Start Button" and centre aligned taskbar buttons; which works now.

As for my other bug reports; those are still happening and have not been resolved with that change. Also, the auto-hide sporadically doesn't work as reported in a previous post above but majority of the time, auto-hide does work.

Start11 v2 - beta 2.05 - taskbar popping issues

Start11 v2 - beta 2.05 - taskbar popping / taskbar pins

Successfully updated karma reason!

Here is an updated video depicting the issue of the taskbar popping; it occurs consistently.

Successfully updated karma reason!

In the new video, I managed to capture the issue of the taskbar not consistently showing up, as shown at the beginning of the video. Subsequently, various other occurrences took place, and I'm finding it challenging to articulate and explain them accurately.

Successfully updated karma reason!

Quoting Vipe-Ness,

reply 79

Here is an updated video of it happening; happens constantly:

Is this only happening with autohide enabled or is the animation happening regardless?

And is it only with that app open?

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+690

I too could not reproduce the issue until I tried to record it:

https://cdn.stardock.us/support/uploads/2024-01-11_14-05-19.mp4

In other words, with the ShareX recording overlay, I could see it happen. Logic would follow that is the case with you all, that there is a screen overlay (Steam, Nvidia, etc) causing issues.

Perhaps the easiest way to test \ eliminate them is to do a clean boot:

https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

Another would be to fire up Windows Sandbox and try under it (it will eat a license so be sure to 'uninstall' before killing the Sandbox)

https://www.windowscentral.com/software-apps/windows-11/how-to-use-windows-sandbox-on-windows-11

Sean Drohan
Stardock Product Lifecycle Manager

+1

Successfully updated karma reason!

Quoting sdrohan,

reply 82

I too could not reproduce the issue until I tried to record it:

https://cdn.stardock.us/support/uploads/2024-01-11_14-05-19.mp4

In other words, with the ShareX recording overlay, I could see it happen. Logic would follow that is the case with you all, that there is a screen overlay (Steam, Nvidia, etc) causing issues.

Perhaps the easiest way to test \ eliminate them is to do a clean boot:

https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

Another would be to fire up Windows Sandbox and try under it (it will eat a license so be sure to 'uninstall' before killing the Sandbox)

https://www.windowscentral.com/software-apps/windows-11/how-to-use-windows-sandbox-on-windows-11

Sean Drohan
Stardock Product Lifecycle Manager

To share, those videos were recorded after a system reboot. I do not have NVIDIA overlay turned on or GG overlay turned on as those apps create a nuisance while gaming and are just a pain to see constantly popping up and wasting resources.

The taskbar issue still happens when Steam is not running.

Successfully updated karma reason!

Thank you sir that worked. I did the clean boot process and autohide worked. So I somewhat systematically started reenabling services until it stopped working. The culprit was "nvidia local system container". I have turned all other services back on except that one and autohide works normal. Turn that back on and autohide only works when there is a window open on the main monitor.

So now to determine if I really need that service or if I can tweak it's settings in the NVIDIA control panel.

Successfully updated karma reason!

Quoting johnson0508,

reply 84

Thank you sir that worked. I did the clean boot process and autohide worked. So I somewhat systematically started reenabling services until it stopped working. The culprit was "nvidia local system container". I have turned all other services back on except that one and autohide works normal. Turn that back on and autohide only works when there is a window open on the main monitor.

So now to determine if I really need that service or if I can tweak it's settings in the NVIDIA control panel.

As a follow up incase anyone is having issues with the same service. That service is only used by the GeForce Experience app. I never use it, so I uninstalled and it removed the NVIDIA Local System Container service.

+1

Successfully updated karma reason!

Quoting johnson0508,

reply 85

Quoting johnson0508,

reply 84

Thank you sir that worked. I did the clean boot process and autohide worked. So I somewhat systematically started reenabling services until it stopped working. The culprit was "nvidia local system container". I have turned all other services back on except that one and autohide works normal. Turn that back on and autohide only works when there is a window open on the main monitor.

So now to determine if I really need that service or if I can tweak it's settings in the NVIDIA control panel.

As a follow up incase anyone is having issues with the same service. That service is only used by the GeForce Experience app. I never use it, so I uninstalled and it removed the NVIDIA Local System Container service.

Really appreciate you report back your finding here. Hopefully it would help all others who have similar issue.

Thank you,

Basj,
Stardock Community Assistant

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+690

Quoting johnson0508,

reply 84

Thank you sir that worked. I did the clean boot process and autohide worked. So I somewhat systematically started reenabling services until it stopped working. The culprit was "nvidia local system container". I have turned all other services back on except that one and autohide works normal. Turn that back on and autohide only works when there is a window open on the main monitor.

So now to determine if I really need that service or if I can tweak it's settings in the NVIDIA control panel.

Very good news. That is never fun but exactly what we would need a client to do, tyvm Johnson.

Quoting Vipe-Ness,

reply 83

To share, those videos were recorded after a system reboot. I do not have NVIDIA overlay turned on or GG overlay turned on as those apps create a nuisance while gaming and are just a pain to see constantly popping up and wasting resources.

The taskbar issue still happens when Steam is not running.

If you did the same, a clean boot, it would eliminate doubt about what may still be lingering (and why we ask for clients to do it).

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting johnson0508,

reply 84

Thank you sir that worked. I did the clean boot process and autohide worked. So I somewhat systematically started reenabling services until it stopped working. The culprit was "nvidia local system container". I have turned all other services back on except that one and autohide works normal. Turn that back on and autohide only works when there is a window open on the main monitor.

So now to determine if I really need that service or if I can tweak it's settings in the NVIDIA control panel.

Great! I tried to stop that service and the autohide then work as I would expect. I even didn't do any restart, update or anything. Also, I'm still on version 2.03.

Now the questions are: what is the purpose of this service and if it is nonessential how to prevent it from starting?

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+690

Quoting MalakAdonai,

reply 88

Now the questions are: what is the purpose of this service and if it is nonessential how to prevent it from starting?

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting MalakAdonai,

reply 88

Now the questions are: what is the purpose of this service and if it is nonessential how to prevent it from starting?

Here is a link to the Nvidia GeForce Experience FAQ:

https://www.nvidia.com/en-us/geforce/geforce-experience/faq/

Successfully updated karma reason!

The NVIDIA LocalSystem Container process is an integral part of NVIDIA graphics drivers, responsible for managing and providing system-level services for NVIDIA software and hardware components. It runs in the background to ensure optimal performance, compatibility, and power management for NVIDIA graphics cards.

Or, at least that's what Google says.

Great. So, we have to disable a critical component of the nVidia driver for our video cards in order for this issue to be fixed? Um... that's not a fix.

Successfully updated karma reason!

Quoting trparky,

reply 91

The NVIDIA LocalSystem Container process is an integral part of NVIDIA graphics drivers, responsible for managing and providing system-level services for NVIDIA software and hardware components. It runs in the background to ensure optimal performance, compatibility, and power management for NVIDIA graphics cards.

Great. So, we have to disable a critical component of the nVidia driver for our video cards in order for this issue to be fixed? Um... that's not a fix.

I understand; indeed.

I've reached a point where I've decided to discontinue using this product. Each time I raised concerns, it seemed as though I was being perceived as the one at fault. This will be my final interaction with the product, including any potential upgrades, due to consistent issues.

Successfully updated karma reason!

Haha, the hateraid is strong in here. Nvidia GeForce Experience is not an integral part of NVIDIA graphics drivers. Per NVIDIAs web site:

"GeForce Experience is the companion application to your GeForce graphics card. It keeps your drivers up to date, automatically optimizes your game settings, and gives you the easiest way to share your greatest gaming moments with friends."

It is basically a vehicle for your PC to call the mothership and upload your data. I am not a high end gamer, but I play a few higher end games and have had no problems with the graphics since uninstalling the GeForce Experience app. From my perspective, I feel I have got more support on this issue than I expected from a $6.99 piece of software, but everybody is different. I hope you guys find a solution that works for you, I know I did.

+1

Successfully updated karma reason!

Quoting Vipe-Ness,

reply 92

I understand; indeed.

I've reached a point where I've decided to discontinue using this product. Each time I raised concerns, it seemed as though I was being perceived as the one at fault. This will be my final interaction with the product, including any potential upgrades, due to consistent issues.

I ultimately hope that Stardock can truly fix this issue now that we've found the root cause of this issue.

Successfully updated karma reason!

As a quick reminder it has just been around a week since the user posted the link between GeForce Experience and the issue on their computer. We aim to be responsive on bug reports, but for an issue that does not cause crashes, has a temporary workaround and has limited user impact (autohide is I think everyone would agree a niche thing) I do need to set expectations here.

Now that said, this issue has been investigated this morning both with 2.03 and 2.05 but without the results we all want. The issue did not reproduce on a Windows 11 test machine with a nvidia graphics card added. Now this may mean there is a setting in GeForce Experience that needs to be turned on to trigger this.

Would it be possible for someone who has this issue to let us know what settings they are using and what version of GeForce experience you are using along with the graphics card and driver version and OS scaling factor.

We wish to resolve the issue and have previously made changes to try to work out what could possibly be going wrong but I think the key is to be able to reproduce it locally.

It also occurs to me to ask if you are also running anything that might interact with the desktop like Stardock Fences?

Also it would be expected that it might have trouble when recording the screen because some screen recording apps put an overlay over the entire desktop which could prevent mouse messages arriving at the very edges of the screen

Successfully updated karma reason!

Quoting trparky,

reply 91

The NVIDIA LocalSystem Container process is an integral part of NVIDIA graphics drivers, responsible for managing and providing system-level services for NVIDIA software and hardware components. It runs in the background to ensure optimal performance, compatibility, and power management for NVIDIA graphics cards.

Or, at least that's what Google says.

Great. So, we have to disable a critical component of the nVidia driver for our video cards in order for this issue to be fixed? Um... that's not a fix.

It is intended as a workaround for now whilst the issue is investigated further. That is also not a critical component as others have said.

Successfully updated karma reason!

Quoting Neil Banfield,

reply 96

It is intended as a workaround for now whilst the issue is investigated further. That is also not a critical component as others have said.

OK...

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+690

Quoting Vipe-Ness,

reply 92

I understand; indeed.

I've reached a point where I've decided to discontinue using this product. Each time I raised concerns, it seemed as though I was being perceived as the one at fault. This will be my final interaction with the product, including any potential upgrades, due to consistent issues.

Sorry you feel that way, Vipe-Ness, and that it did not work out for you in time.

I have refunded your purchase of Start11 v2.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

We have updated the start11 beta 2.05 with some more fixes.

One fix relates to autohide so it may impact this Nvidia related issue too depending on the cause of course.

https://forums.stardock.com/524909/get;3915022

Successfully updated karma reason!

Quoting Neil Banfield,

reply 99

We have updated the start11 beta 2.05 with some more fixes.

One fix relates to autohide so it may impact this Nvidia related issue too depending on the cause of course.

https://forums.stardock.com/524909/get;3915022

Not quite, but a lot closer to a possible fix.

When I drag my mouse cursor to the bottom of the screen it doesn't bring the taskbar back up, but a click of the mouse button does. I don't think that that has ever worked before.

+2

Successfully updated karma reason!