@roguecode said:
@kegobeer-plex Please send it to me, along with the exact version number of Windows (Start > Run > “winver”)
Sent this morning. Hope it helps.
@kegobeer-plex
@mashuto
@Pete_AUS
@Beudbordel
I’ve been dealing with Microsoft on this, and the latest response suggests that it could just be a driver thing:
Downloads can be pulled from here: aka.ms/drivers/surfacepro4
Alternate locations:
· https://www.microsoft.com/en-us/download/details.aspx?id=49497
How to change update settings. https://www.microsoft.com/surface/en-us/support/performance-and-maintenance/install-software-updates-for-surface?os=windows-10&=undefined
This appears to have also been an issue with the Surface Pro 4.
Eugh, I give up trying to format this thing.
They’re waiting for a response, so please let me know if you’re able to check that.
Not sure if this one applies to me directly. I do not use a surface pro 4, but rather a surface book. I also keep my drivers up to date, and even did a manual driver install after the 7/14 driver update, so I am pretty sure I am running the latest drivers. And I can confirm that I am still seeing the same behavior as of a day or two ago with the latest 3.0.32 release. The only thing that might be different in my configuration is that for a while I had beta intel display drivers installed, but after the last surface driver update (which I did on or a day or two after the 14th), I should be back running the latest MS drivers.
I would be happy to double check this again and reinstall the drivers this evening and test for you if you would like.
I have a Surface Pro 3 and all the drivers are updated via Windows Update. I’ve never run any beta drivers. My drivers are the same versions as those available from a manual download.
Would you guys mind running the test again after making 100% sure that you’re on the latest version. And then also running the tests at the end of this and sending to me?
Thanks so much!
Is there a way to validate that particular firmware update is indeed the current version, and was up to date prior to / during the battery study?
I just want to validate that:
• the latest firmware is actually installed,
• and with that latest firmware, are the results still the same? (Same battery usage, from same background process, from same app, etc.)
o Even if/though it seems the issue is still occurring on the latest version, it’s possible that it’s now occurring for a different reason.
Also, windows has some built in commands for running reports to check for common battery drain issues. In addition to the study, is it possible to include results from the same machines, with the latest firmware, can you include the output results from the following commands?
powercfg /SLEEPSTUDY
powercfg /ENERGY
powercfg /BATTERYREPORT
@roguecode, I sent you my reports. All firmware and drivers are current, still the same results.
