This content has been marked as final. Show 8 replies
Do you have the machine setting enforced for "disable sleep/hibernate"?... or whatever the exact wording is.
No. We have not enabled the "Reject suspend/hibernate requests" in Machine configuration.
Several laptop models work OK, even if some of theese periodically have delay in the hibernate compared to the setting in the Power settings in Control Panel. I guess that this is due to process activities which do not allow hibernate a the exact time, and it will then try again at a later time??? Messages from both sbclientmanager.exe AND other executable from other sw vendors indicate this in a popup message on the desktop.
We are conducting more tests on this to hopefully get an more exact fault situation. Will get back in 1-2 days with update.
Just a note to let you all know there is more than one person with this issue, I too have a machine not going into Hibernate, and the reject box is not checked.
The answer I got was that McAfee broke Hibernation. (5.1.7 broken, 5.1.3 ok)
Lenovo T60 errored with a BSOD the first time I enabled hibernation & tried it.
After the reboot, no more BSODs on hibernation, but an error message every time. At certain times, the Hibernation tab on the power mgmt applet disappeared as well. Very odd behaviour.
Standby still works. happy
this is reported fixed in 5.18 (5600)?
I applied the fix as noted in the KB Article. I am awaiting the user to get back to his desk to sync Laptop, reboot and test.
I will edit later with the result.
EDIT: Yes, the KB Article's procedure fixed the Hibernate Issue.
I have just tested build 5600 5.1.8 with hibernation. I am seeing no errors and seems to be hibernating as it should.
I installed Build 5600 in a test environment, and run some testing on the same model testing the Build 5502 on. Did se one occation of Black screen and no response to any keyboard command. Need to power off by pressing button for a few seconds.
BUT I have not been able to run extensive tests on this on multiple machines, and different models. Since this is not happening often in our environment, it is not sure we will run an upgrade just based on this problem. Will update if I get any new update on this.