Skip to main content

unable to mount the source wim file

Thread needs solution

Hello,

I am trying to make Rescue Media but have faced the error "Unable to mount the source .wim file". It happens even if I choose Simple method and ISO or WIM files.

Changing TEMP folder to C:\Temp does not help.

Thanks for your help.

BR, Oleksandr

Attachment Size
acr.png 56.05 KB
0 Users found this helpful

Oleksandr, welcome to these public User Forums.

The Simple method for the rescue media builder uses the wim file from your Windows Recovery Environment and therefore the error message you are seeing suggests that there is either a problem with the Windows Recovery Environment or else you have more than one such recovery environment on your computer and Acronis is finding the wrong one!

You can check the status of your WinRE by using the following command from an Administrator level command prompt window1:

REAGENTC /INFO

C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: f613c408-ab3e-11e9-ac1c-a86daa71efa2
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

To check if you have more than one Recovery partition on your computer, use the following commands:

diskpart

list disk

select disk 0  (where this is you Windows OS disk)

list partition

(check for partitions shown as type Recovery).

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.18362.1

Copyright (C) Microsoft Corporation.
On computer: STEVE

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          465 GB    46 GB        *
  Disk 1    Online          931 GB      0 B
  Disk 2    Online         1863 GB  1024 KB

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Reserved           128 MB    17 KB
  Partition 2    System             260 MB   129 MB
  Partition 3    Primary            417 GB   389 MB
  Partition 4    Recovery           979 MB   464 GB

DISKPART>

Please take great care using diskpart as it is very powerful and can destroy your OS if used incorrectly!

See KB 60091: Acronis True Image 2018: how Simple bootable media creation mode works

Hello Steve,

Thanks for your reply.

Sorry, I forgot to mention. My OS is Windows 7. Then I downloaded and installed Windows ADK and PE. During ADK installation there was a message that one driver was not signed. After that I tried to make Rescue Media for Win 10 but faced the error (unable to mount the source wim file). When I tried to make Rescue Media for the same laptop (Win 7), it was the same error. Finally, the current Win7 laptop has been back up and restored many tims with ATI 2012 without issues.

Regarding reagentc, I am an administrator on my laptop but it still requires more privileges. Do you know how to run it (cmd) with higher privileges?

Regarding Recovery partition, it's one only.

  Partition 1    Recovery             13 Gб      1024 kb

  Partition 2    Reserved             100 Mб   13 Gb

  Partition 3    Primary                81 Gб      13 Gb

  Partition 0    Extended(?)        501 Gб    94 Gb

  Partition 4    Logical (disc D)   501 Gб    94 Gb

 

Best regards,

Oleksandr

Oleksandr, if you have installed the Windows ADK, then this should negate any issues with your Windows Recovery Environment but you also need to use the Advanced method of the Acronis rescue media builder in order to use the ADK.  The Simple method will always use the WinRE files.

Even as an Administrator, you need to right click on the CMD.exe and select to 'Run as Administrator' to have the correct permissions to run REAGENTC.

Please also see forum sticky topic:  How to repair the TI 2020 build 22510 boot disk created in Windows 7 using the Simple option - which may be relevant after you can create the rescue media as you are still on Windows 7.

You can also use the MVP Custom PE Builder tool with the installed ADK to create the media - link in my signature.

Hi Steve,

It seems my Windows RE is disabled.

 Windows RE status: 0

 

My ultimate goal is to have one bootable USB Flash drive to make partition images for both Win 7 and Win 10 on different laptops. IDo you think it is feasible?

BR, Oleksandr

I would suggest making the rescue media on your Win 10 laptop if possible as this should work fine for both computers provided they both use the same CPU architecture, i.e. are both 64-bit systems.

If you have a mix of 32-bit and 64-bit systems, then use the MVP Custom PE tool on the Win 10 laptop and create the 32-bit version of the WinPE rescue media which will again work on both computers.

The alternative is to use the Advanced >> Linux version of the rescue media which is capable of being used on both architectures too.

Thanks Steve.

As you recomended, I installed ATI 2020 on my new laptop where Windows 10 and created there rescue media on USB flash drive. Unfortunately, I could not to make back up using it as it was made in trial version.

Then I downloaded from Acronis website two ISO files for ATI 2020: 20770 and 22510. Both work well on my old VAYO laptop where Windows 7, but touchpad does not work on the new HP laptop.

So, there are two questions:

1. Why touchpad worked well when rescue media was created by myself, and it was not working for ISO downloaded? Do you know how to enhance ISO image to make touchpad working?

2. Why does trial version makes rescue media is for restore only, while ISO files on your website do backup as well?

Please notice, there were screen resolution issues on my new 4k screen.

BR, Oleksandr

