Why a shutdown in Windows 8 / 10 is not a restart.


Recommended Posts

 

Ever since the dawn of the personal computer when a computer would act funny or miss-behave people would just turn the computer off (Sometimes for minutes or hours, when in fact the amount of time you leave it off makes no difference unless the issue is heat related) and turn it back on.

Starting with Windows 8, Microsoft wanted to make “Windows” Boot faster when you press the power button to turn it on (The time between pressing the power button and arriving at the desktop). To accomplish this they created “Fast startup”.

Fast startup is a shutdown + Hibernation Hybrid. First, let’s talk about what hibernation is and how it works.

Hibernation allows you to turn the computer completely off (even unplug it if you wish) and when you turn it back on, you are right back where you left off including all the applications you had open.

How does all this voodoo work? For hibernation to work, windows looks at how much Ram (memory) you have in your computer.

It then creates a file on your hard drive called HIBERFIL.SYS. Back in the days of Windows 2000 and Windows ME, this file was the exact same size as the amount of ram your computer has so if you had 2GB of ram you would of had a 2GB hiberfil.sys file. In Windows 7 they set the file size to 75% and in Windows 8 the file size is smaller yet, due to not hibernating user data during shutdown.

When you tell your computer to hibernate, it takes the contents of your ram and dumps it into the HIBERFIL.SYS file. Then the computer shuts off.

When you turn the computer back on, the reverse happens. It takes the contents of HIBERFIL.SYS and puts it back into ram and your computer is now booted. One reason this is faster is that typical spinning hard drives are much faster at large single files than thousands of small files.

Now that you know how hibernation works, let’s take a look at how fast startup works. The fast startup works by not hibernating the entire system but just the core functions, such as the kernel (the lowest level of the system), system drivers (software that tells your devices how to operate), and a few others.
.
When you turn your computer off in Windows 8 and Windows 10, it first closes all your applications, then it logs off and dumps the system files listed above into the HIBERFIL.SYS file and your machine shuts off.

When you turn the machine back on, it will start faster because half of the boot process is transferred directly back into ram, in the exact state it was in before the shutdown, problems and all.

This is also why when you select restart instead of shut down it feels like your system takes longer to startup. When you select restart nothing is hibernated and the system has to start everything from scratch.

Hopefully, you can see now why turning your computer off and back on in Windows 8 and Windows 10 is pretty worthless for solving any sort of problems and why it’s much better to select restart.

The issue I have with Fast Startup is that they told the average user NONE of this. How is the average person supposed to know that turning the computer off and back on won't solve their problem? After all, the process looks the same and it worked just fine in Windows 3.1, Windows 95, 98,ME, XP, Vista and Windows 7.

One customer was running Windows 8 and was having problems accessing their email. They were trying to open their email program but nothing was happening. I asked them if they restarted their computer and they told me yes, they turned the computer off 3 times and it still won't work. So I walked them through selecting "Restart" instead of "Shutdown" and after the "restart," their email opened up first try.

  • Like 4

Hello,

 

I have upgraded all of my computers to SSDs for at least their boot drives over the years, and find that booting from a powered down state to the logon screen to be fast enough that I disable the hibernation and suspend features of the operating system. 

 

One small bonus to this is that I gain the space back previously used by the HIBERFIL.SYS file on the boot drive (which can be considerable on workstations with 64-96GB of RAM), but the major reason I do this is to avoid incompatibilities with the computer's device drivers that sometimes do not handle the transitions between the different power/suspend states very well.

 

Regards,

 

Aryeh Goretsky

 

  • Like 2

Huh not something that I knew :)

 

Personally, being the family "IT guy", if someone has an issue, I always suggest a restart.  More than likely, the issue that they're having is something they want to try again ad see if it's been resolved so I haven't come across that "feature". 

 

Personally, given how little power is used during hibernation, most of the machines that I use frequently aren't ever shut down, they're either restarted or hibernated. 

 

MS should remove the other options from the power menu and keep just restart or hibernate. 

  On 06/09/2018 at 12:23, dipsylalapo said:

