Backup and Restore Windows 10 Pro

Hi,

I don't think that cloning is an issue.. Normally cloning software has the ability to resize partitions and etc. as needed to fit a smaller drive.. Within reason of course..

WindowsImageBackup requires that the disk receiving the image is the EXACT same size or larger for the process to work.. I have had threads in which a HDD\SSD was maybe only 5mb smaller, or even less, and WindowsImageBackup would refuse to proceed.. It will cut you absolutely no slack on that issue..

It is possible that WindowsImageBackup has issues with a drive of a different manufacturer as well.. It is incredibly picky as to what it will accept.. I will see if I have anything laying around to test that..

I believe we are getting off track. None of what you say about issues with a drive of a different manufacturer is true, because, as I stated before, I have been using them together for years, but thanks for the comments.

Hi,

WindowsImageBackup is very finicky.. To make my point, I just tried recovering one of the images that had previously worked earlier this evening to an exact duplicate of the 512GB SSD that I use for Windows.. The images did appear as available, but all attempts failed with some error concerning "An Active Data Drive In Bios" and another I don't remember..

But prior to this I made the mistake of changing two things at once.. A different drive, and I renamed the folder inside the WindowsImageBackup folder copy.. It's name was Asrock just for reference.. I simply added a date..

When initially attempting to recover these two images to a 1TB HDD and a 512GB SSD, neither of my brand new images were appearing.. After a good bit of head banging I tried something else.. One of the things I tried was creating a 3rd image which worked normally.. This gave me the idea to return the renamed folder to it's original name.. Suddenly I now had all three images available and working.. It seems that tinkering with the copy also caused the original to not appear.. After returning the copy to it's original name, it and the original appear and work..

BTW... Have you been switching the actual WindowsImageBackups between different drives ?

I should note that I have been doing this for a good number of years as well.. I haven't used it much lately due to the types of issues we are discussing now.. The free Macrium Reflect seems to be an excellent imaging tool, but that will not make your existing images usable..

My recollection is that at one time I was able to recover images to different drives without issue, but the Windows 7 Backup + Restore has appeared to me to become less reliable with every new build of Windows 10..

That's right, mounting the .vhdx is only useful for recovering individual personal files. Then, the apps that use them would have to be reinstalled, if not already present.

I still think you needn't have installed Windows first. Backup & Restore would have done the reformat if run from any external recovery environment. I would only run it from the Recovery partition if all the partitions were the same size & in the same position as they are in the image. Also, I'd want the existing Recovery partition to be of the same Windows version as is in the image. I don't think I'd even want a greater version in that case. However, I don't think this was your problem because I'm sure the images should have at least shown up.

The fact that the images don't even show up on any computer is really puzzling. I thought Slance310 might have been right about permissions, but why would they have changed on all the HDDs/partitions involved or gone bad in all the computers? And you say they haven't changed at all anyway. The other things he said (like renaming or moving WindowsImageBackup off the root) could also have done it, but you say none of that happened.

I wonder whether Backup & Restore will write a new image to those drives? Plug one in, open its WindowsImageBackup folder, & rename the computername folder inside. Then make a new image to that drive. It should go into the WindowsImageBackup folder & have the name of the computer. It will be separate & distinct from the renamed one, & both would be offered by the restore process (if you ever get that to work).

Well, as I said, I have been using that procedure for years, even before Windows 10, and never had any problems. I have been backing up with a Windows 7 image back forever and it seems to be a coincidence, at least in my setup, that when I discovered that I could not restore to one laptop because of one set of problems with that laptop, I ended up discovering that my other laptops, which had not had any problems, all of the sudden have the same problem, and the thought occurred to me that since Microsoft stopped supporting Windows 7, the programmers had inadvertently, perhaps, screwed up by removing or changing something that relates to old WindowsImageBackup files, which are part of the Windows 7 legacy.

The way I have been backing up my 4 laptops is by deleting old backups wherever they happen to be, and reformatting the drive or partition prior to backing up. So, as a consequence, backups from a particular laptop does not always gets backed up in the same drive or partition. My experience has shown me that it does not matter where it is as long as the correct USB drive with the right backup is connected to the laptop, the software will find it. I never change anything after creating the backup file.

I did try the Macrium Reflect free version, but it does not work other than with the files it created, It will only restore its own backups.

...snip...

By the way, the procedure to mount the vhdx file is more complex than that. Since I tried double clicking the file to mount it and it did not work, I did a search and found this procedure: How to Create and Mount VHD / VHDX File in Windows 10 – Step by Step Guide (systoolsgroup.com)

We don't get notified of edits. You should only edit a post to which there has not yet been a response. And even then, do it quickly because a response may have already begun. And when I begin a response, it may be an hour before I'm through.

Anyway, that link is informative as to creating one's own .vhdx to use as a partition on a more/less permanent basis. looks like. I guess it's a way to have a partition without using as much space as a real one. I never did that. I'd prefer to find space on a drive & create an actual partition on it.

But the bottom two sections -- "Attach Virtual Hard Disk" & "Dismounting VHD and VHDX in Windows 10" -- are an alternative to double-clicking (or right-click, Mount) the .vhdx of Backup & Restore. That way, you probably won't get the error message. But all you had to do was was click OK on the message, then put a letter on the fake partition using Disk Management.