Unarc.dll returned error code 6: how to fix it?

Surely many fans of modern computer games when installing them on the computer faced a problem when the installation is about to end, and instead of successfully completing the system gives a message like "Unarc.dll returned error code 6". What is the reason and how to correct this situation, now and will be shown on the simplest examples.

"Unarc.dll failed to return error code 6": what does this mean and why?

Before you begin to fix the failures associated with this type of error, you need to understand the reasons for their occurrence. It is believed that in most cases they arise only when downloading from the Internet and using unofficial installation assemblies, which are called Re-Pack.

Unfortunately, most often these are not "native" game distributions, but custom 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 too many problems can arise.

For the installation of games is responsible for the decompressor and two dynamic libraries - ISDone.dll and Unarc.dll. Error code 6 with different types of fault description may indicate the most common causes of the problem, among which are the following:

• Damage to the downloaded archive in violation of integrity;
• The creation of an archive with a higher version of the archiver than the one used for unpacking;
• Virus infection of the contents of the archive;
• Failures in dynamic components.

Errors of the components of the installation distribution when installing games

The most unpleasant situation for a gamer is the appearance of a mistake in the final stage of the installation of the game. The progress of the installation can already be performed at 95-99%, but it is at this time and there is a critical failure.

The reason for this is trite is simple. The Unarc.dll component generates error 6 when the missing components are unpacked and installed. As a rule, these are the archives, the extraction of which is done last. In official distributions there are no problems only because the set has its own decompressor, the files are represented in the form of self-extracting archives, or during the unpacking process the installer refers to the archiver installed in the system that corresponds to the modification of the program with which the archive was originally created.

In this case, you can often find phrases in the description "Unarc.dll returned error code 6. Error. File read operation failed "or" Decompression failed ". The first description indicates that the installer can not read (recognize) the file, the second indicates that the archiver can not decompress the content.

Unarc.dll returned error code 6: how to fix the crash in the simplest way

The first and most simple way to troubleshoot the failure of the archive is to try to download it to the computer again. It may very well be that he simply did not download.

If the re-download does not give a positive result, and the archiver in the error message mentions CRC Check reading , you should search for an undamaged (one-piece) archive on another resource and download it to the computer.

Troubleshooting archivers

On the other hand, when the installer accesses the archiver installed in the system, or the user extracts the archive contents during the installation itself, the situation with the warning that Unarc.dll returned error code 6 can also occur.

The most common problem is that the version of the compression program is lower than the one that the archive was packed with. The easiest example is an attempt to unpack archives created with WinRAR of the fifth modification, similar to the application, but version 4. The solution to this situation is to install the required version of the archiver or replace it with another equivalent (WinZIP, 7-Zip, etc.) .

By the way, as for archive packing with the 7-Zip program, non-standard methods of enhanced compression can sometimes be used, which WinZIP and WinRAR do not support. In this case, the content must be extracted by the original application.

Problems of viral infection

Viral effects should also not be underestimated. The archive itself and the dynamic libraries involved in the process of installing the game can be infected.

In the first case, before unpacking, you should check for the viruses the archive you need, in the second - perform a comprehensive scan of the entire computer system, 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 a critical impact on the operating system (incorrect shutdown, voltage drops, system component errors, etc.).

For such cases, too, there is a solution. Since it is impossible to manually fix such failures (even when integrating the original libraries copied from another computer with a similar OS or downloaded from the Internet), they should be restored. We do not consider the rollback of the system, because the components could have been damaged for a long time, and there is no control point for recovery.

You can check the system with the sfc scannow command, which is entered in the appropriate console. The easiest way to use special utilities like DLL Suite or Microsoft Fix It !, which will do all the operations automatically without user intervention.

Conclusion

In conclusion, it remains to add that the most frequent failures are the errors of the archive data, so it's better not to use any kind of re-packs, but to install favorite or favorite games with the help of official distributions. Only in this case it is possible to give a guarantee that the installation will be successful, and during the installation there will be no problems.

Just in case, the archiver programs should also be kept up to date, as the new versions, with which the archives are created, suggest more powerful compression using updated algorithms, and older technologies may not support such technologies.

Finally, there were not considered issues related to damage to the memory slots, and any other physical disruptions.