I bought my Surface Pro 2 just 3 or 4 days ago, and having spent the last couple of days installing all the updates (including the latest firmware one) and the odd bit of software, noticed that the battery life certainly wasn't living up to what it was claimed to be. Checking the Task Manager when the device was essentially idle showed a fairly consistent 22% CPU utilisation, so I started searching online for reports of this problem.
Having found this thread, I can confirm that the microSD problem works for me, with removing that immediately dropping the CPU usage down to a much more healthy 0 to 1%. However, before I tried that, my search resulted in me stumbling by chance upon an entirely different solution.
One of the bits of software I had installed over the past day or two was the Google Search app from the Microsoft Store, and I used that to look for reports into this problem. I then returned to Task Manager without terminating Google Search - and discovered that the cpu utilisation had dropped to around 1%. I didn't connect the two straight away, but after I did make the connection and tried shutting down and restarting Google Search a considerable number of times, I found that the effect was consistently reproducible - shut down Google Search and the CPU climbed to 22%, start it again and the CPU instantly dropped to almost zero, without fail.
Can anyone else confirm or otherwise that they get the same effect here? And can anyone else explain why this should be happening? Ok, it's a relatively convenient work-around to keep GS running in the background (much more so than doing without my microSD card), and the memory overhead isn't very much, but it's still hardly satisfactory as a permanent solution.
Having found this thread, I can confirm that the microSD problem works for me, with removing that immediately dropping the CPU usage down to a much more healthy 0 to 1%. However, before I tried that, my search resulted in me stumbling by chance upon an entirely different solution.
One of the bits of software I had installed over the past day or two was the Google Search app from the Microsoft Store, and I used that to look for reports into this problem. I then returned to Task Manager without terminating Google Search - and discovered that the cpu utilisation had dropped to around 1%. I didn't connect the two straight away, but after I did make the connection and tried shutting down and restarting Google Search a considerable number of times, I found that the effect was consistently reproducible - shut down Google Search and the CPU climbed to 22%, start it again and the CPU instantly dropped to almost zero, without fail.
Can anyone else confirm or otherwise that they get the same effect here? And can anyone else explain why this should be happening? Ok, it's a relatively convenient work-around to keep GS running in the background (much more so than doing without my microSD card), and the memory overhead isn't very much, but it's still hardly satisfactory as a permanent solution.
