Aller au contenu principal

Images only visible after chkdsk /f

Thread needs solution

I am slowly to Windows 10 from Windows 7 and in that proces i purchased a new SSD on which installed Windows 10. First i did a Win installation using a microsoft account, and made images as i progressed with software instalation, optimizations, changes etc. (Image01, Image02 etc.). After a while i became aware that i could install windows with a local account, so i did a new install of Windows 10, but with a local account (these were named LK_Image01, LK_Image02 etc.). All images were saved in a folder on a separate, internal 2TB HDD. I played around and decided to restore to a MS account Windows 10 install (Image04) The problem is that now i could only see the images made from the first installation (i.e. Image01, Image02) but not the ones with the prefix LK. They weren't visible neither from the Windows 10, nor the installed ATI2020 nor from the ATI bootable media. I then hooked up my Win7 SSD and the images could not be seen here either. In both Win 10 and 7 i could see that the space was used, but only the imnages made of the first install were visible. Searching elsewhere i found a "solution" in doing a chkdsk x: /f (x is the drive letter of the HDD with backups) from a admin level cmd.. This promted Acronis Active Protection, but after allowing chkdsk to run it did its thing and the "orphaned" files became visible (chkdsk identified them as orphaned files). My question: Is it something in the ATI2020 that "hides" images from being seen? E.g. images made with different windows account.

Fichier attaché Taille
Procedure ATI2020_1.pdf 310 Ko
0 Users found this helpful

Daniel, welcome to these public User Forums.

The issue that you describe is caused by Windows Fast Start being involved and your computer not being fully shutdown when you created the orphaned backup images!

Windows Fast Start is used to improved startup times for the OS and does so by using a Hybrid Sleep state when you shutdown, putting the computer in a hibernation type state.

When you make a backup in this state, then the changes to the filesystem created by making the backup files is lost when Windows is restarted and resumed from the hibernation state.

This is a known issue that has been reported multiple times in the forums.

Thank you welcoming me to the forum Steve and thanks for the answer. I did read about the Fast Start and hybrid sleep, and initially i thought that that was the problem. However, the first three images were made using Acronis Bootable Media (ABM) from a USB pendrive. Windows was restarted, and at start I chose boot options and booted into ABM-USB. I only installed ATI2020 in Windows after that third image. So i'm guessing that Windows Fast Start shouldn't be the issue here, or am i missing something?

What's even more weird is that the first set of images, made of the Win10 MS-account install, were all made in the same way, and those are visible.

Daniel, this has been the case with other users seeing this type of issue, where resuming from a hybrid sleep state has 'lost' any file system changes made during that state by ATI from the bootable USB / CD/DVD rescue media.

The only sure way to avoid this is to either turn off Fast Start or disable Hibernation from within Windows, or else perform a full shutdown by pressing / holding a Shift key while clicking on the Shutdown option.