[1909, ou] Windows 10 and WOL

[garethEds]

Evening All,

For a while I've been trying to get Windows 10 and WOL to work across the Curriculum network but am having no luck. Any help appreciated.

We purchased a piece of softwrae called EMCO Remote Shutdown - it's great. Shuts the machines down brilliantly on a schedule.

It also tries to wake them up on a schedule - except it doesn't work.

Through reading I've read that Windows 10 doesn't shut down fully when sent the shutdown command. There are two types of shutdown:

1. Emco shuts the machine down - a soft shutdown. WOL doesn't work.
   
2. I power off the machine with a 5 second power button press. A hard shutdown - EMCO Wol works immediately.
   

The company don't seem to have any idea beyond the way we broadbast WOL packets. The software tries several methods - none work.

So - there must be a way to force Windows to perform a 'hard shutdown' with the shutdown command.

I'm happy to ditch the software if we can get something else to work - but for now am stumped.

Any help appreciated.

Gareth

[ass17]

Evening All,

For a while I've been trying to get Windows 10 and WOL to work across the Curriculum network but am having no luck. Any help appreciated.

We purchased a piece of softwrae called EMCO Remote Shutdown - it's great. Shuts the machines down brilliantly on a schedule.

It also tries to wake them up on a schedule - except it doesn't work.

Through reading I've read that Windows 10 doesn't shut down fully when sent the shutdown command. There are two types of shutdown:

1. Emco shuts the machine down - a soft shutdown. WOL doesn't work.
   
2. I power off the machine with a 5 second power button press. A hard shutdown - EMCO Wol works immediately.
   

The company don't seem to have any idea beyond the way we broadbast WOL packets. The software tries several methods - none work.

So - there must be a way to force Windows to perform a 'hard shutdown' with the shutdown command.

I'm happy to ditch the software if we can get something else to work - but for now am stumped.

Any help appreciated.

Gareth

 

We had exactly the same issue. It seemed as if it was a Ethernet driver issue but low and behold for us I managed to track it down to the fact that the hard disks needed to be converted from MBR to GPT partitions.

 

Nothing to do with WOL, I know!!

 

If you are still experiencing issues with WOL then let me know as I have created a doc that goes through specific settings to change.

[round2it]

We had exactly the same issue. It seemed as if it was a Ethernet driver issue but low and behold for us I managed to track it down to the fact that the hard disks needed to be converted from MBR to GPT partitions.

 

Nothing to do with WOL, I know!!

 

If you are still experiencing issues with WOL then let me know as I have created a doc that goes through specific settings to change.

 

we are rolling out windows 10 this summer (Late i know) could i get a copy of the document

[ass17]

we are rolling out windows 10 this summer (Late i know) could i get a copy of the document

 

Of course, PM me your email and I will drop it over to you later today :-)

[mavhc]

Same problem on every model of computer?

[Steve21]

So - there must be a way to force Windows to perform a 'hard shutdown' with the shutdown command.

 

 

Try changing the registry setting of a computer to 0 using:

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled

 

We found it was more linked to having fast startup enabled, which effectively doesn't shut down the machine properly. However, for our purposes of WOLing machines in the morning we found it's better to disable the fast startup and have wol work

 

You should be able to test it on one, just add the above reg key, reboot, shutdown "normally" (not hard), and try the wol

 

Steve

[mavhc]

S4 vs S5 https://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface#Power_states

[DJ-1701]

Interesting... as you remember...

 

Unfortunately, WOL from a full shutdown is not something that Microsoft support now...

 

http://www.edugeek.net/forums/impero-direct-support/195250-w10-spring-creators-update.html#post1669561

 

But if the behaviour of the shutdown from Windows itself has change from previous versions as it may have from your forced powered off test, and if there is a way to get Windows to perform a similar safe shutdown, that would be brilliant...

[mavhc]

Weirdly this is the opposite of Impero's message. S5 works but S4 doesn't for this thread.

[ass17]

Here is the doc For all things WOL as promised

 

 

https://docs.google.com/document/d/1PklUcYDj6SGDY6DZVq57BV3SR_4NC2yx5h-fjb1Vq5Q/edit

 

If your fix is not on my doc please let me know so I can add to it :-)

Edited July 17, 2020 by ass17

[mavhc]

https://en.wikipedia.org/wiki/Wake-on-LAN#Microsoft_Windows

[ass17]

Wiki is wrong, the S5 state does still work and it’s what state we use in Windows 10 1703 up to 1909.

 

Interestingly enough some drive have started to disable S5 wol state in the INF driver file.

[mavhc]

All my desktops just sleep, and my laptops don't WOL, so never noticed.

 

'In Windows 8, 8.1 and Windows 10, the default shutdown behavior puts the system into the hybrid shutdown (also known as Fast Startup) state (S4), and all devices are put into D3. In this scenario, WOL from S4 or S5 is unsupported. Network adapters are explicitly not armed for WOL in these cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of invalid wake-ups when an explicit shutdown is requested. Therefore, WOL is supported only from sleep (S3), or when the user explicitly requests to enter hibernate (S4) state in Windows 8, 8.1 and Windows 10. Although the target system power state is the same between hybrid shutdown and hibernate (S4), Windows will only explicitly disable WOL when it's a hybrid shutdown transition, and not during a hibernate transition.'

[ass17]

All my desktops just sleep, and my laptops don't WOL, so never noticed.

 

'In Windows 8, 8.1 and Windows 10, the default shutdown behavior puts the system into the hybrid shutdown (also known as Fast Startup) state (S4), and all devices are put into D3. In this scenario, WOL from S4 or S5 is unsupported. Network adapters are explicitly not armed for WOL in these cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of invalid wake-ups when an explicit shutdown is requested. Therefore, WOL is supported only from sleep (S3), or when the user explicitly requests to enter hibernate (S4) state in Windows 8, 8.1 and Windows 10. Although the target system power state is the same between hybrid shutdown and hibernate (S4), Windows will only explicitly disable WOL when it's a hybrid shutdown transition, and not during a hibernate transition.'

 

We still use S5 state because we know the system is off completely, maximum power saving (other than switching off at the plug!) and it’s always worked for us 100% for the last 10 years.

[mavhc]

Depends how much power it takes to shutdown and boot up of course, and how often it does that vs how long it's off for

[ass17]

Depends how much power it takes to shutdown and boot up of course, and how often it does that vs how long it's off for

 

Of course, it’s always perceived that an S5 state was the least power hungry state whilst allowing a computer to turn on by WOL, but to be honest I bet now it is negligible across the S states in terms of £ per PC per year costs and savings.

 

I dare say not one techie has actually ever measured it and just gone off the theory and potential costs/savings.