If they let Bob, Carol, Ted, and Alice work on PC version - things might move faster. If they let Larry, Moe, and Curly work on tablet version - things might move faster. If they let Ben and Jerry work on the phone version - things might move faster. If they let Zeke and Gus work on whatever other versions there are - things might move faster. MS seems to be following the "same-sex-marriage" theory. Sounds great in the beginning, not so good in the end.
I haven't tested games yet (scanning D3 and SC2 from backups atm), but in order to get the launcher running; set the Battle.net exectuable found in C:\Program Files (x86)\Battle.net\Battle.net.5383 to Windows 7 compatibility (Windows 8 didn't work). May have to run it as admin too, but not entirely sure (I have UAC disabled). Probably have to set the executable compatibility mode each time the client updates also (if it's still incompatible), but that shouldn't be a huge issue. Edit: SC2 and D3 both run.
Firefox is the one app that uses taskbar progress that doesn't trigger the problem for me in the first place. Does it for you? If so, which version?
To be quite honest, I don't know. I use Chromium as my default browser and I can confirm the leak there. I rarely use Firefox. It's possible that Firefox utilizes the progress feature in a way that doesn't cause it. Seems to happen more with MPC-HC though.
I had a quick look at the MPC-HC, Firefox, and Chromium source code (fortunately, they are all open source), and couldn't find any major differences in how they utilize the progress bar feature. Basically, there's only one possible way for an application to use this feature, which is through the ITaskbarList3 COM interface that provides the SetProgressState and SetProgressValue APIs (sorry if being a little technical). Firefox and Chromium update the taskbar progress pretty straightforward and isolated (by "isolated" I mean that the function that is responsible for updating the taskbar progress is not doing anything else than its intended purpose - it updates the taskbar progress and that's it). It's a little bit different in MPC-HC, where the taskbar progress update is tied to updating the seek bar of the player, although only triggered when the show taskbar progress option is enabled. Have you rechecked if disabling the taskbar progress update in MPC-HC prevents the leaking? If not, it could also be a bug in ATL/MFC, which would explain why Firefox isn't affected - MPC-HC builds on MFC for its UI, and Chromium on WTL (which is an extension to ATL/MFC), while Firefox uses its own UI framework for presentation.
Anyone try using Eyefinity on build 9888 by some chance? Bezel compensation won't work for me (screens flicker a bit; then Catalyst says display setup has changed). I'm not sure if it's because of the 14.12 driver, Windows 10, and/or build 9888.
When I shut down my system from the 'Start' screen it restarts itself instead of shutting down but when I do that from the desktop or log-in screen it normally shut down. Is anybody having the same issue in Build 9888?