Can't create rescue media


Author
Message
davefox
davefox
New Member
New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)
Group: Forum Members
Posts: 5, Visits: 17
I'm new to the product (an Acronis refugee) and have been creating backups successfully for a couple of weeks.  But I cannot seem to build rescue media on a USB stick.
After getting an error the first time, I went through the procedure for "Preparing a USB stick for Windows PE" on this site, but it still gives the same error.
The error message is:
 
One or more WinPE files failed to copy to the USB device.
The rescue media may not work as expected; the log file will contain more information.

The log file:

Open handle to physical drive: \\.\PHYSICALDRIVE4
Read drive geometry
Check for active FAT32 partition in removable media
Partition 1 has active FAT volume
Calculate space required for PE files
PE File Count: 228 requiring 569.1 MB disk space
Determine target volume for WinPE files
Partition 1 is size 3.73 GB
Partition 1 is FAT type
Volume for partition 1 is \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\
Volume \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\ has file system FAT32
Determine free space on hard disk volume \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\
Free space on disk volume \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\ is 3.72 GB
Checking for existing target WIM file
Disk volume \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\ is the Active partiton
Disk volume \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\ meets requirements
Free space at end of disk: 0 B
Writing MBR boot code
Existing MBR boot code found, skipping write of MBR boot code
Setting target partition active
Target partition successfully set active
Writing partition boot sector code
Removing pre-existing drivers...
Copying WinPE files to target volume...
Copying c:\boot\macrium\WinREFiles\media\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\
Copying c:\boot\macrium\WinREFiles\media\Boot\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\
Copying c:\boot\macrium\WinREFiles\media\Boot\bg-BG\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\bg-BG\
Copying c:\boot\macrium\WinREFiles\media\Boot\cs-CZ\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\cs-CZ\
Copying c:\boot\macrium\WinREFiles\media\Boot\da-DK\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\da-DK\
Copying c:\boot\macrium\WinREFiles\media\Boot\de-DE\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\de-DE\
Copying c:\boot\macrium\WinREFiles\media\Boot\el-GR\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\el-GR\
Copying c:\boot\macrium\WinREFiles\media\Boot\en-GB\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\en-GB\
Copying c:\boot\macrium\WinREFiles\media\Boot\en-US\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\en-US\
Copying c:\boot\macrium\WinREFiles\media\Boot\es-ES\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\es-ES\
Copying c:\boot\macrium\WinREFiles\media\Boot\es-MX\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\es-MX\
Copying c:\boot\macrium\WinREFiles\media\Boot\et-EE\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\et-EE\
Copying c:\boot\macrium\WinREFiles\media\Boot\fi-FI\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\fi-FI\
Copying c:\boot\macrium\WinREFiles\media\Boot\Fonts\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\Fonts\
Copying c:\boot\macrium\WinREFiles\media\Boot\fr-CA\ to \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\fr-CA\
Failed to open handle to target file \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\fr-CA\bootmgr.exe.mui (3): The system cannot find the path specified.
One or more PE Environment files failed to copy to the USB device

The USB stick is left with a single folder, "Boot", with contents correponding to the Copying entries in the log, and a total used space of 20.9 MB.  After the error message appears, the creation process stops.

What's going on?  Thanks for any help.




Beardy
Beardy
Proficient Member
Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)
Group: Forum Members
Posts: 313, Visits: 1.4K
Failed to open handle to target file \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\fr-CA\bootmgr.exe.mui (3): The system cannot find the path specified.
One or more PE Environment files failed to copy to the USB device

This leads me to suspect the program lost communication with the drive momentarily.
You could try using a different USB port.
If you have one you could also try a different USB drive.

If you have third party anti-virus running, you might also try with that disabled.

davefox
davefox
New Member
New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)
Group: Forum Members
Posts: 5, Visits: 17
Thanks for the reply.
I've tried it a few more times, with Malwarebytes disabled.  Each time, it fails , but not always in the same place.  On the most recent attempt, the log file says

Failed to open handle to target file \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\EFI\Microsoft\Boot\zh-TW\bootmgfw.efi.mui (3): The system cannot find the path specified.
One or more PE Environment files failed to copy to the USB device

