[SOLVED] Sleep mode missing

[backwoodsman]

I have 2 identical HP Probook 645's, both new installs of Win10, upgraded to 1903 and fully updated. Sleep mode is there and works fine on one of them, but completely missing on the other. It's nowhere in any settings or shutdown menu. It does seem to work normally when you hit the Sleep key, except that there's no slowly flashing light telling you it's sleeping. I reset Windows; no change. Sleep works normally under Linux, so it's software, not hardware.

I'm drawing a blank. Any ideas?

 

[Porthos]

It's nowhere in any settings or shutdown menu.

Two words, Video Driver.

 

[frase]

My sleep mode is missing as well, takes me three hours to get to sleep!

 

[backwoodsman]

Two words, Video Driver.

Looks like that was it. It was still updating after the reset, and hadn't installed the video driver yet. The strange thing is, before the reset, it had the correct driver, and sleep didn't work. And now, after the reset, audio doesn't work even though it has the right driver and worked fine before. I guess I'll nuke & pave and hope for the best.

Meanwhile, the other identical machine still works fine. Gotta love Windoze 10.

 

[Porthos]

audio doesn't work even though it has the right driver and worked fine before.

Uninstall the driver and let Windows install the generic driver.

 

[Porthos]

My sleep mode is missing as well, takes me three hours to get to sleep!

Why I post at odd times taking my timezone into consideration.
My other issue is the computer is in beteen my bed and the toilet.(middle of the night trips)

 

[britechguy]

I know this topic is over a year old, but since I believe my issue is precisely the same, I'm reviving it.

What I want to know is whether anyone has ever experienced this with AMD's own Radeon Update application. My partner's machine and mine are hardware twins, though his still has Win10 Home on it and I upgraded to Pro. I've done many, many upgrades to Radeon using the AMD Radeon Software Installer but never encountered this issue, until now.

Sleep is just gone entirely on his machine, even in advanced power settings (where it only shows Hibernate after and Allow wake timers options under Sleep).

I'm trying a Repair Install with the AMD Radeon Software Installer that's employing the factory reset (nuke any and all old drivers and software from AMD) as part of it. We'll see if that works (and I'll report back).

But has anyone else had this with AMD Radeon specifically?

 

[Porthos]

Sleep is just gone entirely on his machine, even in advanced power settings (where it only shows Hibernate after and Allow wake timers options under Sleep).

Assuming sleep is missing in the start menu as well.
I usually just uninstall the driver and use whatever Windows update provides. AMD drivers are a pain and go unsupported real fast.

 

[britechguy]

Assuming sleep is missing in the start menu as well.
I usually just uninstall the driver and use whatever Windows update provides. AMD drivers are a pain and go unsupported real fast.

I have not had anything AMD Radeon go out of support yet, over a number of years now. My old standby laptop has AMD R5 Radeon Graphics on board and that's still supported by the AMD Radeon software and gets regular upgrades. That's exactly why I use the Radeon software to maintain the graphics drivers.

All of that being said, if this repair install doesn't reverse the issue I will nuke the AMD software in its entirety from Programs and Features, let Windows 10 select a generic driver, then start again from scratch with the AMD stuff later. I really prefer for all of my machines to be operating in as close to "exactly the same way" as possible when possible.

 

[britechguy]

The issue is also now [Solved] for me.

Running the Radeon Installer again, which did show "repair mode," and including the "factory reset" option as part of it, which removes all old AMD software and drivers leaving only the latest ones, did the trick.

I don't know if the original install burped or if there was some old component that put some hitch in the gitty-up, but it's good now.

Never in a million years would I have suspected a video driver update could have triggered this situation were it not for this topic. Thanks to "those who came before" for documenting it.

 

[Sky-Knight]

It's always a great reminder. We all need to never forget... The NT kernel has strange interdependance on the video driver. It always has been this way, and it doesn't look like it's going to change anytime soon. So yes, strange and inexplicable problems can be caused by it, and fixed by its replacement.