On that storage issue, I don’t understand it. But I thought it might be doing something to the files or even format to make them look bigger than they are. Not that anything is running, that the files been changed, basically corrupted. But I, too, doubted that was the issue.
Actually, even Windows, under its imaging process, says in order to have the necessary volumes, it must be three of them, the C drive (the Windows partition), the EFI partition, and the “push button” recovery partition. The other two partitions are so small, a few hundred MB each, that it doesn’t even matter. My Win 10 was an upgrade from Win 8.1.
I have to run Legacy in bios in order to boot from a DVD. That is so even when I boot my Win 10 installer disk, which I have to presume Win 10 made with Win 10 OS on it. Of course, UEFI is required to boot it from the Win 10 OS on the hard drive. Its a pain in the neck, I have to keep switching back and forth for this kind of thing. But, it means Acronis True Image is booting as Legacy.
And you just confirmed that Acronis True Image 2016 is fully compatible with the newest level of the Win 10 OS. Thanks, at least I have that answer now. So, can rule out that consideration.
Could the bad sectors on my internal hard drive be the issue? They have been like that for quite some time, were like that when I last imaged in April, and I’m pretty sure also when I imaged last year. (I had already decided to get another disk, but I need this image now so I can put it on any disk I get.) Until I get this image, I do not want to do anything that might impact or damage the April image. Gee, even copying it off the disk could result in something corrupted in that image, so I don’t even want to do that.
Will get a shot of Disk Management and post. I’m on a different computer right now.