Announcing Windows 10 Insider Preview Fast Build 17107 - Feb. 23 Insider

cbwilsha said:

No, I didn't. As soon as it finishes starting up, I'll give that a try. I'll report back ONLY if it works.

I used Windows PowerShell (Admin) and turned Hibernate back on (it didn't work with the command prompt, nor did it work with Run).

Right click the Start Button, then click on Windows PowerShell (Admin) and type Powercfg -h on and Enter. Then check to be sure you really did turn it back on. Go to Settings>System>Additional Power Settings>Choose what the power buttons do. If you see Fast Startup and Hibernation, it's back on. So, now, Change Settings that are currently unavailable. Be sure Fast Startup and Hibernate are both unchecked.

The computer went to sleep and when I came back, it woke up.

My guess is that when fixing the non-boot issue, the Devs broke something else. :)

Looey said:

I executed the Powercfg -h on command and them went to power options and turned fast start up and hibernate off. That cleared up a similar problem that you're having. I had issued the Powercfg -h off command in the previous build as I think you did. It might be worth a try.

Thanks, Looey, that worked. I left feedback on this, with your solution. I didn't name you, since I wasn't sure you'd want me to. Here's what I posted:

Build 17107: My computer wouldn’t wake from sleep. It nudged the hard drive, then gave a blank black screen and nothing else. Last week Build 17101 left my computer in a wouldn’t boot state. The workaround for that was to turn off Fast Startup, which didn’t work for everyone; By using Powercfg -h off, both hibernate and Fast startup were turned off; we could now boot our computers. Fast forward to this week’s update to Build 17107 and my computer would no longer wake from sleep; I would get a blank, black screen only with a little bit of noise form the hard drive. While discussing the issue in TenForums.com, we remembered what we’d done to Hibernate/Fast Startup, and a member came with turning Hibernate back on (Powercfg -h on) and then going in and manually turning off Fast Startup and Hibernate by unchecking their check boxes. Sleep should be checked. Now, my computer wakes from sleep.

Hopefully your discovery will help some others. And, maybe everyone this helps here should go to the Feedback Hub and upvote.

Looey said:

Wynona, you helped me fix my sleep problem in the prior build. I'm glad my discovery helped you. I didn't explain it as well as you did so thanks for doing that.

Oh, well, we help each other when we can. :)

Bottom line here is that Microsoft seems to have messed up Hibernation and Fast Startup ... maybe the whole power settings. No telling what we'll have to contend with in the next Build!

Personally I never hibernate my Desktop or Virtual Machines. I only use sleep when I am away or sleep. If I leave for a trip I shutdown everything. As far as I am concerned M$ fixed the not being able to sleep problem a few build ago and I have not run into a problem, yet, on waking it up. Hibernation takes disk space and I don't have that much with 3 OS's.

How do we actually test this on this build, unless we get any updates which is rare on Insiders?

I assume you would have to set sleep to a very short period eg 10 minutes and wait for next build?

What happens if it fails - would it screw up the upgrade. My PC is set to never sleep, only turn off screen on power.

Keeping PCs Up-to-date: In an effort to prevent PCs from becoming out of date, we are introducing a change in behavior to Windows Update that is designed to be more proactive at keeping PCs updated. In RS4, now when Windows Update scans, downloads, and installs on a PC with AC power – it will prevent the PC from going to sleep when it is not in active use, for up to 2 hours when receiving an update in order to give Windows Update more opportunity to succeed. If you are not seeing this new behavior, let us know by sending in feedback via Feedback Hub.

Fafhrd said:

At last! - a build upgrade that installs first time, straight through from the first download, fairly quickly without stalling, repeating, or failing with Windows Setup as the first bootmenu option, before having to rollback to the last build installed.

It seems like months since fast builds installed faultlessly, first time, for me on 2 machines, an i5 desktop and an AMD E300 APU laptop, each 6 or 7 years old. 17063, 2 months back!

All intermediate builds faltered several times before installing eventually, with both 17101 and 17604 failing totally.

Now both machines on 17107, no oddities to report yet.

I totally agree with this! Finally something that at least installs without hiccups!

cereberus said:

How do we actually test this on this build, unless we get any updates which is rare on Insiders?

I assume you would have to set sleep to a very short period eg 10 minutes and wait for next build?

What happens if it fails - would it screw up the upgrade. My PC is set to never sleep, only turn off screen on power.

Keeping PCs Up-to-date: In an effort to prevent PCs from becoming out of date, we are introducing a change in behavior to Windows Update that is designed to be more proactive at keeping PCs updated. In RS4, now when Windows Update scans, downloads, and installs on a PC with AC power – it will prevent the PC from going to sleep when it is not in active use, for up to 2 hours when receiving an update in order to give Windows Update more opportunity to succeed. If you are not seeing this new behavior, let us know by sending in feedback via Feedback Hub.

I just read that, Cereberus! I haven't done it lately, but historically, when an update was pending, I set sleep to Never so it wouldn't go to sleep while installing. Once installation was finished, I set it back to its normal sleep pattern.