The key difference with the ISO images you downloaded is that these are based on a small Linux kernel OS which in turn has limited support for some devices, whereas the media you create within the application are based on Windows PE.

Unfortunately there are limitations for the rescue media when using ATI in trial mode.

See KB 2768: Trial version limitations of Acronis products for more information.

Hello Steve,

 

Finally I managed to made a backup with AcronisTrueImage2020_22510 (Linux) using keyboard only.

Yesterday I tried to restore this backup with USB made on my new Win10 laptop (trial version).

It took a while restoring the image and there was an error at the end of process.

Is it wrong to restore using Windows based rescue media if backup was made with Linux based rescue media?

What other reasons might have caused the error?

Unfortunately, Windows 10 disc is corrupted now. So, I cannot make another Win based rescue media.

Thanks for your support.

 

Best regards,

Oleksandr

Oleksandr, there should not be any significant differences in using either the Linux or WinPE versions of the rescue media to recover a backup image, the two should be interchangeable as far as is possible.

The key to understanding any issue that arises when using the rescue media is to always check the log file while still in the rescue environment, as these logs are volatile and disappear as soon as the computer is restarted.

With knowing what error was given at the end of the restore process, it is difficult to guess why this may have failed?

Thanks Steve.

Let me clarify a bit.

Originally it was the only disc on a drive, 1TB (950 GB in fact).

AcronisTrueImage2020_22510 (Linux) made a backup of it.

Then, I shrinked volume to 100 GB and created a new disc D of 850 GB.

Backup files were copied to the new disc D.

Yesterday, I restored disc C using files on disc D.

Is it possible that ATI recreated a one big disc C again, deleting disc D. As backup files were on Disc D, this caused the error yesterday?

 

Today, I have run a restore once more, storing backup files on rescue flash drive. Unfortunately, error again:

<?xml version="1.0" encoding="UTF-8" ?>
<log build="25700" product="Acronis True Image" task_name="Recover" uuid="C704DC57-9A0C-430C-AD3B-318654926194" version="24.6">
    <event code="0" id="1" level="2" message="Operation &quot;Recover&quot; started." module="100" time="1587769480" />
    <event code="8" id="2" level="4" line_tag="0xC75257350CE0FA0F" message="A format/resize error." module="534" time="1587769508">
        <field name="$module" type="TIdentifier">disk_backup_vsa64_650</field>
        <event code="13" id="3" level="4" line_tag="0x8AF64B2C0920F7ED" message="The file is corrupted." module="4" time="1587769508">
            <field name="$module" type="TIdentifier">disk_backup_vsa64_650</field>
            <event code="5003" id="4" level="4" line_tag="0xF76D5F471A5F4934" message="Data is corrupted: CRC mismatch or internal data structures mismatch" module="667" time="1587769508">
                <field name="function" type="TIdentifier">archive_stream_read_simple</field>
                <field name="path" type="TString">\\?\D:\_HP New\/20200329_C_New.tibx</field>
                <field name="$module" type="TIdentifier">disk_backup_vsa64_650</field>
            </event>
        </event>
    </event>
    <event code="252" id="5" level="4" message="Recover operation failed." module="100" time="1587769508" />
</log>

Oleksandr, if you have made a Disk backup and are restoring the same, then this should normally be done by selecting the top Disk entry and will wipe the whole target drive to perform the operation.

If you want to recover a Disk backup to only part of the target drive, then you will need to select and configure the size of each individual partition one by one for the restore.

When you created the backup image using the rescue media, what name did the file have, in particular, what extension was used?

Disk backups in ATI 2020 now must use .tibx file extension and not be named as .tib as will be found to be corrupt if doing so!  If the backup file is .tib, then change this to .tibx and try again.

Steve,
 

Writing "disc" I meant partition, as it's called in Windows.

Backup - Disc C, 950 GB

Restore - Disc C, 100 GB  (a new Disc D, 850 GB I wanted to be untouched)

What do you mean "the top Disk entry"?

 

As backup was made on Flash drive with FAT32, there were 8 files:

20200329_C_New.tibx

20200329_C_New-0001.tibx

....

20200329_C_New-0007.tibx

How many partitions are in your original 1TB source drive?

Normally Windows will have 3 partitions.

EFI System (UEFI) or System Reserved (Legacy) hidden / system partition.

Windows OS C: partition.

Windows Recovery hidden / system partition.

These are all needed for a successful recovery.

Normally when a disk recovery is performed, users should select just the entry at the top of the panel which is shown as 'Disk' - this will then select all the partitions below that level without the need for the user to worry about configuring the size of each partition.  Doing this would want to use the whole size of the target disk, not just the free 100GB space on that drive.

When recovering from your segmented .tibx file, you should select the first 20200329_C_New.tibx file and all further numbered files must be present.

