The two most recent Win10 Builds — namely 16215 and 16226 — have brought lots of changes and trouble to intrepid Windows beta testers. My desktop PC weathered recent builds admirably, but not my Dell Venue Pro 11 7139. I couldn’t install 16215 on that PC (not from Windows Update, not via an in-place upgrade, nor even a clean install). After uninstalling .NET 3.5, as suggested in the release notes, 16226 did install. But it’s been plagued with issues. The absence of .NET 3.5 means some favorite programs don’t work. Alas, CPU Meter can’t pick up Core Temp data without it, and the Codeplex version of RAPR.exe doesn’t work either. Worse, it means that Office 2016 won’t run (it also needs .NET 3.5; see end of thread for a possible fix). On the plus side, Win10 Build 16226 adds GPU Task Manager info. Thus, it can now show what’s going on with your graphics card. Here’s a quick peek:
GPU information from the latest version of Task Manager in Build 16226.
When Win10 Build 16226 Adds GPU Task Manager Info, What Does it Show?
Good question! The preceding screen capture is NOT the default view from this new facility. It appears on the Performance tab in Task Manager. Notice it shows metrics for various rendering subsystems: 3D, LegacyOverlay, Compute_O, and VideoDecode at the upper right. I got that display by right-clicking the GPU item at upper left, then picking “Multiple engines” from the pop-up menu entry “Change graph to…” The default is called “Single engine.”
But it only shows the 3D entry by itself. Because Multiple Engines is more interesting and informative, I’ve switched to that view instead. That’s much as I routinely do with the CPU entry. There, “Change graph to…” Logical Processors shows a panel for each execution thread.
This GPU capability rolls into mainstream Windows 10 when the Fall Creator’s Update is released, probably in September or October of this year. It makes a nice addition to Task Manager, and I’m glad to see it included in the overall mix. Until then, non-beta users will have to rely on tools like TechPowerUp’s excellent GPU-Z to show them what’s going on with their graphics cards instead.
[Note Added late morning 6/23: Anyone else bitten by the .NET 3.5 Framework issue on 16226 should try this fix. It worked for my Dell and conferred the added bonus of restoring Task Manager to normal operation. Run msconfig.exe, and on the boot tab direct your PC to boot into Safe Mode. Restart the PC, then use Winkey-R to run “Control Panel” to quickly access Programs and Features/Turn Windows Features On or Off and add .NET Framework 3.5 back in there. Then, use Winkey-R with “msconfig.exe” and go to the boot tab to turn off the Safe Mode checkbox. Reboot, and you’re back in business! Thanks loads to user Waltc who posted this information in thread #226 at TenForums.com.]