<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Hibernation on Aperture Zone</title>
    <link>https://aperturezone.com/tags/hibernation/</link>
    <description>Recent content in Hibernation on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/hibernation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GPO - Disable hibernation</title>
      <link>https://aperturezone.com/gpo/no-hibernation/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/gpo/no-hibernation/</guid>
      <description>&lt;p&gt;Hibernation can be useful on a laptop. You close the lid, the system saves the state of the RAM to the disk, and you pick up where you left off a few hours later. However, it drains the battery.&lt;/p&gt;
&lt;p&gt;On a workstation, it’s a different story. Hibernation reserves a &lt;code&gt;hiberfil.sys&lt;/code&gt; file on the system drive whose size is equivalent to the total amount of installed RAM. On a machine with 32 GB of RAM, that’s 32 GB of disk space locked up for a feature that no one will ever use.
Another consequence observed in production: updates distributed by an internal WSUS server that require a reboot fail every time. Upon further investigation, you’ll find that after the reboot requested by the update, the uptime counter in Task Manager hasn’t been reset to zero, so the machine hasn’t actually rebooted.
Result: WSUS waits for confirmation of the reboot; the machine reports &amp;quot;reboot complete&amp;quot; but technically it hasn’t, and certain multi-stage updates (particularly cumulative updates and kernel security updates) remain stuck indefinitely.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
