Announcing Windows 10 Insider Preview Build 14942 for PC on Fast ring Insider

sgage said:

I never used any particular trick. Sometimes it can be a bit fiddly to physically get it out - be gentle with the clip that holds it in. Don't want to break that! But I never had any problems. You may have to reset the time, and maybe boot order of your drives in the BIOS.

Thank you very much, SGage. I have now restored my desktop and reset the BIOS as it should be. Of course, when I finally got back up and running, Microsoft asked if I shut my computer down due to a problem, so I wrote them a little story:

Build 14942 Update seemed to install correctly; however, when the system went to sleep, it wouldn't wake up! There was no option except for a hard shutdown, which I did.

At that point, the computer would not boot. I tried booting as per normal with external hard drives attached; I removed them and tried again, to no avail. I tried Win PE and it still wouldn't boot. I tried a bootable flash drive and it wouldn't boot.

A member of TenForums.com told me to unplug the computer, remove the CMOS battery, hold down the power button for 30 seconds (I held it down for one minute) and then try to boot.

I did and it did; I was taken into the BIOS. I reset what needed to be reset, and I'm now back into my computer. Everything seems intact; however, until the computer sleeps again and is successfully awakened and/or shut down and successfully rebooted, I will be paranoid.

I can only say that if I were a Joe Public novice user, I would have had to take the computer to a repair shop! This is not good, Microsoft!

sgage said:

That's a good, succinct write-up - and good that you sent it! And I'm so glad you got going again!

That whole mess was totally uncalled for, especially on the heels of the Cumulative Update fiasco.

BTW, Simrick and I spoke on Skype and discussed your solution. One thing that came out is that Fast Startup is part of the hybrid hibernation function, and may have caused the thing to not wake from sleep. I now have hibernation turned off, which will make Fast Startup gone. Also, it seems that by disabling this, it makes for a longer life of the SSD.

- up and running..

Wynona said:

That whole mess was totally uncalled for, especially on the heels of the Cumulative Update fiasco.

BTW, Simrick and I spoke on Skype and discussed your solution. One thing that came out is that Fast Startup is part of the hybrid hibernation function, and may have caused the thing to not wake from sleep. I now have hibernation turned off, which will make Fast Startup gone. Also, it seems that by disabling this, it makes for a longer life of the SSD.

Sorry, I don't agree with that Wynona. I have Fast Start-Up turned on but Hibernate is off.

Here's a critical bit of information from the 14942 Announcement blog post from Dona Sarkar:

Service hosts are split into separate processes on PCs with 3.5 GB+ of RAM: If your PC has 3.5+ GB of memory, you may notice an increased number of processes in Task Manager. While this change may look concerning at first glance, many will be excited to find out the motivation behind this change. As the number of preinstalled services grew, they began to get grouped into processes known as service hosts (svchost.exe’s) with Windows 2000. Note that the recommended RAM for PC’s for this release was 256 MB, while the minimum RAM was 64MB. Because of the dramatic increase in available memory over the years, the memory-saving advantage of service hosts has diminished. Accordingly, ungrouping services on memory-rich (3.5+ GB of RAM) PCs running Windows now offers us the opportunity to do the following:

1. Increase reliability: When one service in a service host fails, all services in the service host fail. In other words, the service host process is terminated resulting in termination of all running services within that process. Individual service failure actions are then run. As you may have noticed in Task Manager before, service hosts can contain a lot of services:image: https://winblogs.azureedge.net/win/2...services_1.png
   
2. Increase transparency: Task Manager will now give you a better view into what is going on behind the scenes. You can now see how much CPU, Memory, Disk & Network individual services are consuming.
   image: https://winblogs.azureedge.net/win/2...services_2.png
   
   To see the name of the service, click on the left-most arrow such that the Display name drops down. Alternatively, right-click on the header and select ‘Command Line’ to add the Command Line column. Service names will be listed in the format ‘svchost.exe -k <svchost name> -s <service name>.’
3. Reduce servicing costs: Following reports of instability, service engineers, IT admins, and Microsoft engineers can rapidly pinpoint issues to the exact service and fix it.
4. Increase security: Process isolation and individual permission sets for services will increase security.

Note that critical system services (services whose recovery require system restarts), as well as a couple of select service hosts, will remain grouped.

Source: Announcing Windows 10 Insider Preview Build 14942 for PC Windows Experience Blog, 10/7/2016

DooGie said:

Sorry, I don't agree with that Wynona. I have Fast Start-Up turned on but Hibernate is off.

Very strange, Doogie, because here's mine:



What I did was:

Right click on the Start Button and click on Command Prompt (Admin), then type powercfg.exe /hibernate off, press Enter. Type exit, and then press Enter to close the Command Prompt window.

BTW, here's a link to intructions to turn on and off Hibernate:

https://support.microsoft.com/en-us/kb/920730

Wynona, click on Settings That Are Not Currently Available and see what you get :)

DooGie said:

Wynona, click on Settings That Are Not Currently Available and see what you get :)

That's where I got my screenshot, Doogie. :)

Whew! I shut down and rebooted without incident! Yay!