Huh not something that I knew :)

 

Personally, being the family "IT guy", if someone has an issue, I always suggest a restart.  More than likely, the issue that they're having is something they want to try again ad see if it's been resolved so I haven't come across that "feature". 

 

Personally, given how little power is used during hibernation, most of the machines that I use frequently aren't ever shut down, they're either restarted or hibernated. 

 

MS should remove the other options from the power menu and keep just restart or hibernate. 

Expand  

What about cases where you'd want a full shutdown (storm, machine move, hardware maint.)?

  On 04/09/2018 at 17:48, warwagon said:

It then creates a file on your hard drive called HIBERFIL.SYS. This file is the exact same size as the amount of ram your computer has.

Expand  

this is wrong.

on all my systems, where I leave hibernation enabled, the hiberfil.sys file is always much smaller than the amout of RAM in the system.

 

 -andy-

  On 06/09/2018 at 12:26, Squirrelington said:

What about cases where you'd want a full shutdown (storm, machine move, hardware maint.)?

Expand  

Fair points! I stand corrected!

  • Like 1
  On 06/09/2018 at 12:26, Squirrelington said:

What about cases where you'd want a full shutdown (storm, machine move, hardware maint.)?

Expand  

Hibernation is a full shut down. Sleep would not be, but Hibernation is. With Hibernation the computer is OFF!

  On 06/09/2018 at 12:27, AndyMutz said:

this is wrong.

on all my systems, where I leave hibernation enabled, the hiberfil.sys file is always much smaller than the amout of RAM in the system.

 

 -andy-

Expand  

I'll edit it. The size probably changes as to how much ram you are are using. After looking it up it appears that in windows 2000 the file was the entire size, but I guess it expands and contracts with other versions of windows.

  • Like 2
  On 06/09/2018 at 12:37, warwagon said:

Hibernation is a full shut down. Sleep would not be, but Hibernation is. With Hibernation the computer is OFF!

Expand  

So you could in theory disconnect from the power and move the machine etc. 

 

How would a machine deal with a hardware upgrade in hibernation?

  On 06/09/2018 at 12:39, dipsylalapo said:

So you could in theory disconnect from the power and move the machine etc. 

 

How would a machine deal with a hardware upgrade in hibernation?

Expand  

Yes, you can disconnect the power and move the computer. I'm curious, did you read the part where I explained how hibernation worked? lol

Always hated hibernation as most every machine I've ever owned, or worked on, had issues when resuming. One of the first things I always used to do was disable that crap! I'll either use sleep or turn the computer off when done. Have never left computers on, even over night! I'm on a different one or 2 every day anyway.

  On 06/09/2018 at 12:41, warwagon said:

Yes, you can disconnect the power and move the computer. I'm curious, did you read the part where I explained how hibernation worked? lol

Expand  

Just re-iterating what you said :rofl: 

 

What about hardware upgrades?

  On 06/09/2018 at 12:55, dipsylalapo said:

Just re-iterating what you said :rofl: 

 

What about hardware upgrades?

Expand  

My guess would be yes. Because most people wouldn't know they are in a hybrid state and would always turn the computer off to upgrade their hardware.

 

That being said, if you want to clone a Windows 8 or 10 hard drive with true image, it will bomb out almost instantly if you just turn the computer off, pull the drive in and clone on another machine. If you are pulling the drive, either turn hibernation off, or restart and when the computer starts to come back on turn it off and then pull the drive.

Was doing remote support with someone who was having issues with their usb printer printing. It would print but it would take a few mins. Looked at the system boot time and it was 8/16/2018. I asked him when the last time he restarted it was (which obviously was 8/16/2018) he said "I just turned it on today" So I had to explain to him the difference between a shutdown and restart.

  On 06/09/2018 at 12:26, Squirrelington said:

What about cases where you'd want a full shutdown (storm, machine move, hardware maint.)?

Expand  

Win 10 - I had a game where it crashed and the sound was "stuck". Powered down, powered back up, stuck sound came back.
It wasn't until I did a "restart" no longer hearing the stuck sound.

