Windows 10: Restore does not indicate correct drive for source of restore

I have recently had to re-install Windows 10 and had problems before so decided this time to do a clean install and then run the system image backup. This went well but when it came to the testing of the restore a problem arose. I was using the Repair Disc created after the system image backup completed and could not understand the source file indicated was not where I had put the backup.
The restore said the file was on the C: drive which was what I was trying to restore to.
I repeated the whole process and took screenshots (photos) of the steps. These photos can be seen on dropbox or onedrive links to those interested (not posted here).

Has anyone seen this before and is there a solution?

:)

 

System Restore failed to extract the original copy of the directory from the restore point.

I suspect that this is indicating a read problem. I received it when for some reason System Restore tried to read for the RP (ie: restore point) from my External HDD after using that drive for a full recovery from backup. It appears to be indicating
a problem with the RP version of \WindowsApps as the source I suspect.

This is as apposed to the error 0x80070091, which would now appear to be a
write issue to the actual \WindowsApps directory as the destination.

 

File History Not Backing Up All Files in Included Folders!

I recently changed over to File History, did a couple of backups from my laptop to an external USB hard disk, and then used File Explorer to browse the File History folder on my backup drive, comparing it to a view of the source drive in another File Explorer
window. From that comparison, it does appear that there are files missing. Comparing folder properties between File History and the source indicates a difference (in my case) of over 4000 files.

However, if I use File History to view the backup (on the Start menu, search for 'Restore your files with file history'), I am able to navigate to the folders which I thought had files missing and see the files (in my case, a very important report in Word
2016 and a PDF file). To test, I restored them to a different location, a TEMP folder, so I could compare them with the originals. They, indeed, were exact copies of the files that I thought did not get backed up.

That being said, as we do not know Microsoft's methodology for File History, I would encourage you (and everyone else experiencing this same issue) to do the same as I did to see if your files are really not being backed up. Even choose an entire folder
tree and restore it, then compare it to the source; or if you have a spare drive of appropriate size, do a full restore and compare it. After all, it is not how the files are stored in the backup that is important, but whether we can restore all of the files.

 

Rest assured, before you know it, someone will tell you to use other "more efficient" program such as macrium reflect.

Be it as it may, I just want to share with you what I do using the built-in Windows 10 system image backup.
I never create the Repair disk.
When I want to run the image restore and if I am already signed in, here is what I do. It may appear lengthy but it never fails me.
I store my system image backup in an external hard drive.
So, first I plug in the ext. hdd.
Start button > Settings > Update & Security > left side, Recovery > right side, under Advanced startup, click the Restart now button > Troubleshoot > Advanced options > system Image Recovery...................

 

Your suggestion was incomplete as shown on the page.
I know about Macrium I have my own preference DriveSnapshot which does everything I think Macrium does and I have been using it for years. I wanted to have a guaranteed MS way of restoring an image.

Using DriveSnapshot works and allows viewing as a drive and selecting individual files to restore.

Your answer does not answer my question.