Windows 10 (1607) - Shutdown does not mean Shutdown (and other related issues)

LC2

LC2

Negan
Suspended / Banned
Messages
11,169
Name
Tim
Edit My Images
Yes
Windows 10 (1607) - Shutdown does not mean Shutdown (and other related issues)

Just a heads up for those of you on Windows 10 aniversary edition.

I noticed this 'feature' on my cheap linx1010b tablet.
Symptoms were:
I was difficult to turn on
Remaining Battery was dropping if not plugged into the charger, even though it was 'shutdown'.

I thought it was dying (it was only cheap), but before putting my hand in my pocket, I thought I'd have a nose around various tech forums.

It seems that MS changed the meaning of Shutdown in 1607 to actually mean hybrid shutdown (or in other words, sleep).
So when you think you're turning it off, you aren't.
I fixed this by disabling this feature in power management and lo, battery life was restored and the power button started working properly again :)

To do this, you need to access
  • Control Panel - Power Options - System Settings ("Choose what the power buttons do" option)
  • Deselect "Turn on fast startup".

It seems in recent weeks, MS have also introduced a dhcp issue as part of one of their patches.
https://community.spiceworks.com/topic/1947168-dhcp-not-working-on-windows-10
http://www.theregister.co.uk/2016/12/12/ongoing_windows_8_10_dhcp_problems_affecting_all_isps/
https://support.microsoft.com/en-gb/help/10741/windows-10-fix-network-connection-issues
Note how the MS fix tells you to restart, and not shutdown / power on.
This is because turning it off and on again no longer turns it off and on again!!!!!

By the way, if you experience the DHCP issue, the following steps are suggested (not my work - copied from a PistonHeads post).

In the search box on the taskbar, type Command prompt, press and hold (or right-click) Command prompt, and then select Run as administrator > Yes.
At the command prompt, run the following commands in the listed order, and then check to see if that fixes your connection problem:
Type netsh winsock reset and press Enter.
Type netsh int ip reset and press Enter.
Type ipconfig /release and press Enter.
Type ipconfig /renew and press Enter.
Type ipconfig /flushdns and press Enter.

I hope this helps anyone having DHCP issues, power issues, or other weird behaviour that doesn't seem to be fixed by the old adage of turning it off anf on again...
 
the hybrid shutdown has been in since the launch of 10 if i remember rightly?

as far as i know the dhcp bug only effects vm in the uk. and vm workaround was renewing the ip and flushing the dns.
 
neil_g said:
the hybrid shutdown has been in since the launch of 10 if i remember rightly?

as far as i know the dhcp bug only effects vm in the uk. and vm workaround was renewing the ip and flushing the dns.
Click to expand...

