Hello! Hoping someone will be able to help me. I have Googled until I can't see straight and nothing seems to be working. Here is my issue:
My IBM ThinkCentre M series on Windows 10 Pro will not wake from sleep or hibernate.
I have changed every setting I can find, both on my own and from Googling the issue.
The computer still fails to wake. I have tried different keyboards and mice, as well as the wake settings on those devices as well.
Could this be a graphics card issue? The screens stay off (sleep) and even when turned on manually, say no input, even though the computer is on and (maybe) awake? I can not hear the computer processing like I normally do, though, when trying to wake it.
If I manually hibernate the computer (click the windows icon, power, then hibernate), the computers screens turn off, but the power light stays on. The computer will not wake from this state unless I hold the power button until the light goes out, then restart. But upon restarting, it wakes like it's been in hibernation, not a fresh restart.
If anyone has any ideas, they would be much appreciated - this is driving me crazy!
UPDATE 9/26/19 11:37am: While doing ALL of the below suggestions including disabling sleep/hibernation. The computer would NOT wake this morning. The screens are set to turn off after 30 minutes. That is the ONLY active power-saving setting. I re-confirmed that both sleep and hibernation are not active and they definitely are not. I also confirmed all USB devices and ports are allowed to wake the computer. I updated the BIOS as well still to no avail. Any ideas? This is dual monitor setup, one on VGA, the other on DisplayPort.
If it is any consulation, you are not alone in having problems with sleep and hibernate and there is no universal solution. (Googling the issue, when people have found a solution it is different for each and one claimed his problem wenr when he uninstalle VirtualBox).
You could try updating the BIOS and HP have a lpage on it which probably applies to all makes: https://support.hp.com/gb-en/document/c03383935
I believe update 1903 broke "fast boot":
I'm in the same camp with Viking Michael. I've ran into similar problems, especially it seems when there were older USB peripherals involved. The easiest solution was to disable sleep/hibernation.
With an SSD, startup is usually pretty fast, so if power savings are a concern, turning the computer completely off isn't as bad a proposition as it used to be.
Hi. rather than destroy your sanity trying to figure out how to get suspend and hibernate to work how about disabling both of them as many others have suggested? Then use the screen saver to off the monitors while users are logged on. If not screen saver then go to the power settings and make sure the monitors are the only only devices set to sleep after 30 minutes or so.
Some IT pros my disagree, but I see no purpose for 'Sleep Mode" and I have a special disdain for 'Hibernate'. These options more often than not lead to issues where you end having to manually power cycle your computer. If you're worried about a dying battery on a laptop, setting a screen timeout time should be sufficient enough to save you some battery life. Long of the short, turn off sleep and hibernate and call it a day.
A screensaver indeed! I like to throw in one of those BSOD screensavers every now and then! While I use hibernation myself, I started disabling it on systems I support back around the Y2K era. I found a virus/rootkit that had embedded itself in the hiberfile and it took a while to figure out that's where it was hiding. I also started killing restore points as there was an infection there as well. Of course, the experience level of each user was taken into account but I'm telling you, manually cleaning out a rootkit (possibly before the term was widely used) was not fun. I had search and destroy 33 registry keys and figure out how and from where certain files were being rewritten at system bootup. "Hijack this" was a critical tool for that as was old ZoneAlarm for blocking/tracking internet access requests...fun times.
I don't recall any issues regarding wake up except in the last year or so, where USB power conservation settings and/or USB pass-thru on monitors seemed to be the culprit...No video signal due to a system sleep/hiber state...No USB response.
I had the same issue on Thinkcentre M Series with Windows 10 Pro/Ent in SSD. Tried multiple keyboard and mouse replacement, repairing windows, and so on. Finally, something came to my mind and checked the Partition Style. Disk Management>Right Click the Disk> Properties>Volume>Partition Style. I made the boot drive GPT which caused the mentioned issue. Changed the drive from GPT to MBR fixed for me.
Some IT pros my disagree, but I see no purpose for 'Sleep Mode" and I have a special disdain for 'Hibernate'.
And some very experienced IT pros will beat that drum, wave that flag, and shout until they're hoarse at the hurricane of mindless Microsoft Sycophancy until the sheep wander aimlessly away. This has been a problem since at least Vista, and from the evidence at hand, it appears Microsoft is not expending a nano-moment of coder time doing anything about it.
PowerCFG /Hibernate OFF
OTOH, I've earned some pretty decent coin fixing this for people, so maybe I doth protest too much...
UPDATE: While doing ALL of the above suggestions including disabling sleep/hibernation. The computer would NOT wake this morning. The screens are set to turn off after 30 minutes. That is the ONLY active power-saving setting. I re-confirmed that both sleep and hibernation are not active and they definitely are not. I also confirmed all USB devices and ports are allowed to wake the computer. I updated the BIOS as well still to no avail. Any ideas? This is dual monitor setup, one on VGA, the other on DisplayPort.
I always advise people that the best way to avoid problems with Hibernate and Suspend is to not use Hibernate or Suspend.
, I agree generally. I have had far greater luck with Hibernate than Suspend, but for low-tech users, I generally disable all forms of suspend at least. Besides, I've seen too often where users suspend, intentionally or not, and come back the next day or days later to find their system is dead. Also, when systems need to be restarted to correct a problem, there is no end to how these pseudo-off modes confuse people into believing they've rebooted when they haven't.
This is a problem with both of these modes, but so long as a "real" reboot isn't required, at least Hibernate acts more like a power off and preserves the battery and the delay for getting back to a particular point isn't all that long, particularly if it comes out of hibernation from an SSD.