Hello,

 

On Windows 10 (and perhaps earlier), you can adjust the size of the hibernation file so it is a percentage of RAM (as low as 40%).  For more information open an elevated Command Prompt (filename: CMD.EXE) and type in "POWERCFG /HIBERNATE ?" (without the quotes) and press Enter to see all of the options and their associated values.

 

Regards,

 

Aryeh Goretsky

 

 

  On 06/09/2018 at 12:27, AndyMutz said:

this is wrong.

on all my systems, where I leave hibernation enabled, the hiberfil.sys file is always much smaller than the amout of RAM in the system.

 

 -andy-

Expand  

 

  • +Warwagon unlocked this topic

When first connecting to someone's computer for "Any" issue, I first open CMD and run  systeminfo to look at the "System boot time". If "Fast startup" is enabled the date will not change each time the computer is turned on and off, only when the computer is restarted.

 

Here is an example. My basement workstation has fast startup enabled and I JUST booted it up today 1/24/2022 at 3:30pm. Lets look at the system boot time. Even though I just turned it on, the machine hasn't actually been restarted since 1/18/2022.

 

image.png.fd9dbcdc9ce8875f0247c6d7f8aa3fd5.png

 

There have been times when the "System boot time" has been MONTHS ago!

I always initiate from an elevated command prompt powercfg -h off enter, reboot.  

 

The hiberfil.sys is notorious for corruption.

  • Like 3
  On 24/01/2022 at 21:40, xrobwx71 said:

I always initiate from an elevated command prompt powercfg -h off enter, reboot.  

 

The hiberfil.sys is notorious for corruption.

Expand  

This! I do that too on "Most" of my machines.

  On 24/01/2022 at 21:34, warwagon said:

When first connecting to someone's computer for "Any" issue, I first open CMD and run  systeminfo to look at the "System boot time". If "Fast startup" is enabled the date will not change each time the computer is turned on and off, only when the computer is restarted.

 

Here is an example. My basement workstation has fast startup enabled and I JUST booted it up today 1/24/2022 at 3:30pm. Lets look at the system boot time. Even though I just turned it on, the machine hasn't actually been restarted since 1/18/2022.

 

image.png.fd9dbcdc9ce8875f0247c6d7f8aa3fd5.png

 

There have been times when the "System boot time" has been MONTHS ago!

Expand  

Same. I find this commonly has caused issues for people with laptops who take it back/forth to the office, especially when group policy is involved, drive mappings, and the sort.

 

This is also why I don't even ask if people have restarted their computer anymore, mostly because they'll say yes when they've simply shut it down, assuming that restart and shutdown still mean the same thing. Anyway, disabling Fast Boot often times resolves those recurring issues.

  • Like 2
  On 24/01/2022 at 21:40, xrobwx71 said:

I always initiate from an elevated command prompt powercfg -h off enter, reboot.  

 

The hiberfil.sys is notorious for corruption.

Expand  

I do the same for every new install of Windows 8 and newer versions

 

This is what I use: powercfg /hibernate off

 

I did not know that h would do the same thing...

First thing I do with a system with a SSD is go into the power options and disable fast startup. I can live with a couple extra seconds and avoid the headaches when I have to pull data off a dead PC. Fast startup is a sloppy hack, IMO. 

 

Microsoft has 3 decades of OS development experience. They know how to make a good OS. Its time to stop cutting them slack.

 

And no, I can't do better and no I don't code. That's what the brainiacs of this multi-billion dollar company are supposed to be for.

Edited by JustGeorge
  On 26/01/2022 at 00:58, aioraito said:

I do the same for every new install of Windows 8 and newer versions

 

This is what I use: powercfg /hibernate off

 

I did not know that h would do the same thing...

Expand  

