Jump to content

StartAllBack for Windows 11


Recommended Posts


Posted
2 hours ago, Uiti P. Uszer said:

When installing SAB I got this Error: Exception EAccessViolation in module StartAllBackCfg.exe at 000000000000058ab25
Can someone help with this?

Same here 

 

Posted

Any ideas why taskbars on secondary monitors aren't hiding with recent updates installed? (the above version doesn't fix this problem)

Posted
2 hours ago, Tihiy said:

No idea, unfortunately. Any triggers?

It happens both on reboot or upon changing projection settings (Win + P) from "Second screen only" to "Extend". In my case I have a 3440x1440 primary + 1920x1080 secondary setup and it generally doesn't happen on my primary IIRC, but it happens almost always on the secondary and I have to right click -> go to SAB settings and toggle autohide off and on and then it's fixed until the next reboot/projection setting change. Is there any kind of logging/dumps I/we can send your way to potentially debug this?

Posted
3 hours ago, Tihiy said:

No idea, unfortunately. Any triggers?

For me it usually happens after waking up my monitors from sleep (on home machine this causes the primary monitor to connect back – when it goes to sleep, it disconnects from the PC, as if it was physically disconnected; on my work machine I'm not sure, it also seems to sometimes happen after waking up monitors from sleep, but none of those disconnect; installing the test version linked above immediately triggered the problem on both computers).

Both of my computers have 3 monitors, with centre being primary. Both are also set up with high contrast mode and use high DPI (one has all 3 monitors at 225%, the other one at 168%).

Sometimes the taskbar stops hiding on only one secondary monitor, but most often it stops hiding on both; also, sometimes when this happens, the taskbar becomes completely transparent, except for text and icons (it still receives mouse clicks in this state). The problem started with October update, and persists with KB5067036 (26200.7019).

Disabling and re-enabling auto-hide makes the problem go away for a while.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...