From: Greg Ercolano <erco@(email surpressed)> Subject: [Q+A] Windows 8.1 upgrade caused rushtop to show an error in place Date: Wed, 22 Jan 2014 20:19:54 -0500 |
Msg# 2372 View Complete Thread (1 article) | All Threads Last Next |
> We upgraded a machine to Windows 8.1 the other day, > and while it's rendering OK, it isn't showing up in "rushtop". > > It shows this error in red in place of the usual cpu bars > for that machine: > > PdhLookupPerfNameByIndex(238): Can't connect to remote machine Confirmed: I upgraded from Windows 8 -> 8.1, and can now replicate the exact same issue in rushtop here. As you've noticed, it only affects the cpu info that shows in rushtop, it doesn't affect rendering or other reports. SOLUTION Short answer: the fix is to give Administrator privileges to the user the Rushd service is configured to run as. Then it works fine. DETAILS Seems Microsoft has locked out access to the cpu info through the PDH library to users in the admin group. Don't know why, but looking at the release notes, sounds like they closed some security holes and (accidentally?) closed cpu info access. This happened once before back in 2005 or so when rushtop wouldn't show cpus after a windows update, and the user had to be an administrative user to work normally. Then they 'fixed' that issue soon after, and it wasn't an issue again until now in Windows 8.1. |