Log analyzing
The most part of possible problems could be detected in RMB log, which shows all steps of the whole process.
To find the encountered error in the RMB log, follow instructions below:
- Open the “rmbengine.log” (By default, the file located in this folder:C:\Program Files\Paragon Software\[Product name]\program )
- Find particular error code or external tools problem filefolder.
- Find the error’s description and the possible solution in the article below.
External Utilities Based
Errors 6,15, 23, 24, 25, 26, 27, 28, 29, 30, 31, 35, 45, 48, 53
The most common are errors connected with processes, when RMB Wizard bases on external utilities such as WIM tools or WAIK/ADK tools. In this case, the error cannot be predicted because it depends on utility version, settings and other conflicts.
WIM tools (Errors 15, 23, 24, 25, 26, 27, 28, 29, 30, 31, 35, 53):
The most part of problems with WIM is caused by permissions conflict. It required having admins permissions to access WIM. Also The WIM could be effected or corrupted.
Possible reasons of WIM corruption:
- Corrupt Windows registry keys associated with Winre.wim/Microsoft Windows.
- Virus or malware infection that has corrupted the Winre.wim file or related Microsoft Windows program files.
- Another program maliciously or mistakenly deleted Winre.wim-related files.
- Another program is in conflict with Microsoft Windows and its shared referenced files.
- Corrupt download or incomplete installation of Microsoft Windows software.
The path to WIM image is specified in RMBInit.xml “source-image” line. By default, WIM locates in C:Recovery hidden folder.
Possible Solutions:
- The easiest workaround is to use WAIK/ADK tools.
- Scan for virus infection.
- Disable Antivirus and other software protection.
- Boot in the safe mode in order to prevent system or software file block.
- Check disk for errors and system files integrity
WAIKADK tools (Errors 6, 45, 48, 53):
These tools are specifically developed by Microsoft for imaging purposes so it is highly recommended to prepare recovery media using WAIKADK. The disadvantage is that it is required to download about 4GB from Microsoft web site but it surely simplifies all the process.
WAIKADK is faultless in general but it is very important to use appropriate version for particular Windows OS. It is possible to obtain it clicking «Download WAIKADK» button in RMB.
Possible reasons of WAIK/ADK problems:
- The version of tools are not appropriate for Windows version.
- The path to the WAIKADK tools is not correct.
- Installation is corrupted.
It is possible to set YesNoForce parameter for searching WAIK/ADK in OS. In RMBInit.xml “SearchForWAIK” line.
Possible Solutions
- Make sure the WAIK/ADK version matches the Windows version.
- Delete and download appropriate WAIK/ADK.
- Scan for virus infection.
- Disable Antivirus and other software protection.
- Boot in the safe mode in order to prevent system or software file block.
- Check disk for errors and system files integrity.
Files and folders processing
Errors 1, 2, 3, 4, 5, 10,13, 18, 19, 20, 21, 22, 32, 33, 34, 35, 37, 38, 39, 40, 41, 42, 43, 44, 46, 47, 49, 50, 51, 53, 60, 64, 65, 66, 67, 68, 69, 70
These errors appear when some files or folders cannot be created/deleted/opened or there is a problem with files content in installation.
Possible reasons for files and folders processing problems:
- Some configuration or .dll files in program directory are corrupted or missing.
- Program files, folders or system resources are blocked.
- Not enough permissions to modify files and registry.
Detecting problem in settings:
The path to product is specified in RMBInit.xml “product-path” line.
Possible Solutions:
- Run RMB with administrator permissions.
- Reinstall the RMB to the folder with admins permissions.
- Check disk for errors and system files integrity.
- Disable Antivirus and other software protection. Make sure nothing blocks program and TEMP folders.
Device accessing
Errors 36, 52, 53, 54, 55, 56, 57, 59, 60, 61, 62, 63, 64, 65, 66, 71
These problems usually appear when device is locked or not suitable for operation.
Possible reasons of device accessing issues:
- Device file system is locked by another process and can’t be handled.
- Device can’t be mounted – can’t assign drive letter or unmounted – locked.
- Device is not suitable for RMB recovery media.
Possible Solutions:
- Format USB flash to FAT32.
- Mount device volume to another letter.
- Disable Antivirus and other software protection.
- Make sure no software uses the USB flash. Usually problem could be caused by monitoring and scanning software.
- Check if you have necessary readwrite permissions to access the device.
Detailed Errors Guide:
If the solutions mentioned above didn’t solve the issue or you may want to familiarize with the full description of the encountered error, please open this file and find your error description: Error code guide
RMB: RMB errors
Tags: error, WinPE
Loading...