Reply #1 Top

What build of Windows 11 are you using? and what version of Start11?

That seems far more than it should be using.

Reply #3 Top

Hello, Sorry to hear you’re experiencing issues. It looks like you’re running a Windows 11 Insider Preview build. Please note that Stardock products are not supported on Insider Preview channels, as these builds are experimental and change frequently.

Kindly revert to the official Windows 11 release and retest your issue.

Thank you,

Basj,

Stardock Community  Assistant.

Reply #4 Top

Before you go to the trouble of moving off that build, there is a quick test that will tell you whether Start11 is even part of this.

Turn off the master switch that lets Start11 enhance the taskbar, then put the taskbar back on the left and watch Explorer again. If the CPU drops, it is Start11's taskbar handling. If Explorer still sits at 12 to 24 percent with that off, Start11 is not what is driving it and the build is the thing to change.

The reason I would look there first is that left and right taskbars arrived as an experimental feature in 2.5 and only on Windows 11 23H2 and up. Most of the taskbar work assumes a horizontal bar, so the vertical path is the least travelled part of it.

If you are not certain whether the enhanced taskbar is currently on, open the taskbar settings and look for the options to hide taskbar buttons. Those are only offered when it is enabled.

Worth noting either way: whether the CPU sits high constantly, or only while the mouse is over the taskbar. Those point at different things.

Reply #5 Top

Same behavior here, on a retail build rather than a preview one, so the Insider Preview explanation in reply #3 does not cover this case.

System:
Windows 11 Pro for Workstations, 25H2, build 26200.9711 (retail)
Start11 2.8.2.0
Ryzen 7 5800X3D, 64 GB RAM

Measurements of explorer.exe, 20 second samples, no user interaction:

Vertical taskbar on the primary display: 66.7 percent of one core
Horizontal taskbar: 5.8 percent of one core

Method: only S11_VerticalTBModePrimary was changed, from 1 to 0 and back again. EnableS11Taskbar stayed at 1 for both measurements, and start10_64.dll was loaded into explorer.exe in both. All six recorded taskbar values were restored afterwards and verified unchanged.

That answers the suggestion in reply #4. The enhanced taskbar master switch is not the variable, because it was enabled during both measurements. Vertical mode on its own accounts for the whole difference.

Two further details that may help narrow it down:

1. The load is constant. It is not limited to times when the pointer is over the taskbar. Before I restarted it, explorer.exe had accumulated 113 CPU hours across 202 hours of uptime, an average of 56 percent of one core, with no Explorer windows open at all.

2. It is one thread, the main thread of explorer.exe, created when the process starts. It performs no disk I/O while consuming the CPU, so this looks like a loop rather than work.

Updating from 2.81 to 2.82 made no difference.

Best regards,
Chris

Reply #6 Top

We will take look at this as this shouldn't be the case.

Do you have anything else running which might reserve any screen border space?