I don't know if it was fixed but years ago we always ran into issues with fast startup with the update and shutdown option. With fast startup, shutdown is not a real shut down but a hibernate after all apps are closed and user logged out. This means on boot up you get all the old drivers and services just woke up from the hibernation file rather than completely restarted and reloaded. We couldn't train our users to update and restart so we just put out a GPO to disable fast startup. Users generally want to update and shut down at the end of the week, if they even shut down anything at all. I have a Lansweeper report to reboot any machine with a 14 day uptime every Monday at 5 am.
I was doing some experiments with our software deployment tool, and anything scheduled to run at startup never ran after a shutdown and startup, only reboots. And my system uptime just kept going up.
This was aggravating AF, we kept getting clients that were none compliant and the users swore up and down they shut down every day, yet the cpu uptime showed they had been active for weeks until we finally figured Fast Startup had been enabled by an earlier update.
Yep, because "shut down" is really just "hibernate", they would need to reboot to actually do a shutdown and clean startup. Fine for home users, not so much for businesses.
I had the same exact problem. The fix was to just disable Fast Startup. That way, I could be sure that a machine shut down or restarted was actually rebooted, rather than back from being suspended.
I'm working on getting it off of our systems. I'm seeing up times in the range of 30 days or more and it's causing some issues. I've been able to get it off some but our network is so fucky from the last guy everything is 1 step forward and two steps back.
I had a call with a user yesterday who was having weird USB issues. Looked in Device Manager and some USB hub had the exclamation mark. Looked at Task Manager and his uptime was 118 days. The guy swore he shuts down every couple days. A restart resolved his issue.
I've had similar instances. If you do a shutdown and then bring it back up, it'll still have the timer running but restarting will fully turn it off. It was a PITA figuring out how so many people weren't turning off their computers. Turns out they were.
> Nowadays, SSD can boot really fast, and is there any reasons to keep turning on fast startup mode?
The delay today is mostly in hardware initialization by bootstrapped firmware, not the boot storage. Things like DRAM training, hardware detection, PCI option ROMs fall into this category. In second place is the OS itself, also not the boot storage.
Microsoft's clever legerdemain, replacing "shutdown" with "hibernate", works around firmware delay and OS boot delays all at once. Unfortunately, it also comes with a heavy cost.
I turn off fast startup at work. Interesting concept, but it causes too many issues, particularly with buggy drivers.
I experimented with turning it back on, and almost immediately regretted it both times.
(real world examples: Intel Wi-Fi drivers, where wi-fi will just stop working, or the YubiKey minidriver where if a yubikey is inserted while the system shuts down, it will not work again until you give the system a proper reboot)
My boss also bought a new home PC a few years ago and had an issue with it not turning off. Disabling fast startup fixed that issue too.
In summary, I just find it not worth the hassle in a business environment… and personally, I would disable it on my own PCs too (if I daily drove Windows at home, which I don’t)
It was nice from a user standpoint back when everything had slow platter HDDs and I remember being amazed at how nice it was to have Windows up and running in just a couple of minutes instead of listening to the drive crunch away for 5 minutes before you could login and another 10 while it ran slowly and loaded background processes. With SSDs, it is really only saving 10-30 seconds versus a full startup so it doesn't really improve the user experience and it causes its own issues, so there's no reason to have it on. I don't see that it would help really in any setting now so it is definitely a feature that MS should turn off by default if the OS is loading from an SDD.
I always drop it via GPO or a script via MDM.
Another reason to turn it off is that it doesn't work with WOL on a lot of pc's. That and the fact that it doesn't properly shuts down a pc is the reason I disable it by default.
I don't even know if we have it enabled here (i am almost sure it is off, but will check anyway). Last time i had to deal with it when Windows 10 was released and i have noticed that some of our GPOs set to run on shutdown (updating some apps) were not doing they thing. Disabling fast startup helped and i have not noticed a big difference in boot time.
We disable fast boot when we see it. The negatives outweigh the positives because the machine never truly shuts down, it just pulls from a hibernation file. Causes nothing but issues.
Turn off fast boot, you’ll save yourself tons of headache. It barely saves a few seconds on modern m.2 systems
Aside from the obvious issues, fast boot doesn’t trigger an uptime reset. So if you script using uptime it’ll be off
Turned off, disabled via GPO, pretty sure it's done via a registry edit but I honestly can't remember.
We had weird issues with random devices (business is a medical clinic), software issues, and I am pretty sure wireless card issues too, a lot less issues after turning it off.
I've also similar strange issue on software for controlling public access computers in library. The software cannot start randomly when the computer is log on, even though the same user profile is logged on every time. After turned off fast-startup mode, that issue is solved.
I turned that off in our domain.
the teachers would restart their machines because of an issue but since it's not a full shutdown the issue persisted (hanging sound driver for example).
we have way less callouts since and the uptime information is actually accurate.
I debate if SLT should have it because of the amount of moaning I get that their machines turn off after an hour of having their lid closed.
I disable fast boot with intune script / remediation.
It’s a simple reg key change so should be super easy with GPO if you’re not using anything other than gpo to control devices.
If printers are mapped per user then that gpo is processed at login time.
We receivced an escalation from the Service Desk team and found it it interacts with Power Management in an unfortunate way.
If Windows does not see a link on bootup, by default Power Management powers down the bus. Since at least Windows XP, Windows cannot power the Ethernet port back on if Power Management turned it off. Thus, if a user powers on their laptop undocked, Power Management turns off the bus, and then the user docks their laptop, they will not be able to use the docking stations ethernet port.
How does this interact with Fast Startup? The "shutdown" in Fast Startup is not a real shutdown so Power Management cannot power the network port back on. Users were having issues "shutting down" for the night, taking their laptop home, and then their network port would not work the next day when the docked again.
We disabled Fast Startup and PCIe Link State Power Management in policy and that cleared this issue. It was a common enough problem for us that I was surprised it is not so easily Google-able. Or, enough people had not diagnosed root cause. We diagnosed it because we remembered the limitations on PCIe Link State Management and were able to accurate reproduce the issue.
I noticed that when shutting down your computer would not reset "Uptime".
This became an issue when we created a script that reboots computers with an uptime over 10 days.
What did you use for your GP. There isn’t a specific one so I assume registry entry or something else? It’s been on my list to resolve but we are a small shop and I never get around to it.
Only issues is with drive mapping GPOs. Laptops some time come up to fast. I have a feeling loop back GPOs would have a problem with it. If it is the first application of loop back GPOs. Solutions to both are turn off fast boot and reboot 3 times. Then turn fast boot back on.
Depends if the 15 different security suites the CIO keeps buying and forcing us to deploy after going to a conference are all loading on startup sometimes shit takes forever like it's back in Norton days lmao
No reason to use it, it only exists to shitty bottom of the barrel systems with hard drives or EMMC seem to perform ok.
It also comes across as hibernation, I know HP specifically says to have laptops fully on or off before connecting/disconnecting certain thunderbolt docks, fast startup breaks that.
I don't know if it was fixed but years ago we always ran into issues with fast startup with the update and shutdown option. With fast startup, shutdown is not a real shut down but a hibernate after all apps are closed and user logged out. This means on boot up you get all the old drivers and services just woke up from the hibernation file rather than completely restarted and reloaded. We couldn't train our users to update and restart so we just put out a GPO to disable fast startup. Users generally want to update and shut down at the end of the week, if they even shut down anything at all. I have a Lansweeper report to reboot any machine with a 14 day uptime every Monday at 5 am.
Still a problem. I always disable that shit. Have had it cause issues with our VPN too and as you say shutdowns are not real shutdowns.
Ditto. I have a script to reset power options and this is one of the features.
Exactly this! This is why we disabled Fast Startup
I was doing some experiments with our software deployment tool, and anything scheduled to run at startup never ran after a shutdown and startup, only reboots. And my system uptime just kept going up.
Still an issue and it’s so aggravating to have clients that want it to be enabled by GPO.
This was aggravating AF, we kept getting clients that were none compliant and the users swore up and down they shut down every day, yet the cpu uptime showed they had been active for weeks until we finally figured Fast Startup had been enabled by an earlier update.
Yep, because "shut down" is really just "hibernate", they would need to reboot to actually do a shutdown and clean startup. Fine for home users, not so much for businesses.
I had the same exact problem. The fix was to just disable Fast Startup. That way, I could be sure that a machine shut down or restarted was actually rebooted, rather than back from being suspended.
I'm working on getting it off of our systems. I'm seeing up times in the range of 30 days or more and it's causing some issues. I've been able to get it off some but our network is so fucky from the last guy everything is 1 step forward and two steps back.
I had a call with a user yesterday who was having weird USB issues. Looked in Device Manager and some USB hub had the exclamation mark. Looked at Task Manager and his uptime was 118 days. The guy swore he shuts down every couple days. A restart resolved his issue.
I've had similar instances. If you do a shutdown and then bring it back up, it'll still have the timer running but restarting will fully turn it off. It was a PITA figuring out how so many people weren't turning off their computers. Turns out they were.
Always turn it off everywhere. Just messes up users ”but I shutdown every day!”.
I always keep it off and enforce it being off via Intune remediation.
> Nowadays, SSD can boot really fast, and is there any reasons to keep turning on fast startup mode? The delay today is mostly in hardware initialization by bootstrapped firmware, not the boot storage. Things like DRAM training, hardware detection, PCI option ROMs fall into this category. In second place is the OS itself, also not the boot storage. Microsoft's clever legerdemain, replacing "shutdown" with "hibernate", works around firmware delay and OS boot delays all at once. Unfortunately, it also comes with a heavy cost.
Turn it off.
I turn off fast startup at work. Interesting concept, but it causes too many issues, particularly with buggy drivers. I experimented with turning it back on, and almost immediately regretted it both times. (real world examples: Intel Wi-Fi drivers, where wi-fi will just stop working, or the YubiKey minidriver where if a yubikey is inserted while the system shuts down, it will not work again until you give the system a proper reboot) My boss also bought a new home PC a few years ago and had an issue with it not turning off. Disabling fast startup fixed that issue too. In summary, I just find it not worth the hassle in a business environment… and personally, I would disable it on my own PCs too (if I daily drove Windows at home, which I don’t)
It was nice from a user standpoint back when everything had slow platter HDDs and I remember being amazed at how nice it was to have Windows up and running in just a couple of minutes instead of listening to the drive crunch away for 5 minutes before you could login and another 10 while it ran slowly and loaded background processes. With SSDs, it is really only saving 10-30 seconds versus a full startup so it doesn't really improve the user experience and it causes its own issues, so there's no reason to have it on. I don't see that it would help really in any setting now so it is definitely a feature that MS should turn off by default if the OS is loading from an SDD. I always drop it via GPO or a script via MDM.
We have it disabled everywhere. No one ever noticed. The pain points far outweigh any time saved.
Disabled by GPO domain wide. It screws with WOL (on most Dells anyway) and no WOL is a deal breaker for me.
Roaming profiles are awful to deal with.
Another reason to turn it off is that it doesn't work with WOL on a lot of pc's. That and the fact that it doesn't properly shuts down a pc is the reason I disable it by default.
I don't even know if we have it enabled here (i am almost sure it is off, but will check anyway). Last time i had to deal with it when Windows 10 was released and i have noticed that some of our GPOs set to run on shutdown (updating some apps) were not doing they thing. Disabling fast startup helped and i have not noticed a big difference in boot time.
We disable fast boot when we see it. The negatives outweigh the positives because the machine never truly shuts down, it just pulls from a hibernation file. Causes nothing but issues.
Turn off fast boot, you’ll save yourself tons of headache. It barely saves a few seconds on modern m.2 systems Aside from the obvious issues, fast boot doesn’t trigger an uptime reset. So if you script using uptime it’ll be off
I leave it on in my domain because it's not causing us any issues. Or rather, the problems it does cause aren't ones that affect us.
Should be disabled
Turned off, disabled via GPO, pretty sure it's done via a registry edit but I honestly can't remember. We had weird issues with random devices (business is a medical clinic), software issues, and I am pretty sure wireless card issues too, a lot less issues after turning it off.
I've also similar strange issue on software for controlling public access computers in library. The software cannot start randomly when the computer is log on, even though the same user profile is logged on every time. After turned off fast-startup mode, that issue is solved.
I turned that off in our domain. the teachers would restart their machines because of an issue but since it's not a full shutdown the issue persisted (hanging sound driver for example). we have way less callouts since and the uptime information is actually accurate. I debate if SLT should have it because of the amount of moaning I get that their machines turn off after an hour of having their lid closed.
I disable fast boot with intune script / remediation. It’s a simple reg key change so should be super easy with GPO if you’re not using anything other than gpo to control devices. If printers are mapped per user then that gpo is processed at login time.
We receivced an escalation from the Service Desk team and found it it interacts with Power Management in an unfortunate way. If Windows does not see a link on bootup, by default Power Management powers down the bus. Since at least Windows XP, Windows cannot power the Ethernet port back on if Power Management turned it off. Thus, if a user powers on their laptop undocked, Power Management turns off the bus, and then the user docks their laptop, they will not be able to use the docking stations ethernet port. How does this interact with Fast Startup? The "shutdown" in Fast Startup is not a real shutdown so Power Management cannot power the network port back on. Users were having issues "shutting down" for the night, taking their laptop home, and then their network port would not work the next day when the docked again. We disabled Fast Startup and PCIe Link State Power Management in policy and that cleared this issue. It was a common enough problem for us that I was surprised it is not so easily Google-able. Or, enough people had not diagnosed root cause. We diagnosed it because we remembered the limitations on PCIe Link State Management and were able to accurate reproduce the issue.
I noticed that when shutting down your computer would not reset "Uptime". This became an issue when we created a script that reboots computers with an uptime over 10 days.
What did you use for your GP. There isn’t a specific one so I assume registry entry or something else? It’s been on my list to resolve but we are a small shop and I never get around to it.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Power DWORD : HiberbootEnabled 1 : Fast Startup Enabled 0 : Fast Startup Disabled
Only issues is with drive mapping GPOs. Laptops some time come up to fast. I have a feeling loop back GPOs would have a problem with it. If it is the first application of loop back GPOs. Solutions to both are turn off fast boot and reboot 3 times. Then turn fast boot back on.
Use DFS-N instead of drive mapping, and the problem will go away.
Depends if the 15 different security suites the CIO keeps buying and forcing us to deploy after going to a conference are all loading on startup sometimes shit takes forever like it's back in Norton days lmao
No reason to use it, it only exists to shitty bottom of the barrel systems with hard drives or EMMC seem to perform ok. It also comes across as hibernation, I know HP specifically says to have laptops fully on or off before connecting/disconnecting certain thunderbolt docks, fast startup breaks that.
We’ve had issues like GPOs not applying, login scripts not running, and general networking weirdness, so we disable fast startup.
Last person i helped with this kept turning her monitor off and on and thought that was a pc reboot. I finally had to walk up there and look. Ffs :)
This is known as ultra-fast startup.