There are also EFI System and Recovery partitions.

I made backups of three of them separately:

Windows disc C; EFI System; and Recovery.

I have tried to recover the "Windows disc C" only .

 

I did select the first file 20200329_C_New.tibx

Have you tried doing a Validation for the backup files when booted from the rescue media?

You can do this by right-clicking on the backup file after selecting Recovey then you will see the option for Validation.

The archive is corrupted, unfortunately. As far as I remember, I did option to check after backing up.

Two other archive files are successfully validated.

P.S. How did you make files as pictures above?

Attachment Size
536188-182399.JPG 148.86 KB
536188-182400.JPG 156.7 KB

The pictures were captured either when running the rescue media in a virtual machine or else using the MVP Custom WinPE media which includes other tools such as image capture, web browser and file manager.

No, Steve. The picture were made as a photo by iphone. No virtual machine neither Custom media - just HP Spectrum laptop. The USB flash drive was made by ATI 2020_25700 installed on this laptop.

Please find attached other pictures how ATI 2020 looks on 4k display.

Attachment Size
536215-182417.jpg 257.23 KB
536215-182420.jpg 124.72 KB
536215-182421.jpg 166.29 KB
536215-182424.jpg 325.18 KB
536215-182425.jpg 355.48 KB
536215-182428.jpg 142.01 KB
536215-182431.jpg 351.16 KB
536215-182433.jpg 188.38 KB
536215-182435.jpg 243.79 KB

Oleksandr, it was my own images / pictures that were captured from either a VM or when using the MVP Custom media.

What is the actual size of the target drive you are restoring to here?  Is it still the same 1TB drive you started from?

If it is still the 1TB drive, then I would recommend doing the following:

  1. If you have any data in the second D: partition on that drive, copy it to a different drive then reformat the drive to remove all partitions.
  2. Restore back the EFI System partition at the beginning of the drive, keeping it as the same size it was originally.
  3. Restore back the C: Windows partition to the remainder of the drive and check that this completes successfully.
  4. If the above are successful, then restart the computer and attempt to boot into Windows normally to see if you have got back to your starting point?
  5. If all is ok booting into Windows, then download a copy of the free MiniTool Partition Wizard software and use this to resize your Windows C: partition to the smaller size you are wanting to have, and create a new D: partition in the unallocated free space created.
    This will then just leave the Windows Recovery partition that you backed up previously.  Use the Partition Wizard tool again to create free space at the end of the drive for the Recovery partition, leaving it as unallocated space, then recover that partition to that area of the drive, which you should be able to do from within Windows using the ATI installed program.

First of all, thanks for replying on the weekend.

There are no any data neither on partition D nor partition C. As the backup file for partition C is corrupted, I cannot restore it.

In contrast, my current idea is to recover Recovery partition and then to restore Windows using a standard aproach. Now, this option is not available. I hope it will become available after restoring Recovery partition. What do you think?

Regarding pictures, my question was not how you captured, but how you presented it here on the forum as visible picture. In contrast, my pictures are presented as attachments.

BR, Oleksandr

Regarding pictures, my question was not how you captured, but how you presented it here on the forum as visible picture. In contrast, my pictures are presented as attachments.

 The icon seems to have gone missing but the option to insert images is still present!

In contrast, my current idea is to recover Recovery partition and then to restore Windows using a standard aproach. Now, this option is not available. I hope it will become available after restoring Recovery partition. What do you think?

You will still need the Windows install media unless you have a Windows System Image created by Windows Backup stored on another drive to use.

I thought Windows install files or Windows system image are stored on Recovery partition. Am I wrong?

Sorry but no, the recovery partition just provides tools to allow some repair actions.

OMG

What can I do if the backup file is corrupted? Either to check and somehow to fix the backup. Or to contact HP asking for media for my preinstalled Windows. Do you see any other options?

If your computer was activated successfully for Windows 10, then you can download the install media direct from the Microsoft support site at any time and reinstall it without any issues.  Activation is based on the hardware signature of the computer and will be recognised if that has not changed.  Disk drive changes do not affect activation, nor memory upgrades.

 

Hi Steve,

Thank you for providing the solution - it works. I installed Windows and it activated automatically.

However, there is an error of making backup if Device encryption is on (BitLocker is not available in Windows Home, but device ebcryption). When I turned encryption off then ATI creates and restores backups without any issues. But there are issues if encription is on. Have you heard already about it?

FYI, I have found that WinRE should be configured, while in my case it is not. WinRE might be caused by the fact that Kernel DMA Protection is Off and Virtualization-based-security is not enabled. While secure boot, TPM an Virtualization in BIOS are enabled.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

sm21 wrote:

