Same here, Turbodogx. Just a tip: make sure it's unplugged from the wall when you're turning it off. Normal Sleep (as in not Connected Standby, on other machines) will almost always ask for PIN based on the power state in which the PC was when you put it
to sleep, not when you woke it up. In other words:
- plugged-in -> Sleep -> unplug -> wake -> no PIN
- on battery -> Sleep -> plug in -> wake -> asks for PIN/password (even if plugged-in then)
(That is if you have the policy set up differently for each power state like I do.)
Also note that when the device is in Connected Standby, which is now the only available state except for Hibernate and Off, it will
BY DESIGN turn the screen on for about five seconds when you plug in or unplug the power adapter. This is supposedly to show you the charging icon in the taskbar and to eliminate the need for an extra charging diode on the device. Go figure.
Tip: to understand the available power states, type "powercfg /a" into your command prompt.
I suspect our Surface Pro 4 never actually sleeps very well, if at all. You know, this is a
very hard computer science problem. Today, for example, mine never properly slept, it heated up in my bag (even after the update), and then - as I woke it up - I had one "Video Driver Failed & Recovered" error or whatever
it says. The battery was exhausted quickly, seeing as the CPU and fans were working all day in the bag. Thankfully, no blue screens so far. What a great advancement!
Sleep seems very unreliable regardless of the way I switch the machine off. I have a Type Cover too. Starting to think maybe the accelerometer in the Cover (detecting its alignment / relative position with the SP4 body) wakes the device up when it's moved
at all, or something even more sinister perhaps. "Fortunately", Connected Standby greatly reduces the number of devices for which you can disable "Allow this device to wake the computer" in Device Manager to only the cable-attached peripherals.
I disabled Wi-Fi connection for both battery and plugged-in (in Settings->System->Power) so as not to irritate more devices during wake than need to be. I was hoping the update would help more but it seems that it just shuffled the cards on the type of errors
we're dealt every day.
I am still very sad :/