Re: PSA: Somehow, without action from me, hyberfile.sys got turned on

...he wrote:
> Having figured out it was the hibernation file, you've also(at least 
> should have) figured(out) that it wasn't 'out of memory'.
> 
> Fyi...nothing in Windows on an existing installation(monthly updates, 
> app updates, software updates, disk cleanup(Windows or 3rd party), 
> imaging, etc. re-enables the hibernation file on disk, the exception is 
> the user changing or tampering with the o/s.

Hi Winston,

Thanks for correcting my technical grammar. 

I agree. The use of "memory" was a thinko since the hard drive is storage.
That memory relates only as my 16GB likely caused a reduced-size hiberfile.

Therefore, I publicly humbly agree & apologize for my inadvertent faux pas.

I never disagree with anyone who makes a logically sensible statement.
But I do disagree with those who make illogical statements sans references.

Based on my lookup during my earlier debugging, there are multiple
documented and Microsoft-acknowledged scenarios where Windows updates,
system changes, or OEM/firmware behavior can automatically re-enable
hibernation and recreate hiberfil.sys, even if the user previously disabled
it.

Hence, I must disagree with you on two counts about nothing re-enables the
hibernation file, one of which you can check but the other is on trust.

You have to trust me when I say what happened to me, happened.
Just as I trust Paul when he says what happened to him, happened.

However, if you don't trust me, then that's fine. Go to step 2.

Step 2 is look it up.
I did.

I was as shocked as you will be (I presume).

Apparently, it "can" happen.
Apparently it "did" happen.

What did YOU find when you looked it up?

HINT: Fast startup REQUIRES hibernation.
DOUBLEHINT: Windows Update can enable fast startup.