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)
For some reason my new Surface is shutting off randomly. I check the setting and a few other things but it's still randomly turns off without warning. I'm losing some of my school work because of it. Is anyone else having this problem?
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.
Hey Everyone,
As of 7/14, the fix for this issue has completed testing and is now live, please go update your Surface Pro via Windows Update to get the latest download. You can obtain this fix by checking Settings> Update & security > Windows Update
The Surface Pro Update History page has been updated with the details of this release and the update is also available on the Surface Pro Drivers and Firmware page as part of the MSI installation package available for download.
BryanH [MSFT]
Updating with the zip as outlined shouldn't lead to that message
(and I think the driver is the same for both i5 & i7: win64_154519.4678)
You are right. I was being a noob.
I installed it using the correct way (picking own location of the .inf file).
I was being to hasty before.
I am working now after a restart, here's hoping and fingers crossed that it solved the problem.
Hi again,
I have now been using the surface extensively for around 45 minutes after updating.
No auto hibernating issues as of yet... Which is better than all the other days; it should have happened at least twice already.
Me = happy
Thank you.
Will report if anything changes, but I suggest other people try this too. Might just be the fix.
Best regards
Kevin
I am testing this now.
