Terabyte Image for Linux Cold Image Question

If you use Image for Linux to make a cold image of the C: Drive of Windows 10 64 bit is it necessary to have Windows 10 Hibernate turned off prior to making the image? Also, is it necessary to have Hibernate turned off before restoring a Windows 10 image? I have never made a restore but I have made cold images. I don't remember seeing any Image for Linux warning about Hibernate being turned on.

I thought about this because today I booted the Kasperksy Rescue ISO and got Warning messages from Kaspersky that Hibernate is turned on and that if any malware cleaning is done using Kasperksy Rescue ISO that the Windows Operating System may be crippled by the malware cleaning.

Thanks in Advance.

 

Not necessary.
For IFL and IFW, hibernate file and some temp files are automatically excluded during backup and restore.
So just go ahead and use it.

 

TheKid7,

Are you referring to Fast Startup? This is different from standard hibernation.

https://www.terabyteunlimited.com/ucf/viewtopic.php?f=2&t=427

 

Does Fast Startup corrupt cold imaging/restores?

Thanks in Advance.

 

If you have a Windows only System and don't use any external processes that run outside of the managed System, you should be OK. BUT, if you use outside processes like dual-BOOTing or RAM-based WinPE processes that share those volumes, there can definitely be problems due to the way Windows "doesn't" put away its drives properly when using FastBOOT. If those "outside" processes rely on a properly closed FileSystem there definitely can be issues.

 

PC users with only regular Windows OS or dual boot OS on the same disk there should be no issues as long as you image/restore the whole disk. I don't see any problem with it.

 

It looks like Fast Startup is dangerous even if you only have one OS...

https://www.terabyteunlimited.com/ucf/viewtopic.php?f=2&t=3709

 

Thank you bro for the heads-up.

I already ran "powercfg -h off" in cmd as admin.

Upon starting IFW, it still warns that fast startup is on. How come?

Edit: The Terabyte user community forum has tons of useful info. Just found the way to turn off fast startup in the post: Corruption using W8 and W10 with Fast Startup - TeraByte Unlimited
Basically - temporarily turn on hibernation, disable fast startup, then disable hibernation.

 

I think the Registry entry is still present.

 

Although we've referred to IFL in this thread, the issues with Fast Startup apply to any imaging app. Or any app that writes data to a Fast Startup hibernated drive.

 

After I temporarily turned on hibernation, disabled fast startup, then disabled hibernation, then message is gone.

 

That certainly fits with what Fast Startup can do.