1. Open control panel -> Program files, locate Macrium Reflect and right click.
2. Select the Change option. And then click on Remove.
3. Check "Remove all user generated files and log files" and click on Remove
This FAQ covers some of the commonly encountered queries regarding transitioning from Macrium Reflect v4 to v5.
Backup aborted! - Failed to create volume snapshot error. Result Code: 0x80042301
The windows snapshot component VSS will fail if a disk with a non standard sector size is attached to your system, even if this disk is either being backed up or used to store the image files. This can be an internal disk or one connected by USB or eSata. These disks are fortunately rare, and are typically found only in sizes of 1TB or above.
The extended VSS error information will be reported as below for version 5. See image, note the result code may be different, but the extended error will always be ...
ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed.
- Returned HRESULT = 0x80042301
- Error text: VSS_E_BAD_STATE
You will see the following error, note the result code may be different.
To get the extended VSS information, you need to run the backup from a VBScript file? Right on your XML definition andselect 'Generate VBScript'. Accept the defaults and run the VBScriptsource. To run VBScript, click the VBSCript tab, right click on the fileand select 'Execute'. Once run, a detailed log file will be created inthe same directory as the VBScript source. The log file name will be'log-<date>-<time>.txt'. Open the log file with notepad or similar and search for the following text as before ...
ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed.
- Returned HRESULT = 0x80042301
- Error text: VSS_E_BAD_STATE
Run 'System Information' ('All Programs' > 'Accessories' > 'System Tools' > 'System Information').
Expand the Components->Storage->Disks node, and scroll down the list of disks, looking for any that have a Bytes/Sector value not equal to 512.
Unfortunately, until Microsoft fix this issue, the only option is to remove this disk from your system. Read this
Article for general information regarding Microsoft support for non-standard sector sizes.
Note: Some Western Digital disks can be formatted for "Windows Vista Compatibility" using the supplied software. This enables 512e in the firmware and adds support for VSS.
Feature | Standard | Pro | Server |
---|---|---|---|
Disk Imaging | ![]() | ![]() | ![]() |
Disk Cloning | ![]() | ![]() | ![]() |
Access images in Windows Explorer | ![]() | ![]() | ![]() |
Schedule backups | ![]() | ![]() | ![]() |
Linux Rescue CD | ![]() | ![]() | ![]() |
Windows PE 3 Rescue Media (RAID support) | ![]() | ![]() | ![]() |
XP / Vista / 7 and WHS compatibility | ![]() | ![]() | ![]() |
File and Folder backup | ![]() | ![]() | ![]() |
Email notification of backup status | ![]() | ![]() | ![]() |
Differential and Incremental backups | ![]() | ![]() | ![]() |
Disk Space Management | ![]() | ![]() | ![]() |
Backup scripting | ![]() | ![]() | ![]() |
Recovery from Windows boot menu | ![]() | ![]() | ![]() |
Password protection and encryption | ![]() | ![]() | ![]() |
Support for GPT and dynamic disks* | ![]() | ![]() | |
Restore to dissimilar hardware with ReDeploy | ![]() | ![]() | |
Windows Server 2003/2008/2011 compatibility | ![]() | ||
Windows Server cross-hardware restore | ![]() | ||
Integrated Windows event logging | ![]() | ||
![]() | ![]() | ![]() |
*To identify if you require dynamic or GPT disk support, read this.
Macrium Reflect uses the Windows Volume Shadow Services (VSS) to take snapshots of the file system prior to taking images and backing up files. As a result of this, Macrium Reflect is not supported on Windows operating systems prior to Windows XP SP1 and Server 2003 since they do not incorporate this service.
Use the table below to see possible solutions to common VSS errors:
VSS Error | Description |
0x8000fff | |
0x80042306 | |
0x8004230f | |
0x80042318 | |
0x8004231f | |
0x80042301 | |
0x80042317 | |
0x80000ffff | |
0x800423f3 |
This article explains how to image and recover a disk that has developed bad sectors. A disk that has bad sectors is permanently damaged and, if the bad sectors were in use by the file system, it is very likely that the data contained in the damaged area is unrecoverable.
This may be a sign that your hard drive is coming to the end of its life, though, it is still possible to manage the situation and create an Image whichcan be restored or used to mount and copy files and folders.
For more information on bad sectors please see this Wikipedia article http://en.wikipedia.org/wiki/Bad_sector
If a bad sector is encountered during image creation then you will receive the following error in your backup log:
Backup aborted! Unable to read from disk - Error Code 23 - Data error (cyclic redundancy check)
Note: This is considered a fatal condition because your data cannot be read and the image will abort.
The first step should be to run 'chkdsk' on the problem drive to reallocate file system clusters to undamaged disk sectors.
Run 'chkdsk c: /r' from a command prompt. Replace 'c:' with the appropriate drive letter.Note: The '/r' switch is important and will cause the entire file system to be checked for bad sectors. This will require a reboot to complete and may take some time.
To open a command prompt click 'Start' > 'All Programs' > 'Accessories' and select 'Command Prompt'. In Vista/7 right click and select 'Run as Administrator'.Enter 'Y' if you receive the 'schedule this volume..' message.
The above will map out any bad sectors in use by the file system. After doing this immediately create an Image of your drive. This will ensure that all file system clusters are located on good sectors. It's important to realize that you have already lost data if clusters are relocated, as the data contained in them is unrecoverable. You should consider replacing your disk.
Note: If you still receive 'Error Code 23' in your log after running chkdsk then run chkdsk repeatedly until an image can be created without error.
A list of bad clusters is stored in the file system and is copied when you create an Image and when you restore the Image. After restoring an Image to a new disk, if you are running Windows Vista or Windows 7, then run 'chkdsk c: /b'which will re-evaluate all the bad clusters restored on your drive andremove non-faulty clusters from the list. If you are running Windows XPthen if you boot into the Windows PE rescue CD you can run the samecommand from there. /b only works with NTFS volumes.
If you are unable to successfully reallocate file system clusters by running chkdsk then you can force Macrium Reflect to continue on Error 23.
Take the 'Other tasks' > 'Edit defaults' > 'Advanced' option and select 'Ignore bad sectors', click 'OK'. Images will now complete:
Note: The bad sectors will be reported in the Image log, e.g:
Read Error: Bad sector found in cluster 2353222
Read Error: Bad sector found in cluster 2353223
This article shows you how to use VBScript to delete differential Images in a backup set. This enablesyou to retain a specified number of recent differential Images, this tutorial also applies to differential file and folder backups.
In the following example we will generate a VBScript source file that creates a differential backup (Image or file and folder)and then delete differentials in the same set retaining the '4' most recent differential images.
Select 'Backup Definition Files' tab, then Right click on your Backup Definition File,and select 'Generate a VBScript File'.
In the next dialog accept the defaults and click on 'OK', although you can make the File Name more descriptive of the drives/folders being backed up if needed.
Select the VBScript tab, right click on the new VBScriptlist entry and select 'Edit'. Notepad will open.
It is strongly suggested you do not select Word Wrap inNotepad, it is easier to edit without selecting Word Wrap
All the following code inGreen willneed to be copied to Notepad as per the instructions given:
After the line:
ExitCode = Backup ("""C:\Program Files\Macrium\Reflect\Reflect.exe"" -e -w <BACKUP_TYPE> ""PATH TO XML file""")
Copy and paste the following code:
Note: The number '4' above is the number of recent differential files you want to keep in the backup set,you can change this number
Example of Paste as indicated in following dialog:
At the very *end* of the file in notepad copy and paste the following code:
Save the file in notepad: File > Save and close notepad.
You can run VBScript files just like XML filesand you can schedule the VBScript file to run by right clicking on the VBScript file: Select 'Run Now' or 'Schedule' (more detail in step 6 if needed). If you have previously scheduled XML files running the Differential, this XML scheduling can now be deleted if it is to be replaced by the scheduled VBScript file; make sure you only delete an XML file under the Scheduled Backups tab and not under the Backup Definition Files tab.
If you want to run backups while retaining a limited number of Differentials you must nowrun the VBScript and not XML definition files. The following two examples aim to get you started with this.
Select the 'VBScript Files' tab and right click the VBScript file name, you wish to run, and fromthe 'Run Now' option select Differential. The Differential backup should now run:
You will note that the details of this task have been addedto the main pain of the application under the 'Scheduled Backups' tab.
Migrating to a new machine due to hardware failure or planned upgrade such as a new motherboard etc.
Moving between a physical and a virtual machine (P2V / V2P ).
Changing a non-raid to a raid installation or legacy SATA to AHCI SATA
There are various aspects of the windows boot processes that will typically causea boot failure after significant changes to the hardware. The purpose of ReDeploy isto attempt to overcome these issues enabling a Windows installation to run on new hardware.
The discovery of hardware and association with a matching device drivers is atime consuming process. It must be undertaken when windows is being installed butthen is skipped during a normal windows boot to make the boot delay acceptable.
Early in the boot process, the boot loader loads the windows kernel (the coreof the operating system) and selected “critical” drivers required to get windowsup and running. If the new hardware configuration requires a new driver to readthe disk containing the operating system then windows will fail to boot.
Once the kernel and the critical drivers are loaded, the kernel is started. Thekernel and its associated HAL need to match the motherboard for best enabling. A driveris optionally loaded to handle specific cpu features. Again, for a stable system,this driver needs to match the hardware – in this case, the cpu model.
ReDeploy is designed to detect changes to these critical system features,locate relevant drivers and inject them into your windows operating system toenable it to boot.
You will need to run ReDeploy from the Windows PE Reflect rescue CD. Thisallows the new hardware to be detected and the configuration of the windowssystem modified to enable it to boot.
ReDeploy is designed make the complex process of getting an offline windows operatingsystem running as easy and intuitive as possible. What it will not do is install thecomplete driver set for the new hardware. You will be able to complete the driver installationfor devices such as network and graphics adaptors once your windows installation hasbooted on your new hardware.
![]() | Note: Image deployment to multiple PCs requires a deployment license for each PC deployed. Please see here for information on purchasing deployment licenses. If you deploy an image to a different PC then you should make sure your installed software, including Windows and Macrium Reflect is suitably licensed for the new PC. |
Workstation | Server | |
v5 Professional | x | |
v5 Server | x | x |
The Standard edition of Macrium Reflect v5 does not contain ReDeploy, neither do any of the 30 day trial editions.
![]() | Note: ReDeploy will modify an existing offline operating system to work with new hardware. You should restore your system image to the PC being deployed before running ReDeploy. There is no need to reboot your PC after restoring an Image and before you run ReDeploy. |
ReDeploy will now seek drivers for all discovered mass storage devices and a list will be displayed with details to the right.
For each mass storage device, there are three possibilities:
The linux CD is a compact and efficient rescue environment to restore all Windowsoperating systems. It will only enable your to restore your imaged partitionsto exactly the same size and position as they were at the time the imagewas created.
If you require more flexible imaging and restore options or your hardware is notsupported then use the Windows PE rescue environment. Note, RAID systems and disks attached via usb3 interfacesare not supported in this rescue environment.
It operates as a wizard, guiding you through locating an image, selecting what to restore and where to restore it to.
First a Macrium image file must be located.
Navigate to the folder that contains the image to be restored in the left hand pane. Possible locations are network attached disks, CDs or DVDs, internal hard disks or those attached via USB or eSata.
The backup list shows all backup images in the selected folder and the pane below shows the partitions included in the image.
Highlight particular backup image that you want to restore, the contents of which will be revealed in the lower right pane. If you have an incremental/differential set, chose the last image in the set, unless you wish to restore to an earlier point in time.
In the case that your images are multi-part images – typical for images stored on a FAT formatted device such as a USB hard disk or on CD/DVD recordable media, locate the last image in the set.
Note that the drive letters presented in the left pane may be different from those that Windows uses. If you wish to eject a CD, double click on the CD icon.
Select a network adaptor from the list and view or change the IP addressand network parameters if incorrect.
Note: if there are no adaptors listed, then the Linux rescue disk doeshave support for your network adaptor. In this case, consider a windows PE rescue disk.
The "Set" button applies any configuration changes, and "Get address" attempts to acquires a new address via DHCP. This will have been attempted at boot time, but may need to be invoked manually, for example where a network lead was not connected at boot time.
The Linux CD supports restoration from network attached storage suchas a shared folder on another computer or network attached disk. Networkbrowsing is not implemented, so you need to know the network name or IPaddress of the computer or NAS device that you wish to connect to.Once you have located the image, you can proceed to next page.
You are now prompted to chose which disk to restore using the drop downlist and then which partitions to restore. By default all partitions includedin the image will be selected.
Image files can contain images of multiple disks, each containing oneor more partitions.You are presented with a summary of the restore operation that you haveconfigured.
If you are happy to proceed, click Restore.
In the case that you have selected a multi-part image on a differentdisk such as a CD or DVD, you will be prompted to insert the disk containingthe first and then subsequent image files as they are required.
Check the disk for possible errors
Error
ERROR: Selected writer 'SPSearch4 VSS Writer' is in failed state!
Backup aborted! - Failed To Create Volume Snapshot. Result Code: 0x8000ffff
The Following errors may be found in the server application log:
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation Search
Event ID: 70
Task Category: Gatherer
Level: Error
User: CONTOSO\spsearch
Computer: CONTOSO-SERVER.contoso.local
Description:
The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.
Log Name: Application
Source: Microsoft-Windows-Backup
Event ID: 521
Level: Error
User: SYSTEM
Description:
The backup operation that started at '?2011?-?07?-?06T02:12:07.198000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
You can also run the following commands to determine if you need to complete the update process with PSCONFIG:
In order to update the SharePoint databases, you must manually run the PSconfig utility. To run the utility:
1. Open an Administrative command prompt.
2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the machine. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.
Original source: http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx
External disks can be configured either for Performance or for Quick Removal. When configured for Quick Removal, Windows will disable write caching to the disk thereby slowing down throughput. All writes will go direct to the disk and throughput IO collisions can occur. It is recommended that external disks are configured for Performance when you encounter the 1117 error code. Follow these steps to configure the disk:
After restarting your computer we recommend trying another backup to see if this has resolved your issue.
Enable Write Caching
You make also want to enable write caching, This solution is used exclusively for backup operations.
Please try another backup when the above steps have been performed.
By their very nature, anti-virus and registry cleaner software may interfere with the normal operation of legitimately installed applications. This article outlines some of the issues this causes with Macrium Reflect and provides some solutions.
Imaging
When imagining your disk, Macrium Reflect performs a number of actions that some anti-virus software may think of as being malicious. For example, when imaging or cloning your disk Macrium Reflect reads certain parts of the disk that are not generally accessed by every day applications. Reflect also writes very large files (the image file) which again is sometimes seen as being malicious by some anti-virus software. Specifically, it is often the case that imaging a drive will lock up or abort when 99% complete.
Performance
Anti-virus software is also sometimes responsible for significant degradation in the speed of imaging and restoration since the anti-virus process is constantly applying its rules to everything that Macrium Reflect and the other processes running on your PC are doing.
Downloading
When downloading a file onto your PC, before it has been written to your disk prior to execution, anti-virus software may exclusively lock file and scan it for viruses. Unfortunately, this may result in corruption of the download.Solution
You should add the Macrium Reflect executable to the white list or trusted zone of your anti-virus software. The executable that runs Macrium Reflect is Reflect.exe and is generally located in C:\Program Files\Macrium\Reflect. We also recommend that you should exclude the scanning of .MRIMG and .MRBAK files.
Turning the security level to a lower setting or off completely may also have the desired effect. In testing we have found that with some products, the only way to proceed has been to remove the anti-virus software from the PC entirely.
It is perhaps an ironic paradox that in their pursuit of "total security" some anti-virus programs have started to exhibit virus-like behaviour by stopping applications performing legitimate actions and compromising your PC by corrupting the data they seek to protect and reducing its performance.
Overview
The registry is a key component of Microsoft Windows and provides an indexed store of values. Any application running on Windows may use the registry although there are certain guidelines on it's correct use. Although most application vendors conform to these guidelines, there is a perceived belief that a large registry contributes to the slow running of a PC. To tackle this problem, there are products that claim to make your computer faster by cleaning the registry and removing data no longer in use. There is no way of determining if a value stored in the registry is in use so the cleaners make a best-guess based on studying commonly used Windows applications and how they affect the registry.
Problems
Since Macrium Reflect uses the registry, cleaners that are unaware of Macrium Reflect may see the keys it uses as reduntant and remove them accordingly. The result of doing so can cause unpredictable behaviour by Macrium Reflect, such as your key appearing to become expired and being unable to mount images.
Solution
We do not recommend the use of Registry Cleaners. The Windows registry is exceedingly complex and used by every aspect of your PC.
We have had a number of issues where users have been unable to uninstall Macrium Reflect. This may be caused by software that deletes the files on your PC that Macrium uses to safely uninstall itself. If these files are removed, it no longer becomes possible to uninstall Reflect. Generally these files reside in folder 'c:\windows\installer' with extension '.msi'. Deleting any files from this folder should be avoided as this will likely cause future problems when upgrading or uninstalling.
Solution
We do not recommend the use of uninstaller programs. Windows provides an entirely adequate framework for installing and uninstalling software and problems in this area are inevitably caused by the applications being installed, not by Windows. If you have issues uninstalling Macrium Reflect please contact support.
If you are experiencing a Blue screen of death (BSOD) or a sudden reboot during a backup on Windows XP or 2003, then consider the following solution.This applies to any software that engages VSS, not just Macrium Refect.
A BSOD is the error message resulting from a kernel mode crash. These are typically caused by either faulty drivers or failing hardware. Unfortunately, Windows is often configured to reboot after crash so the BSOD message is hidden. If your machine suddenly and unexpectedly reboots, this is typically due to a kernel mode crash. You can either configure your machine not to reboot on a BSOD (see here [support.microsoft.com]) or use the free tool blue screen view [www.nirsoft.net] to display previous BSOD errors.Macrium Software takes customer support seriously and this article describes duration and nature of that support. The support for the current version 5 is the same as that for the previous version 4. There has been no downgrading of support, we pride ourselves on the support given.
There are 4 parts to this article, click on the appropriate link:
Support, Updates and Upgrades for v4 & v5 editions of Macrium Reflect
Clarifying the License Duration and Support for the different Macrium Products
How to contact Macrium Support
Links to other sources of Help
When you purchase the v4 Standard edition or v5 Standard/Professional/Server editions of Macrium Reflect, Macrium Support is provided free for one year or until a major release (for example 4.x to 5.x) whichever is the longer. You are guaranteed at least one year of free support. To maintain support after this time you are required to upgrade to the latest version of Macrium Reflect (currently version 5).
Macrium Support is by e-mail and support forum access. Many problems can be solved by finding solutions within the Forum, Knowledge base (KB)Tutorials, Help Tutorials and YouTube videos; these are instant solutions rather than wait for Macrium Support to respond (usually within 24 hours during weekdays). More on how to get support below.
Same version updates (4.x to 4.x or 5.x to 5.x) are free for life.
Major upgrades (for example 4.x to 5.x) are chargeable but with an upgrade discount.
Please note that e-mail Macrium Support is only available for the purchased editions and the full 30 day trial; also only those who purchase can post questions in the Forum.
The free edition is not supported although users do have access to view the Forum, Knowledge Base (KB) Tutorials, Help Tutorials and YouTube videos; but cannot post questions in the Forum.
Each Macrium Reflect license key, for v4 Standard edition or v5 Standard/Professional/Server editions, is for onecomputer. You may only transfer the license key to another computer for legitimate upgrade/replacement purposes.
When you purchase the v4 Standard edition or v5 Standard/Professional/Server editions you have the software licenses forlife, there is no annual fee to pay. The exception is when you upgrade, when your old edition is replaced by the upgradededition and your old license key becomes invalid having been replaced by the new upgrade license key. The supportassociated with these products is describedabovein the first part of this article.
These two license types run alongside v4 Standard edition and v5 Standard/Professional/Server editions. Theselicenses are mainly used by IT support departments of companies and IT organisations. The Technicians license lastsfor one year after which it can be renewed; and each Deployment license allows 10 deployments per license, you can purchaseadditional Deployment licenses.
Macrium Support for the Technicians license is available while the Technicians license is valid. This is normally 1 year from the date the Technicians license is purchased or renewed.
There are 2 versions of the Technicians license - Standard and Enterprise: both allow use on unlimited workstations but the Standard edition can only be used on up to 10 Servers whilst the Enterprise edition can be used on unlimited Servers.
A recent change to purchasing a Technicians license means you now get supplied a v5 Server edition of Macrium Reflect with the Technicians license. This Macrium Reflect server license supplied with the Technicians license is different from a normal Server license in that it includes 'upgrade protection'. As long as the technicians license is renewed annually then all future upgrades of this license are free (for example v5 to v6 etc..).
Support for the Deployment license is associated with the full license which is being used to deploy the backups. If you have a previous version of Macrium Reflect where support has expired it is strongly recommended that you upgrade. If you purchase a Deployment license where your associated full license support has expired then you will only get support within 30 days of the purchase date of the Deployment license.
For more information on Technicians and Deployment licenses see related links below.
The following solutions are available:
Ultimately it is advisable, and highly desirable, to get VSS working correctly on the computer that you are attempting to backup. Please see the VSS Errors Category for further assistance with getting VSS working.
System Disk/Data Partition Encryption | File based virtual disk | |
Windows/Reflect | Encrypted partitions are unencrypted on the fly, so applications, including Reflect will be presented will an unencrypted partition. | The mounted virtual disk will not be recognised as a disk by Reflect. However, the virtual disk file will be imaged correctly when the containing partition is imaged, or it is included in a file and folder backup. Note: You should unmount the virtual disk before the backup. |
Image file contents | By default, unencrypted - use Reflect encryption. If this image is restored, the restored partitions will be unencrypted. | The virtual disk file is stored in its encrypted state. There is no need to use Reflect encryption. |
Rescue CD | Encrypted partitions will be displayed unformatted. It is not possible to navigate the contents. They can be imaged, only in 'exact copy' mode. The fix boot problems and redeploy functions will not work. | It is not possible to mount virtual disk files with the rescue CD. However, they can be restored from a backup, if they become corrupted. |
Booting off a restored system partition | If you restore a system partition using the rescue CD, it will be restored un-encrypted. This is likely to lead to a non-bootable system as the bootloader is configured for an encrypted partition. You can however use the Macrium CD to restore the Windows bootloader, meaning you will have a bootable unencrypted partition. If you wish to image an encrypted partition that will be bootable on restore, you must take the image using the rescue CD. This can only be do in 'exact copy' mode, so will be slower than a normal image and will result in a larger file. | n/a |
Product: | Reflect V5 |
PGP Whole Disk Encryption | Compatible |
TrueCrypt system disk encryption | Compatible |
dism /mount-wim /wimfile:C:\Program Files\Windows AIK\Tools\PETools\x86\custom.wim /index:1 /MountDir:C:\boot\macrium\WAIKFiles\mount
xcopy /i c:\TrueCrypt "C:\boot\macrium\WAIKFiles\mount\Program Files\TrueCrypt"
dism /Unmount-Wim /MountDir:C:\boot\macrium\WAIKFiles\mount /Commit
"x:\program files\truecrypt\truecrypt.exe"
This solution only works if you are have the Microsoft WAIK installed. It will be installed automatically if you create a v5 custom PE rescue CD.
First configure Reflect to use a custom base wim (see here).
Then mount your wim, this will take a couple of minutes. Ensure you use the path to your custom wim.dism /mount-wim /wimfile:C:\Program Files\Windows AIK\Tools\PETools\x86\custom.wim /index:1 /MountDir:C:\boot\macrium\WAIKFiles\mount
Then add the wmi package to your wim.
dism /image:c:\winpe_x86\mount /add-package/packagepath:"c:\Program Files\WindowsAIK\Tools\PETools\x86\WinPE_FPs\WinPE-WMI.cab"
Then unmount your your wim, this will take a couple of minutes.
dism /Unmount-Wim /MountDir:C:\boot\macrium\WAIKFiles\mount /Commit
manage-bde -unlock e: -recoverypassword <key found in bk file>Once unlocked, the partition appears in Reflect as a standard volume andcan be imaged and browsed as such. If an image is restored, the volume becomes a standard(un-encrypted) volume. It can be re-encrypted when you boot back into windows.