Surely many admirers of modern computer games when installing them on a computer had a problem when the installation was about to end, and instead of a successful completion, the system displays a message like "Unarc.dll returned error code 6". What is the reason and how to fix this situation, and now it will be shown on the simplest examples.
Failure "Unarc.dll returned error code 6": what does this mean and what is the reason?
Before you begin to troubleshoot failures associated with this type of error, you should understand the causes of their occurrence. It is believed that in most cases they arise only when downloading from the Internet and using unofficial installation assemblies, which are commonly called Re-Pack.
Unfortunately, most often these are not “native” distributions of games, but user sets, in which some important components may be missing or damaged. In addition, as a rule, they are presented in the form of archives, with which many problems can also arise.
The decompressor program and two dynamic libraries, ISDone.dll and Unarc.dll, are responsible for installing the games. Error code 6 with different types of failure descriptions may indicate the most common causes of problems, among which are the following:
- damage to the downloaded archive with violation of integrity;
- creating an archive with a higher version of the archiver than used for unpacking;
- virus infection of archive contents;
- failures in dynamic components.
Errors of components of the installation distribution when installing games
The most unpleasant situation for a gamer is the appearance of an error at the final stage of the installation of the game. The installation course may already be 95-99% complete, but it is at this time that a critical failure occurs.
The reason for this is simple. Unarc.dll component error 6 is issued when unpacking and installing the last missing components is impossible. As a rule, these are archives, the extraction of the contents of which is carried out last. Official distributions have no problems just because the set has its own decompressor, the files are presented in the form of self-extracting archives, or during unpacking the installer contacts the archiver installed in the system, which corresponds to the modification of the program with which the archive was created initially.
Moreover, in the description you can often find the phrase "Unarc.dll returned error code 6. Error. File read operation failed ”or“ Decompression failed ”. The first description indicates that the installer cannot read (recognize) the file, the second indicates that the archiver cannot decompress the contents.
Unarc.dll returned error code 6: how to fix a crash in the simplest way
The first and easiest way to troubleshoot a damaged archive is to try downloading it to your computer again. It may well be that he simply did not load.
If the repeated download does not give a positive result, and the archiver in the error message mentions a failure to read CRC Check data , you should look for the intact (whole) archive on another resource and download it to the computer.
Troubleshoot archiver related issues
On the other hand, when the installer accesses the archiver installed in the system, or the user extracts the contents of the archive during the installation process on his own, the situation with the warning that Unarc.dll returned error code 6 can also occur.
Most often, the problem is that the version of the compression program is lower than the one with which the archive was packaged. The simplest example is an attempt to unpack archives created using WinRAR of the fifth modification, a similar application, but version 4. The way out of this situation is to install the necessary version of the archiver or replace it with another equivalent one (WinZIP, 7-Zip, etc.) .
By the way, regarding the packaging of the archive with the 7-Zip program, sometimes non-standard methods of enhanced compression can be applied, which WinZIP and WinRAR do not support. In this case, the extraction of the contents must be done by the original application.
Viral infection problems
Viral exposure should also not be underestimated. The archive itself and the dynamic libraries involved in the installation process of the game may also be infected.
In the first case, the archive should be checked for viruses before unpacking, in the second case, a comprehensive scan of the entire computer system should be performed, activating in-depth analysis.
Correction of failures of dynamic components involved in the installation process
Finally, the message “Unarc.dll returned error code 6” may also appear in the event of a failure of the dynamic components themselves, due to critical impact on the operating system (incorrect shutdown, voltage drops, system component errors, etc.).
For such cases, there is also a solution. Since it is impossible to fix such failures manually (even when integrating original libraries copied from another computer with the same OS or downloaded from the Internet into the system), they should be repaired. We do not consider the rollback of the system, because the components could have been damaged for a long time, and there is no checkpoint for restoration.
You can check the system with the sfc scannow command, which is entered in the corresponding console. The easiest way is to use special utilities like DLL Suite or Microsoft Fix It !, which will do all the operations automatically without user intervention.
Conclusion
In conclusion of the topic, it remains to add that the most frequent failures are precisely errors of archive data, therefore it is better not to use all sorts of re-packs, but to install your favorite or favorite games using official distributions. Only in this case can we guarantee that the installation will be successful and that there will be no problems during the installation.
Just in case, archiver programs should also be kept up-to-date, because new versions, with the help of which archives are created, suggest more powerful compression using updated algorithms, and outdated modifications such technologies may not support.
Finally, issues related to damage to RAM slots and any other physical failures were not considered here.