True but...
Yeah, I've got a weak argument, but bear with me.
The error/crash only occurs when Taskbar Shuffle is used with Flash.
It seems to happen with Firefox, Chrome, and IE8 (dunno if TS is always installed nor whether it always involves Flash, but those seem to be the most common intersections).
It seems to me to be an API issue. The API is either written in such a way that it's easy for Flash to stomp on shared memory used by TS, or Adobe is trying to do something it shouldn't.
MS has control over the Win32 API. The OS controls what is legal or not.
Either MS's API needs to be tightened up to prevent Flash apps from stomping on someone else's shared memory, or Adobe needs to be slapped down for doing things outside the standard API.
This problem has been going on for years. Lots of people have this trouble, but the actual solution is very hard to find and not widely known. It shouldn't still be happening.
Adobe is the logical person to fix this, but if the OS and API were better then it wouldn't show up on the user's desktop at all. It would have been caught in the build process AFAICS.
And if MS hadn't broken their taskbar functionality over the years, then TS wouldn't be needed...
FWIW.
Cheers,
Scott.