Large orphan file deposited in 'C:\Winows' if machine shuts down with an image (.TIB) mounted.
When an image file (filename.tib) is mounted, a working file is created in 'C:\Windows' with a system mount point filename similar to {DF61B605-D744-11E1-B676-00248C52D922}. In this release of ATIH, on my machine, the last part of the name is always "00248C52D922". Maybe it's always "00248C52D922", I can't say.
If the computer is shut down deliberately or crashes while an image is mounted, the file becomes orphaned. I discovered this when I was looking for a reason why my windows directory had increased in size by more than 27 GB (i.e. to 50 GB). If the temp and dump directories are kept clean, the Windows directory on a W7 x 64 installation will be about 23 GB and will grow only 2 or 3 GB ever. There were five of these files that had accumulated over the last year and a half or so. One was 15 GB by itself.
If any of these files are present at startup they can only be orphans and should be removed by an ATIH background process for obvious reasons or there should be clear instructions to the user to look for them and remove them manually.
In addition, there are 538 registry entries (currently on my machine) referencing every mounted Acronis image I have used in the year and a half since this W7 installation started running on this machine and that has probably not been more than 12 occasions. These should also be cleaned by an Acronis process for obvious reasons. This registry entry residue represents mounted images that were unmounted properly as well as those that suffered a surprise. I am certainly not going to even try to remove these manually.
- Accedi per poter commentare
I am building an image for migration to new hardware, to avoid potential problems I will retry Beta 2013 after that move is complete.
Thanks
- Accedi per poter commentare