Macrium Reflect v7 wont make rescue media (iso or USB)

BrokenDaily · 27 Aug 2019

So I decided to install macrium reflect v7 free (current installed version at v 7.2.4325) to make a backup of my current windows OS in-case my updating to windows 10 1903 doesn't go well, so that would involve making a rescue media and either burning it to a disc, or a usb, so I go USB

I open the advanced tab, and on choose base WIM, I use windows PE 10 (WADK) since the 1st option doesn't work, so it downloads the needed files, and I expect the USB stick to be turned into rescue media, but it fails every-time, and the following logs below show what errors it spits at me

I haven't used this in a while, not since v6 of the reflect program if I remember, so I am puzzled on why v7 wont let me make a rescue media usb drive. I want to stick with reflect since it seems this forum highly recommends it over others, but am I forgetting to do something macrium wise, or is it as simple as choosing a different base wim option in the advanced tab?

AK6DN · 27 Aug 2019

I would go download v7.2.4440 ... .4325 was having USB issues in building rescue media.
Read release note here: Macrium Reflect Patch Details

BrokenDaily · 27 Aug 2019

just downloaded and installed the 7.2.4440 update and installed it over the other macrium I had, still didnt work; did a full uninstall and reinstall and I am re-downloading the WADK components to see if it works now

if this doesnt work, does acronis let you make a usb rescue drive to restore windows backups without needing winpe components?

Try3 · 27 Aug 2019

Acronis TI & its boot disk only work for restoring system images that Acronis TI has made. It cannot restore images made by Windows, Macrium, ...

It used to be able to restore Windows images [.vhd] in Windows 7 but Windows 10 makes .vhdx images which Acronis TI cannot read.

Denis

AK6DN · 27 Aug 2019

So can you use Macrium and build the rescue image into an ISO file (not burn to disc or write USB)?

If that does not work either, you might try posting here: Macrium Support Forum
on the Macrium support forum.

From your .zip error log files I see this:

Code:

Cannot create a file when that file already exists. 
Mount failed.
Unmounting the wim - 8/27/2019 3:34 PM
"C:\ProgramData\Macrium\Reflect\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\imagex.exe" /unmount "c:\boot\macrium\WA10KFiles\mount"

so there might be a permissions problem on an existing file that you can't delete/rewrite.

Are you running Macrium as an administrator when you try and generate the rescue media?

Bree · 27 Aug 2019

BrokenDaily said:

...I am re-downloading the WADK components to see if it works now...

The default in 7.2 is to make WinRE media because that requires no download, the WinRE recovery environment is copied from your recovery partition. The .wim file is built in the 'staging area' which is c:\boot\macrium. Details here:

Rescue Media Builder - How It Works - Macrium Reflect Knowledgebase - KnowledgeBase v7.2

Your waiklog.txt has several entries where dism tries to mount a .wim from the staging area and reports:

Error: 183
Cannot create a file when that file already exists.

This suggests the is a problem in the staging area. If you continue to fail making RE or PE rescue media, try deleting the staging area folder. Macrium will recreate it when you next run the rescue media builder. If you stiil can't build media, look to see if a 3rd-party AV may be blocking access to the c: drive.

Try3 · 27 Aug 2019

You might also consider setting up Macrium's Boot menu as an alternative / an interim workaroud.

Denis

Bree · 27 Aug 2019

Setting up the Macrium boot menu may also fail, that too has to mount and build the .wim and it is this step that seems to be failing.

Anibor · 27 Aug 2019

Yes, it´s a DISM problem, it seems it can´t mount the image. It affects both the WinRE and the WinPE processes. Maybe caused by a previous process which didn´t finish normally.

Bree · 27 Aug 2019

Anibor said:

Yes, it´s a DISM problem ... Maybe caused by a previous process which didn´t finish normally.

Restart the PC. This will perform a full restart from cold and should stop any dism processes that are still running in the background. Use Restart, not Shut down as that may use Fast Startup to perform a warm boot which can leave some processes still running.