This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Split from this thread.
My SP4 gets very hot and drains the battery very fast even though it is asleep. I found it very hot in its sleeve and down to 28% earlier today. Found it dead later in the afternoon. This is one of MANY issues this device has.
(My SP4 is not part of the insider program)
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi All,
We released an update on 2/17/2016 that addresses this issue.
We recommend that you install this update to keep your Surface performing its best. You can get updates now by checking Settings> Update & security> Windows Update.
To confirm the updates are installed, check Settings> Update & security> Windows Update> Advanced options> View your update history.
Thanks,
Josh
I'm not saying it's a hardware issue ... ???
I know, I saw the same prior to TH2. That's why I went back to the September driver. As for someone working on it, glad to hear you know someone who is.
I did not experience this issue until 1511 and associated firmware/driver updates. If I had the device would have been back in the box and returned to the Microsoft Store where I bought it. If it is a hardware issue I guess Microsoft will be providing us all with a new SP4! Oh and those with Surface Books will be getting new hardware too.
10% per hour is high. The 15/11 numbers you posted in the screenshot are consistent with others here. With all the latest updates and drivers, my drain rate is 16 (GPU)/12 (CPU), about 4% per hour. I'm really hoping it's a driver issue. I reverted to using the display adapter driver from September for now, and the drain rate is a bit better, about 1.3% per hour.
As to whether or not Microsoft is aware of this and/or working on a fix, .. who knows. They probably figure people don't keep it in Connected Standby for a long time, so it's most likely not a high priority for them. It doesn't prevent us from using the device.
This is clearly not a hardware issue as it did not occur prior to build 1511 and associated firmware/driver updates.
I know that Microsoft is working it as I stated in prior threads. My communications with a Microsoft Engineer (who used to work for me) and the discussion during the incident report troubleshooting on the issue (Microsoft acknowledged that this was a known issue) confirms that Microsoft is fully aware of the issue and is working it.
I know, I saw the same prior to TH2. That's why I went back to the September driver. As for someone working on it, glad to hear you know someone who is.
10% per hour is high. The 15/11 numbers you posted in the screenshot are consistent with others here. With all the latest updates and drivers, my drain rate is 16 (GPU)/12 (CPU), about 4% per hour. I'm really hoping it's a driver issue. I reverted to using the display adapter driver from September for now, and the drain rate is a bit better, about 1.3% per hour.
As to whether or not Microsoft is aware of this and/or working on a fix, .. who knows. They probably figure people don't keep it in Connected Standby for a long time, so it's most likely not a high priority for them. It doesn't prevent us from using the device.
This is clearly not a hardware issue as it did not occur prior to build 1511 and associated firmware/driver updates.
I know that Microsoft is working it as I stated in prior threads. My communications with a Microsoft Engineer (who used to work for me) and the discussion during the incident report troubleshooting on the issue (Microsoft acknowledged that this was a known issue) confirms that Microsoft is fully aware of the issue and is working it.
