- Jan 13, 2018
- 57
- 0
- 11
Hello again. While experimenting with the problem of my previous post, an unbelievable encounter happened:
In Recovery Environment, with only the <300MB in recovery drive, and 400KB in image backup, Windows was able to create itself, without any proper source.
What happened is that, using "System Image Backup", I created an image.
I formatted the destination partition.
In the folder WindowsImageBackup\[ComputerName], I deleted all the 13 files that held the contents of the image, and made sure they were permanently deleted and no other image existed in storage. The folder size became only 400KB.
In spite of that, "System Image Recovery" detected an image, and the restore process was made into the new formatted partition.
The resulting OS appeared complete. It's folders and files were there in the new partition. I logged into it with my specific user name, and it was functioning normally.
How can the Image Recovery tool create the OS, without the GBs of files that hold the contents of the image?
I'm curious to know if anyone can explain.
In Recovery Environment, with only the <300MB in recovery drive, and 400KB in image backup, Windows was able to create itself, without any proper source.
What happened is that, using "System Image Backup", I created an image.
I formatted the destination partition.
In the folder WindowsImageBackup\[ComputerName], I deleted all the 13 files that held the contents of the image, and made sure they were permanently deleted and no other image existed in storage. The folder size became only 400KB.
In spite of that, "System Image Recovery" detected an image, and the restore process was made into the new formatted partition.
The resulting OS appeared complete. It's folders and files were there in the new partition. I logged into it with my specific user name, and it was functioning normally.
How can the Image Recovery tool create the OS, without the GBs of files that hold the contents of the image?
I'm curious to know if anyone can explain.
Facebook
Twitter