Hardware

Sleepless In Seattle: Surface Sleep Bug Remains Elusive

Surface Pro 4 Hero

Last week, Microsoft pushed out a firmware update to its new Surface devices, the Pro 4 and the Book. While the firmware update did bring some needed updates including making the keyboard base more reliable when attached to the display, the most annoying bug was not squashed.

Both the Pro 4 and the Book suffer from a well-documented problem, they will not ‘sleep’. When you try to use feature of Windows with these devices, it will cause the battery to drain and they will get very warm when they should be in a low idle state.

Microsoft acknowledged in their forums that this bug was not fixed in the latest firmware update and that they are still working on the issue but offered no timeline for a resolution. The statement came from a Microsoft employee who is on the Surface team, “We know some of you are still experiencing issues, including issues related to power management, and we are working to address those as quickly as possible. We’ll publish additional updates as soon as they are ready.”

Sponsored Content

Passwords Haven’t Disappeared Yet

123456. Qwerty. Iloveyou. No, these are not exercises for people who are brand new to typing. Shockingly, they are among the most common passwords that end users choose in 2021. Research has found that the average business user must manually type out, or copy/paste, the credentials to 154 websites per month. We repeatedly got one question that surprised us: “Why would I ever trust a third party with control of my network?

This issue, which as been on-going since the device was released, is giving the Book and Pro 4 a bad which otherwise are fantastic devices. But, when you cannot trust your device to be ready when you need it, this becomes a serious issue for Microsoft who boasts that they have the most productive PCs on the planet.

It’s clear that Microsoft is getting a lot of flak for the issue but it should also be noted that Intel is part of the problem here as well. Insiders from the company state that this problem is related to the silicon used; we know this because other Windows 10 devices, not using the Skylake chip, do not have this problem.

The best work-around right now, is to make closing the lid on the Book or pressing the power button on either device hibernate the machine. It’s not a perfect solution as resuming your PC does take more time and you cannot resume the machine right where you left off like you can with sleep.

For now, when a fix will arrive is unknown and I suspect Microsoft will not give out any timeline until they are absolutely sure of it. Whatever the underlying issue is, it must be a serious problem as there is no way the company would be taking their time with this fix as it compromises the integrity of their premium devices.

Related Topics:

BECOME A PETRI MEMBER:

Don't have a login but want to join the conversation? Sign up for a Petri Account

Register
Comments (0)

Leave a Reply

Brad Sams has more than a decade of writing and publishing experience under his belt including helping to establish new and seasoned publications From breaking news about upcoming Microsoft products to telling the story of how a billion dollar brand was birthed in his book, Beneath a Surface, Brad is a well-rounded journalist who has established himself as a trusted name in the industry.
Don't leave your business open to attack! Come learn how to protect your AD in this FREE masterclass!REGISTER NOW - Thursday, December 2, 2021 @ 1 pm ET

Active Directory (AD) is leveraged by over 90% of enterprises worldwide as the authentication and authorization hub of their IT infrastructure—but its inherent complexity leaves it prone to misconfigurations that can allow attackers to slip into your network and wreak havoc. 

Join this session with Microsoft MVP and MCT Sander Berkouwer, who will explore:

  • Whether you should upgrade your domain controllers to Windows Server
    2019 and beyond
  • Achieving mission impossible: updating DCs within 48 hours
  • How to disable legacy protocols and outdated compatibility options in
    Active Directory

Sponsored by: