gshaw Posted September 11, 2017 Posted September 11, 2017 Just going back through my Windows 10 deployment settings and noticed on some hardware the NIC wasn't able to catch up in time after a "Fast Startup" boot. In some cases it didn't come up at all, maybe a driver issue, more investigation required for the exact cause. However it's made me question whether that should be turned off for reliability of connections and ensuring Computer GPO etc. is fully refreshed on each boot. The hiberfile also eats up disk space, which is at a premium these days with SSDs and ever increasing Windows Update caches. So I'm looking to set the following registry GPPs: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power\HiberbootEnabled = 0 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\HibernateEnabled = 0 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\HiberFileSizePercent = 2 So basically disable all Hibernation and set the hiberfile size down to a nominal size. Anyone gone the other way and using Fast Startup and Hibernation on their network? On the plus side boot times are lightning fast but wonder if what you gain in speed you lose in management \ reliability?
eddyc Posted September 11, 2017 Posted September 11, 2017 We have it disabled here. As part of our mdt workflow we call powercfg-h off That removes all entry points to hibernate the device. Not noticed any performance issues at all 1
Arthur Posted September 12, 2017 Posted September 12, 2017 We have it disabled here. As part of our mdt workflow we call Same here, but in a SCCM TS. cmd /c powercfg -h off I vaguely remember Fast Startup causing a few issues with some apps we have so I turned it off. Boot times are still quick anyway since all PCs have SSDs. Btw, you might also want to run WinSAT too. 2
gshaw Posted September 12, 2017 Author Posted September 12, 2017 Thanks for the confirmation guys, I used to set powercfg -h off manually in the reference image but left it out by mistake when moving over to MDT as we made a lot of changes in how we build systems now along with piloting Win10. Btw, you might also want to run WinSAT too. Interesting, I used to run this in my old imaging system to get Aero enabled on Win7 but skipped it on Win10 now everything is flat again and doesn't rely on graphics so much. I thought I read somewhere that 10 automatically optimises itself for SSD but maybe all that is old is new again and winsat needs to go back in
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now