Not sure on Hybrid shutdown, but they certainly changed something in the way it functions at 1607. The linx1010b was fine before the upgrade (though to be fair, I didn't notice the issue immediately after 1607, so it could have been 1607+some other patch). Regardless, it does seem that for currently patched Windows 10 machines, turning it off and on again doesn't actually turn it off and on again.

The links I've pasted in the original thread indicate this isn't just a Virgin Media problem - The spiceworks thread indicates it's happening on a company lan.
Further reading identifies that MS have patched the DHCP issue in KB3206632
http://www.infoworld.com/article/31...2-solves-dropped-internet-connection-bug.html
Obviously if you are impacted, you need to get back onto the web, so a restart to power cycle (not shutdown) is still needed.

I get the idea behind Fast Boot, but hiding the fact that shutdown now leaves the machine in a sleep mode is daft.
 
Last edited:
hmm not seen any issues on a non-router based dhcp server (i.e. provided by windows server).

looks like they fixed it in update -
December 13, 2016—KB3206632 (OS Build 14393.576)
"Addressed a service crash in CDPSVC that in some situations could lead to the machine not being able to acquire an IP address."
 
neil_g said:
hmm not seen any issues on a non-router based dhcp server (i.e. provided by windows server).

looks like they fixed it in update -
December 13, 2016—KB3206632 (OS Build 14393.576)
"Addressed a service crash in CDPSVC that in some situations could lead to the machine not being able to acquire an IP address."
Click to expand...
Yup, as noted in the post above.

neil_g said:
fast boot definitely been in since release candidate btw. (edit - it was a feature that started life in W8)

also it's not a "sleep" if anything its a hibernate (it does use the hib file)

MS blurb - https://blogs.msdn.microsoft.com/b8/2011/09/08/delivering-fast-boot-times-in-windows-8/
Click to expand...
Odd then that it caused battery usage when shutdown on my linx tablet, as my understanding is that hibernation write to a file, rather than saving into RAM, so shouldn't use power.
I have to say, I've not seen the same behaviour on our 2 other Windows10 machines.

I guess I knew that MS had done something to the boot since Win8 (though not needed to investigate), but regarless of how it's spun, Shutdown is no longer a shutdown unless you either amend the configuration, or execute "shutdown /full".

In essense, this is a fudge to make it appear to the general populous that Windows is booting faster. It's not, it's 'restoring' rather than 'booting' behind the scenes.
Why they couldn't have left the options as Shutdown / Hibernate / Sleep, which was clear what it was doing, is beyond me.

By the way, I'm not knocking Windows, since Windows 2000 it's generally been pretty good, and certainly more transparent about vulnerability patching than a certain other vendor.
 
Thanks for this. I've just spent all day struggling with a friend's Win 10 machine that couldn't sort its internet connection any more. I managed to cure it but from what you have posted I did accidentally when I discovered the full shut down when trying to get the machine to boot off a Linux DVD!
 
Aha! Light dawns! Have just acquired my first Windows 10 computer, and have been struggling to understand why the settings which should have turned it off hibernated it instead!
 
chris malcolm said:
Aha! Light dawns! Have just acquired my first Windows 10 computer, and have been struggling to understand why the settings which should have turned it off hibernated it instead!
Click to expand...
not sure we're talking about the same thing to be fair.

for all intense purposes the fast boot looks like a normal shutdown, just that the kernel is being paused into a temp file.
 
neil_g said:
horses for courses. i've never seen fast boot cause an issue in all honesty.
Click to expand...
But it just has, all over the world by all accounts but maybe you have not been affected! Perhaps you haven't rebooted your machine since the suspect update was released last week? I suspect MS have updated their update by now.
 
sphexx said:
But it just has, all over the world by all accounts but maybe you have not been affected! Perhaps you haven't rebooted your machine since the suspect update was released last week? I suspect MS have updated their update by now.
Click to expand...
i dont think the dhcp bug was caused by this fast boot option, unless ive missed something?
 
neil_g said:
i dont think the dhcp bug was caused by this fast boot option, unless ive missed something?
Click to expand...
My understanding (no expert) is that the fast boot prevents Windows from "curing" whatever the problem was -- that seems to fit my experience with it since it cured itself when I disabled the fast boot -- though, as I wrote above, I did that because I was trying to get into BIOS to get it to boot from a Linux DVD.
 
sphexx said:
My understanding (no expert) is that the fast boot prevents Windows from "curing" whatever the problem was -- that seems to fit my experience with it since it cured itself when I disabled the fast boot -- though, as I wrote above, I did that because I was trying to get into BIOS to get it to boot from a Linux DVD.
Click to expand...
dont think so? there isnt really any details posted other than the dhcp issue was caused by one of the device services failing. a restart would have done a cold boot and people say that didnt help dhcp.

but ill happily be proved wrong.
 
Thanks for the tip! I have the same cheap Linx tablet (bought it to see if I liked Win10 before "upgrading" laptops and desktops) and thought the battery life was a bit poor (to say the least!)
 
All bet it I've still got my fingers crossed....

I've been blighted by this problem, and going through the various things that said would resolve it didn't....

After a reboot I could access the internet but it didn't last long, found pages started to slow on loading, then wouldn't load and I would have to reboot.

So I took a look at my 'power options' where yep my lappy was default set to go into sleep mode when shut down button was pressed, and the fast start up was tick (recommended) So I've changed the setting to Shut down, when Shut down button is pressed, and no to fast start up...

Funny enough my lappy is loading a lot quicker at start up, and so far so good, I haven't lost the internet
 
@Ellie Jones
Microsoft released a patch for the internet issue
https://support.microsoft.com/en-us/help/4004227/windows-10-update-kb3206632
on the 13th.
Changing the behaviour of 'shutdown' won't have fixed the issue, it would have mitigated it temporarily (a restart should have had the same effect too).
So I wouldn't say that changing shutdown behaviour will have been the fix to your internet issue.
Startup shouldn't be faster either - so if it is, then you've had something odd going on.
 
I have something 'odd' going on :(

I've got that patch, but didn't go on until the 17th, and no other updates since march!

The problem has reappeared...

I use AVG antivirus, so I've now turned off the firewall for this to see what happens.... As doing some research there seems to be issues with the firewall causing a similar problems so will leave firewall off for a little while see what happens.

So perhaps it's time to change my antivirus
 
Since I don't use Win 10 frequently I didn't realise that "restart" is "stronger" than "shutdown", to me the words seem to imply the opposite. Anyway, it seems that restart is more likely to solve the dhcp problem but many people find it may take multiple restarts before the problem is solved.
It seems that the fault is very variable between different machines (manufacturers?) and also some people never suffered the fault because they didn't apply the faulty update before the curative update was issued and so on.
 
Fwiw I don't think ellies problem is relate to this bug. The Internet gradually slowing to a point where it no longer works is not really symptomatic of a dhcp issue.

Sounds like a bit of an odd one.
 
neil_g said:
Fwiw I don't think ellies problem is relate to this bug. The Internet gradually slowing to a point where it no longer works is not really symptomatic of a dhcp issue.

Sounds like a bit of an odd one.
Click to expand...
Yes, I was really posting generally but I suppose partly to your quote of me, above ;-)
 
You must log in or register to reply here.
Back
Top