ender`

Then you don't have StartAllBack active – this is the standard Windows 11 taskbar. Go to StartAllBack's Settings, and make sure it's not disabled for your account.

I've noticed a weird problem on one of my computers: if Explorer is restarted for any reason (eg. due to StartAllBack upgrade), Alt+Tab dialog stops working afterwards until I log out and log back in (meaning Alt+Tab behaves as Alt+Esc, since 24H2 removed the better, classic Alt+Tab dialog).

Here's a problem I noticed on two laptops so far – log in locally first, then log in with RDP, then log in locally again, and taskbar rendering will sometimes corrupt like this: The computers where I noticed this are quite different, one is Ryzen 5 230 with integrated graphics, the other one is 10th gen i7 with some mobile Nvidia card.

One thing you can try as a workaround: open Task Manager, kill explorer.exe process (or run taskkill /im explorer.exe /f), then start Explorer again.

Is anybody else having problems accessing startallback.com (and startisback.com)?

Here's a problem I have when RDPing to Volterra (ARM64 Windows): The problem only appears when connected with RDP and moving mouse over Start menu items. Changing colour and transparency style has no effect.

It opens on whichever monitor the focused window is.

Maybe just enable transparency, and let the wallpaper changing take care of the rest (assuming you have a slideshow set up for wallpapers).

That bug goes back at least to XP.

Slovenian: https://eternallybored.org/misc/startallback/sl-si.txt BTW, Plumpness → Aura does not work properly in high contrast mode (the border is completely transparent – maybe the setting should be removed and Buffer used always if anybody wants to use Plumpness in high contrast); I also noticed that with Windows 11 default high contrast themes the Settings window colours are quite bad in the left column (ironically, this doesn't happen with the customised theme I use, otherwise I'd report this earlier).

I noticed a small bug – sometimes when I hover over a pinned icon (usually from the program that I just closed), only half of the highlight is painted: And when this happens, the neighbouring icon doesn't get a highlight on hover at all.

It's a bit too late now, but in the future if you're planning to reinstall Windows, export the Registry key HKEY_LOCAL_MACHINE\SOFTWARE\StartIsBack\License before you reinstall, then import it back.

I just upgraded my main workstation to 24H2, and I noticed that some of my taskbar settings were lost, specifically the taskbar was only 1 row high, and my Quick Launch toolbars were missing (is SaB using Windows' own Registry settings for this, and Microsoft reset them?). Also, please add a classic Alt+Tab dialog, the modern one is so much worse for my workflow.

I noticed a problem with classic Control Panel when StartAllBack's dark mode is enabled: the (keyboard) focus rectangle is not visible at all. This only affects Control Panel, and only in dark mode (in light mode and in high contrast mode there are no problems); it doesn't matter what the view is set to, it happens in Category, Large Icons and Small Icons views. I'd post a screenshot, but there's nothing to show at all.

That's always been supported – look in the Settings → Start Menu → scroll down to Right side items → Control Panel.

I noticed something funky today – the taskbar on one of my computers was suddenly different colour, and also wasn't auto-hiding – Windows somehow toggled the setting. After enabling auto-hide again, it went back to the usual colour, and if I disable it, it changes colour again: Autohide disabled: Autohide enabled:

Exactly, you purchased a game license, so you should ask the game support why it's triggering on StartAllBack – this is not something Tihiy can solve (it's like when AV products have false positives – there's basically nothing the software author can do, it has to be the AV company that needs to fix their s***).

I've been using multiple QuickLaunch toolbars practically since they were introduced with the IE4 desktop update – they are my main way of launching programs, specifically those that I use regularly, but not all the time (the programs that I use all the time have been pinned since that's been introduced in Windows 7). OTOH, I never missed the ability to have toolbars on secondary displays.

Right-click the taskbar, use the Toolbars menu?

No, the windows that were covering it weren't topmost (TigerVNC Client and Ripcord [Discord client], both of which are stretched to fill the full height of the monitor, but not maximised), though the taskbar sure behaved as if they were topmost as long as it didn't have focus; I then started RoyalTS, which I do run maximised on secondary screen, and I couldn't get the taskbar to appear at all by using my mouse, though after I closed RoyalTS, taskbar now behaves normally again. and appears on top of other windows. No idea what triggered this.

Today the taskbar on my secondary screen started appearing behind windows (it's set to auto-hide); no idea what triggered this (Windows 11 23H2 22631.4169, StartAllBack 3.8.10). There's one weird thing I just noticed – if I click the taskbar, it comes to top, but as soon as another window gains focus, the taskbar will appear behind all other windows.

My problem is that I am running on a tablet (and sometimes even use it as a tablet, with on-screen keyboard), but those gaps between files in Explorer really don't do anything useful for me.

Feature request, if possible: Explorer ignores "Compact view" and "Show checkboxes" options when it thinks it's running on a tablet, any chance to have StartAllBack override this and make it honour the settings?

Here are two Explorer dumps from the last few days, from different computers: https://eternallybored.org/misc/startallback/dumps/

A few times so far I've had Explorer freeze during login – taskbar appears, but only the Start Menu button is painted, everything else is empty; wallpaper also doesn't appear, nor do any of the desktop icons. Nothing responds to clicks, I have to kill and restart Explorer, then it works fine. Any way to help troubleshoot this (I've had this happen both on my 23H2 x64 and 24H2 Arm64 machine; IIRC, it also happened after SaB upgrade once)?