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]
Hey AlanLefor,
This update launched on 7/13 and can be downloaded from Windows Update today (Settings> Update & security > Windows Update), but for our driver updates we do not assign a KB# like we do for the Windows OS updated. Driver updates are designated by the specific version number of the updated driver.
example, for this update:
Surface - Firmware - 233.1763.257.0
You can also validate if you have received this update in your Windows Update history Settings> Update & security > Update History > expand the Driver Updates section to review the installed drivers.
BryanH
Thank you! I haven't had any more random hibernations!
Is that fix really out there? It is now July 18, and I haven't seen it yet, at least when I tried Windows Update today. Is there a KB number for it? Thanks very much.
After two days of testing I think I can say that the problem has been soved for me too!