That folder does exist.  But note that the log says bootmgfw.efi.mui.  The other time, it was bootmg.efi.mui.  I don't know what to make of the fw in the filename.
I've used multiple USB sticks, multiple computers, and have plugged them into multiple USB ports.
dbminter
dbminter
Most Valuable Professional
Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)
Group: Forum Members
Posts: 2.9K, Visits: 27K
Also, make sure the file bootmgr.exe.mui exists somewhere on the drive where you have Reflect installed and/or where Windows is installed.  Sounds to me like the file simply isn't there to copy over to the Rescue Media.  For some reason, it looks like a translation file for French.  Are you trying to build French language Rescue Media?  You may not actually trying to be, but the Reflect Rescue Media may have those files on the media as part of the installation.


As I said, sounds to me like the file trying to be copied over is simply missing for whatever reason.  How to fix it, I couldn't say.


In the meantime, try creating the Rescue Media you're trying to build to an ISO file.  See if that succeeds.  If it does, as an interim step until you get this resolved, you can take that ISO and burn it to a bootable flash drive with something like Rufus.  Although be aware Rufus will erase all the contents on the flash drive every time you write an ISO to the flash drive.  Unlike the behavior of the Rescue Media creation wizard, which will default to keeping all files intact except those it needs to overwrite, unless it encounters a case where it can't.  You'll be informed if it can't, which will erase all the contents on the flash drive.

Beardy
Beardy
Proficient Member
Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)Proficient Member (382 reputation)
Group: Forum Members
Posts: 313, Visits: 1.4K
@dbminter You beat me to suggesting .iso > Rufus as the next possible workaround.
davefox
davefox
New Member
New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)
Group: Forum Members
Posts: 5, Visits: 17
Thanks, dbminter.  I was able to create the ISO file.  Not familiar with Rufus, but I'll look into it.

I'm not trying to create anything in French, but the media creation tool looks like it creates lots of folders under Boot for various languages.  These folders all seem to contain only two files, bootmgr.exe.mui and memtest.exe.mui.  I don't know where it's getting the files to copy, but the error messages indicate that it can't find something on the target device.  And the error is happening in different places in the process.

I run several apps that write to usb sticks and have never had any issues with them, so it's hard to understand how simple copy operations could be failing.

I need to understand what's going on.  Booting off a USB stick is an important part of the backup/restore strategy, so it's a bit unnerving that this is happening.  
dbminter
dbminter
Most Valuable Professional
Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)Most Valuable Professional (4.3K reputation)
Group: Forum Members
Posts: 2.9K, Visits: 27K
If you can create ISO files, then the problem does appear to be one writing contents to the flash drive.

davefox
davefox
New Member
New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)
Group: Forum Members
Posts: 5, Visits: 17
OK, used Rufus to create the usb media.  No errors, and the USB stick has about 569 MB of data on it.  I'll try to boot off it tomorrow and see how that goes.
Thanks for the help!
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)Macrium Evangelist (15K reputation)
Group: Forum Members
Posts: 10K, Visits: 65K
When Rescue Media Builder throws errors about not being able to find or access files, it's usually third-party AV that's intervening, even if that AV isn't advertising that it's doing so -- which always makes it more exciting to troubleshoot issues it causes.  It can happen with Rescue Media because Rescue Media includes some utilities that can be used for malicious purposes, such as utilities that can modify boot sectors of hard drives.  But of course those utilities also have legitimate purposes.  Are you running third-party AV?

davefox
davefox
New Member
New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)New Member (6 reputation)
Group: Forum Members
Posts: 5, Visits: 17
Yes, Malwarebytes.  I tried disabling its four real-time protection functions (web, malware, ransomware, exploit) but the build still failed with the same error.  I also run Windows Defender, but I didn't do anything with it.  It's not so easily turned off, and I haven't done anything to customize it, so I figure it's not "third-party".  If there's a conflict with Defender, I'd expect lots of people to have seen it.

The error message is, as always, a bit cryptic.  "Failed to open handle to target file \\?\Volume{103950a5-4889-11eb-ae51-40b076430cea}\Boot\fr-CA\bootmgr.exe.mui (3): The system cannot find the path specified."  The target folder most certainly exists, and I don't know the significance of the "(3)" that follows the filename.

In earlier attempts, I also found that a failed attempt somehow munged the flash drive, requiring me to reformat it, or to use the method in the "Preparing" document that I mentioned in the OP.  Strange stuff.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search