Hi everyone.
I've previously had no problems with Macron reflect either imaging or cloning my 2Tb HD, but these last few days I've had an error when cloning - broken pipe.
The only thing different from last time I cloned is I had to use DISM to repair a problem, reinstalling the Windows 10 upgrade (to try & correct said problem didn't fix it) & the laptop crashed when I plugged the 2Tb HD in which I use for the clone. Of the three I suspect the external HD.
I have run DISM again with no problems found, cleaned the external HD using diskpart, formatted it to gpt & tried a different USB port.
I have attached a screenshot.
Is there anything else to try? I only have a 1Tb spare HD which I assume wouldn't be large enough to use as a clone HD to test.
TIA,
Have you tried using Restore Image instead of cloning ?? You could also try this from your bootable rescue disk also, if you haven't already.
One more thing, make sure you verify the image your trying to restore 1st also.
Thanks for your reply but am not restoring but creating a clone of my Win 10 pro to an external HD.
I wonder if an undeletable folder is the cause, after I reinstalled Win 10 update I was left with a Windows.old folder, I used disk cleanup to delete that folder but although it cleaned some of the files/folders I was still left with two folders which say are in use, can't delete at all.
I always verify the image when I create/run image backup.
Ok my mistake, I never use the clone setting, only use "image this disk" option myself. Try that option.Thanks for your reply but am not restoring but creating a clone of my Win 10 pro to an external HD.
I wonder if an undeletable folder is the cause, after I reinstalled Win 10 update I was left with a Windows.old folder, I used disk cleanup to delete that folder but although it cleaned some of the files/folders I was still left with two folders which say are in use, can't delete at all.
I always verify the image when I create/run image backup.
On those files you can't remove in your Windows.old folder, did you try booting into safe mode to remove them??that sometimes works better.
Not yet as I'll have to read up on how to do safe mode in Win 10 but am thinking of using a program from Malwarebytes - FileAssasin to see if that works, if it doesn't then try safe mode.
I want to make sure all avenues are covered should a problem with Windows occurs, if restoring an image doesn't work then I have a fail-safe backup of a clone with which I can just swap out the old HD & replace it with the clone HD.
One more sure way to remove those files in your Windows.old folder is to download Kyhi's program
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 blog
Which has many useful tools that can be VERY handy to have on hand. Including Macrium Reflect, among lots of other apps. This Would remove those files.
Booting into safe mode is actually easy, Use option 2in this tutorial.
Safe Mode - Start Windows 10 in - Windows 10 blog
I usually get this error when restoring image from an external drive. But then I found out that if I attach the external drive (on USB 3.0 dock), directly to a SATA port, the problem goes away. Probably just a data communication problem between the destination and the source. (YMMV).
Edit.
I just came across an article saying that macrium should have full permission to access files. Maybe this is why plugging the hard drive directly to the host PC fix the broken pipe problem.
Will look into that once I'm home, will let everyone know how things go.One more sure way to remove those files in your Windows.old folder is to download Kyhi's program
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 blog
Which has many useful tools that can be VERY handy to have on hand. Including Macrium Reflect, among lots of other apps. This Would remove those files.
FYI FileAssassin has not been updated for many years (pre-Win10) and AFAIK is no longer being developed.Not yet as I'll have to read up on how to do safe mode in Win 10 but am thinking of using a program from Malwarebytes - FileAssasin to see if that works, <SNIP>
So, I'm not necessarily suggesting that you not use it or that it would be harmful.
I would just be aware of the product history (and probably lack of robust support).
I might consider first the other options suggested.
Cheers,
MM
