Something else I have been thinking about: you know the issue with WorkShelf sometimes using more CPU than it normally would for extended periods of time and that I was never able to track down despite extensive analysis, optimizing code, etc?

It only happens under Windows 11.

Something else unique to Windows 11 is its support for the Performance and Efficient cores of Intel CPUs since the 12900K.

Needless to say, Efficient cores are much slower than Performance cores.

What if the REAL reason the Winstep application *appears* to be using more CPU than normal is because Windows sometimes classifies it as a background process and has the Winstep process running on an Efficient core instead of a Performance core?!

Just food for thought.

Phew, that sounds like a heck of a lot of effort - with possibly uncertain results - for relatively little gain Jorge.

Not sure if it's for little gain. Over the years I've had a ton of people complain about the lack of jumplists in the NextSTART tasklist buttons, for instance. I assume most of these complaints referred mostly to the lack of a list of files recently opened by that application.