What is Windows 10 fast startup

Fast Startup in Windows 10 is supposed to help boot Windows up much faster. In a complete shutdown scenario, Windows logs off all users and closes all applications. Fast start up is similar to a complete shutdown but with a mix of hibernation. In Fast Startup Windows logs off all users and shuts down all applications at this point Windows is at a stage similar to first boot but Windows then hibernates the windows kernel and loaded drivers to “help” reduce the startup time.

 

Why you should consider disabling it

In our environment we have found that on machines with many profiles Fast Startup actually slows things down and can use a lot of disk space. Most of our teaching machines have SSD’s and space is limited. Its worth pointing out that this can also cause problems with

  • Windows Updates – many updates need a restart and if you have shutdown the machines rather than restarted it can cause them to fail to install.
  • Dual boot systems – On shutdown it locks the hard disk, so only a reboot works.
  • Encrypted drives – I have found on laptops that are installing updates that need a restart this has caused Bitlocker to ask for the recovery key.

Automating the management with SCCM CB

It looks like Windows 10 Fast Startup mode seems to help some machines and disabling it across the enterprise seems over kill, from what my colleagues have said and my own experience staff machines with limited number of users (and large hard disks) seem to benefit from this. I am sure if you are a fan of the site you may have realized by now that Maurice Daly and I are big fans of Configuration Items and Configuration baselines.

Configuration Item

  1. Open the SCCM Console and expand the Compliance Settings section
  2. Right click on the Configuration Item and select Create Configuration Item
  3. Give your CI a name, always good to follow a naming pattern.
  4. Select Windows 10 only.
  5. This a registry setting so we can actually browse to the setting we want to change(clearly do this on a Windows 10 machine)
  6. Browse to HKLM\SYSTEM\CurrentContorlSet\Control\Session Manager\Power and look for “HiberBootEnabled
    • It will currently be set to 1 (enabled) this is turned on by default on Windows 10
    • Tick “This registry value must satisfy the following rule if present”
    • We want to enforce the value of 0 on it (disabled)
  7. So thats the setting and compliance rules set, time to review.
  8. Under “HiberbootEnabled Equals 0” make sure you tick “Remediate noncompliant rules when supported”.
  9. Under Compliance Rules make sure remediate is ticked.

Configuration Baseline

With the Configuration Item created the next step is to create a Configuration Baseline and deploy it to your collection. My collections contains all Windows 10 teaching machines.

  1. Right click on Configuration Baseline and click Create Configuration Baseline.
  2. Give the baseline a name.
  3. The final step is to deploy the Configuration Baseline to the Collection, so right click on the Configuration Baseline and Deploy. Ensure that “Remediate noncompliant rules when supported” is ticked.

Monitoring

Under the monitoring node I can see compliant machines.

 

I am originally from Dublin – Ireland but moved to London in 2000 to study for a Computer Science degree. I currently work for London Metropolitan University, It’s a challenging but also a creative environment.

I specialise in system center configuration manager and application packaging, I’m working on increasing my online presence though my website and twitter account so please feel to drop me a line.

(3394)

comments
  • James
    Posted at 14:18 March 31, 2017
    James
    Reply
    Author

    Step 6 Should be HKLM\System\CurrentControlSet\CONTROL\SessionManager\Power (you have it missing the CONTROL Entry)…Great Post, thanks for posting, this came in handy.

    • Terence Beggs
      Posted at 14:26 March 31, 2017
      Terence Beggs
      Reply
      Author

      Yes thanks for that, i had to do this in a rush today. I have updated the post, always nice to get feedback either way.

  • Sergey Korotkov
    Posted at 13:40 April 1, 2017
    Sergey Korotkov
    Reply
    Author

    Also use it on Win 8 / 8.1.
    Thanks

  • seb
    Posted at 16:31 April 4, 2017
    seb
    Reply
    Author

    I also found on one computer with fastboot that it won’t shut down at all (black screen then back to login screen)
    Any way, great post thanks!
    Do you still have to manage or lock the shutdown settings by GPO or defining a configuration baseline is enough for the user not to change it?

    • Terence Beggs
      Posted at 16:39 April 4, 2017
      Terence Beggs
      Reply
      Author

      That setting requires admin privileges so not an issue for my env. You could enforce using a GPO but the compliance baseline will just keep writing over it, if and only if it changes.
      A colleague of mine describes GPO’s like using a hammer, and a CB is like using a scalpel 🙂

  • Martin
    Posted at 23:21 April 5, 2017
    Martin
    Reply
    Author

    Great guide! Another thing that could be mentioned is that Wake on LAN also won’t work if fast startup is enabled.

    Source: https://support.microsoft.com/en-us/help/2776718/-wake-on-lan-wol-behavior-in-windows-8,-windows-8.1-and-windows-10

  • Leave a Reply to Terence Beggs
    Cancel Reply