-h not just h. But yes, it does.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Windows 11 gets 1Password passkey integration, version 25H2, and more with the latest builds by Taras Buria Microsoft is finishing this week with a now typical build duo for the Dev and Beta Channel users. For Windows Insiders in the Dev Channel, Microsoft is rolling out build 26200.5670; for those in the Beta Channel, Microsoft prepared build 26120.4520. Both updates have nearly identical changelogs with a new 1Password passkey integration, bug fixes, and more. Another important thing worth noting is that build 26200.5670 is the first officially confirmed Windows 11 version 25H2 build. 25H2 is this year's Windows 11 annual feature update, and it is now properly communicated in Settings > System > About and in the winver dialog. Note that the Beta build is still based on version 24H2. As for 1Password, customers who use this password manager can now enjoy a more seamless passkey experience. Windows Security will use passkeys stored in your 1Password and save new passkeys there as well. However, this change requires installing 1Password Beta for Windows 11. Here are other changes included in today's builds that are rolling out gradually: [Voice access] We are temporarily disabling support for Japanese to iron out a few more bugs. [Settings] In addition to the small changes that we made in the EEA region for default browsers via Settings > Apps > Default apps with Build 26200.5603, we’re also making this change: The new default browser will be pinned to the Taskbar and Start menu unless you choose not to pin it by clearing the checkboxes. [File Explorer] Fixed an issue which could cause File Explorer Home to crash (potentially also making File Explorer crash on launch, since Home is the default section for File Explorer). Fixed an issue which could cause the thumbnail for a pinned favorite in Home to disappear. [Start menu] Fixed an issue which was causing duplicate entries to appear when interacting with folders on the Start menu. Fixed an issue where the folder expand animation wasn’t correct in some cases. [Input] Fixed a high hitting ctfmon.exe crash in the latest flights, which could impact the ability to type. [Other] Fixed a memory leak which could happen when lock screen was set to use a slide show, which could impact performance and reliability over time. Did some more work improving how dialogs in the system react to increased text scaling, for example the “You must restart your computer to apply these changes” dialog should now support it. Here are the fixes that are available to all: [General] Fixed the issue causing the Windows Vista boot sound to play instead of the Windows 11 boot sound. Unfortunately the fix wasn’t completely working in the last Dev Channel flight. [File Explorer] Fixed the issue causing File Explorer to not persist view changes after the last Dev Channel flight, including desktop icons. And here is the list of known issues: [General] [UPDATED!]When joining the Dev Channel on Windows 11, version 24H2 – you will no longer be offered Build 26200.5641 first and will be offered the most current update available in the Dev Channel. [UPDATED!] When joining the Beta Channel on Windows 11, version 24H2 – you no longer will be offered Build 26120.4250 first and will be offered the most current update available in the Beta Channel. [UPDATED!] Some Windows Insiders may experience a rollback trying to install this update with a 0x80070005 in Windows Update. We’re working on a fix for Windows Insiders impacted. If you are impacted, using Settings > System > Recovery > “Fix issues using Windows Update” may resolve the issue. [Start menu] The following are known issues for Windows Insiders with the new Start menu: Using touch to navigate the new Start menu may not work reliably. For example, it currently does not support the swipe-up gesture. Drag and drop capabilities are limited from “All” to “Pinned.” [Xbox Controllers] Some Insiders are experiencing an issue where using their Xbox Controller via Bluetooth is causing their PC to bugcheck. Here is how to resolve the issue. Open Device Manager by searching for it via the search box on your taskbar. Once Device Manager is open, click on “View” and then “Devices by Driver”. Find the driver named “oemXXX.inf (XboxGameControllerDriver.inf)” where the “XXX” will be a specific number on your PC. Right-click on that driver and click “Uninstall”. [Click to Do (Preview)] The following known issues will be fixed in future updates to Windows Insiders: Windows Insiders on AMD or Intel™-powered Copilot+ PCs may experience long wait times on the first attempt to perform intelligent text actions in Click to Do after a new build or model update. [File Explorer] The following are known issues for AI actions in File Explorer: Narrator scan mode may not work properly in the action result canvas window for the Summarize AI action for Microsoft 365 files when reading bulleted lists. As a workaround, you can use Caps + Right key to navigate. [Widgets] Until we complete support for pinning in the new widgets board experience, pinning reverts you back to the previous experience. You can find the complete changelog for the Dev build here and for the Beta build here.
    • I'm in agreement with you here. I think the Windows Snipping Tool has the easiest highlight functionality to use. You literally select the highlighter and then just highlight. All other editors I have tried require some bizarre set of steps. So, 2 thumbs up'n'd'aya! for the Windows Snipping Tool with Idiot Proof Highlighter!
    • Microsoft officially confirms that Windows 11 version 25H2 is coming later this year by Usama Jawad Microsoft released Dev and Beta builds for Windows 11 today, and while the updates contain nearly identical change logs, one interesting observation is confirmation that Dev Channel users will be seeing Windows 11, version 25H2 in Settings > System > About and winver moving forward. Even though we had heard some whispers about it before, this is the first time that Microsoft has officially confirmed this next feature update to Windows 11. In a much more detailed blog post, Microsoft has made recommendations to organizations about how they can prepare for the arrival of Windows 11, version 25H2. The Redmond tech firm has highlighted that version 24H2 and version 25H2 both share the same Windows servicing branch, which means that the upgrade process should be fairly quick due to the presence of enablement packages (eKB). For those who don't know, enablement packages are bits and pieces of disabled code containing new features that are activated by Microsoft during a feature upgrade. This means that Windows 11, version 24H2 PCs can quickly update to version 25H2 in a single restart since the new code is already there, it just needs to be toggled on. That said, if you are utilizing a PC older than version 24H2, you won't be too happy to hear that it doesn't share the same servicing branch as version 25H2. What this means is that you'll have to go through the regular upgrade process through Windows Update or Windows Autopatch, which can be notably longer and require multiple restarts. As always, Enterprise versions of Windows 11, version 25H2 will receive 36 months of support starting from the release date, while Pro and Home variants will enjoy 24 months of support. It is worth keeping in mind that while Microsoft has confirmed that Windows 11, version 25H2 will begin rolling out later this year, it hasn't confirmed a concrete release date yet.
    • Mozilla fixes Firefox crashes on Windows by Taras Buria Mozilla is rolling out yet another update for the Firefox browser. Version 140.0.2 follows the just-released version 140.0.1 to address more bugs causing crashes on Windows in certain scenarios. Here is what the release notes say: Fixed a startup crash on Windows experienced by some users. (Bug 1974259) According to a post on Bugzilla, Mozilla's bug tracker for Firefox, the browser crashes with the ERROR_INVALID_HANDLE or ERROR_INVALID_PARAMETER error. This happens when Exploit Protection is enabled in Windows security settings. While that is a feature a regular user is unlikely to fiddle with, Exploit Protection is enabled for apps from the Microsoft Store. As such, crashes are most likely occurring for users with Firefox downloaded from the Microsoft Store. Still, if Exploit Protection is enabled globally, "standard" Firefox downloaded from the official website also fails. Note that the bug does not affect newer Firefox versions. Now, with Firefox 140.0.2 out, the browser should no longer crash regardless of your security settings or the browser origin. For reference, you can find the release notes for the latest update here; for version 140.0.1 (which fixed a couple of crash-inducing bugs), here; and for version 140.0 (a major release), here. As usual, you can update Firefox by heading to Menu > Help > About Firefox. The browser is available on the official website, in the Microsoft Store for Windows 10 and 11 users, or on Neowin's Software page.
    • They are always there, available third week every month, not fully public tho
  • Recent Achievements

    • Week One Done
      emptyother earned a badge
      Week One Done
    • Week One Done
      DarkWun earned a badge
      Week One Done
    • Very Popular
      valkyr09 earned a badge
      Very Popular
    • Week One Done
      suprememobiles earned a badge
      Week One Done
    • Week One Done
      Marites earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      563
    2. 2
      ATLien_0
      179
    3. 3
      +FloatingFatMan
      172
    4. 4
      Xenon
      122
    5. 5
      Som
      114
  • Tell a friend

    Love Neowin? Tell a friend!