However, there is an error of making backup if Device encryption is on (BitLocker is not available in Windows Home, but device ebcryption). When I turned encryption off then ATI creates and restores backups without any issues. But there are issues if encription is on. Have you heard already about it?

Hi! Basically, the limitations are listed in  1649: Compatibility of Acronis Backup Software with Encryption Software

Ekaterina wrote:
sm21 wrote:

However, there is an error of making backup if Device encryption is on (BitLocker is not available in Windows Home, but device ebcryption). When I turned encryption off then ATI creates and restores backups without any issues. But there are issues if encription is on. Have you heard already about it?

Hi! Basically, the limitations are listed in  1649: Compatibility of Acronis Backup Software with Encryption Software

 

Do you mean that ATI does not support Device encryption (Windows 10 Home)?

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Yes, there might be issues when creating a backup from within Windows. However, Acronis software can always create a raw (sector-by-sector) backup of an encrypted partition when booted from Acronis Bootable Rescue Media.

FYI, in my case ATI creates sector-by-sector backup of Windows 10 2004, but ATI does not see any disks/partitions of 1909 build.

Build 1909 will be in the Windows.old directory of the backup; it is not on a separate partition. Windows.old is not one of the default exclusions (although there are some exclusions that cannot be overridden and are not listed).

IanL-S wrote:

Build 1909 will be in the Windows.old directory of the backup; it is not on a separate partition. Windows.old is not one of the default exclusions (although there are some exclusions thІat cannot be overridden and are not listed).

Sorry, Ian, it must be misunderstanding.

I mean partition backup using bottable media (25700 Linux).

When I try to backup encrypted Win 1909, then no partitions are visible/available.

When I tried to backup encrypted Win 2004, then partitions ARE visible/available but process is slow (sector-by-sector?).

sm21 wrote:
I mean partition backup using bottable media (25700 Linux).

When I try to backup encrypted Win 1909, then no partitions are visible/available.

When I tried to backup encrypted Win 2004, then partitions ARE visible/available but process is slow (sector-by-sector?).

The Linux boot rescue media has no support for encrypted partitions or drives unless these have been unlocked or encryption removed first.  Sector-by-sector mode would always be used if ATI will allow the backup to proceed.

See KB 56619: Acronis True Image: compatibility with BitLocker for more information.

Hallo Steve!

I´m using ATI 2021 and have the same problem, when i am using "Survival Kit - Function"

I have found two recovery environment (part 1 and part 5) on my WIn10-System. 

What i have to do in this case, can I delete the part1, if have done the command "reagentc /info" an i can see, that part 5 is enable and in use!

thanks for your answer ans support

Hermann, if you have two separate recovery partitions, first look at the size of each partition to ensure that both are those created by Windows 10 (or an earlier version of Windows) and that one is not an OEM factory recovery partition of a much larger size (in GB's) that would be used to return the PC back to how it was shipped from the factory?

If you confirm that the second, inactive Recovery partition is from an earlier Windows install or upgrade, then that partition could be removed using a partition manager tool such as the free MiniTool Partition Wizard software.

I would recommend making a full disk backup before making changes to any partition.

Hallo Steve!

I have erased the inactive partition on hdd-0 and checked the status. Take a look to attachenment,admin01 and admin02

Then I tested the function "Survival Lit" by using ATI 2021, I am so sad, because  the problem is still here! (see attachment acronis_01, 02 and 03

Many thanks to you an all the best for the new year 2021. I hope, there is a issue for my problem in ATI

Attachment Size
563818-209682.jpg 34.75 KB
563818-209685.jpg 29 KB
563818-209688.jpg 73.29 KB
563818-209691.jpg 45.82 KB
563818-209694.jpg 54.14 KB

Hermann, there are several potential causes for this situation.

See forum topic: Media Rescue Builder geht nicht: Failed to mount the source .wim file - which covers some of the causes.

Other possible causes are:

Not running ATI from an Administrator account. (post #11 of above topic)

If the %Temp% folder has been relocated to another drive. (post #19 of above topic).

If a previous attempt to create media has left the %Temp% MntWIM Folder with files remaining and locked. (post #13 of above topic)

With the older 1709 Windows ADK having Secure Boot enabled caused an issue! (Not seen with later ADK versions). (post #16 of above topic)

See also forum topic: Can't Create Survival Kit - where alternative methods of achieving the same end result are discussed and which work!

These include:

Installing the Windows 10 ADK and using this to create the rescue media.

Note: You can create your own 'Survival Kit' by using a partition tool such as the free MiniTool Partition Wizard software to create a 2GB FAT32 partition at the start of your external drive and then allocating a Windows drive letter to that partition, i.e. drive 'S:', then using the normal Acronis Rescue Media Builder program to create media on drive 'S:'.

Using the MVP Custom PE Builder script to do the same as above.