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

The global problem of many gamers when installing a game is the error when unpacking Unarc.dll, which causes the installation to be interrupted almost at the initial stage. What is this failure and how to fix it, now we'll see.

Unarc.dll returned error code 12: what would that mean?

Let's start with the interpretation of the failure itself. Since we have the error when unpacking Unarc.dll, it is logical to assume that this is due to the decompression of the installation distribution. This is partly true.

However, the error 12 of Unarc.dll mainly occurs when installing non-official distributions that are delivered in an unpacked form, and the so-called manually repacked repack, which often includes many additional or unofficial patches, which, in fact, must be unpacked In the process of installing the main game files.

Multiple variants of the causes of the failure

Now let's look at a few specific cases when an installation error occurs. Unarc.dll in this case has a link to another dynamic library ISDone.dll. Without going into technical details, we will define the two most common situations.

The first is that the failure description contains a CRC Checksum check error message. What does this mean? Only that the requested archive is damaged. Incidentally, the cause of the failure is also described: Unarc.dll returned error code 12. How to fix this situation? Yes, it's very simple. If such a failure occurs, then, the archive is simply nedokachan, so it is worth looking for another version of it and downloading it from another resource. You should also pay attention to the fact that the archive file may actually be corrupted. The solution is the same.

In the second case, the message also contains the Unarc.dll library (error code 12), however, as a result, the system indicates the impossibility of unpacking (decompression failed). This is not damage to the archive, as many users think. In fact, everything can be fine with it, only to reduce its volume, we used the methods of maximum compression (in 7-Zip it's the algorithms bcj2, ppmd, lzma2, delta, etc.), maximally archived self-extracting SFX archives that require a DLL on The unpacking stage, or the most recent versions of archiver programs.

Unarc.dll returned error code 12: how to fix it in the simplest way?

Proceeding from the above, let's look at the simplest solution to the problem. Let's take a standard situation. For example, repack is packed with the WinRAR program of the fifth version, and the user has a fourth installed on the computer. It is clear that with its help decompression of files will be simply impossible, despite the almost identical compression algorithms.

What should I do in this case? Yes, just download the latest version of the archiver from the Internet and try again. It should be noted that if it does not work, say, WinRAR, you can try the same procedure with 7-Zip. That's all.

Correcting ways to install games or other software

But not everything is so simple. The fact is that the failure of "Unarc.dll returned an error code of 12" may appear in another very trivial situation. The fact is that some repacks with games and patches, which are "cracked" versions of original distributions, do not allow unpacking or installation in folders whose names or in the indicated ways contain Cyrillic characters.

Let us explain with an example. For example, if the user installs the game on the path C: \ Documents \ Games or C: \ Documents \ Games, it simply will not stand up because of the directory names in Cyrillic. As already clear, in part the problem (if only it really is this) is solved by the usual renaming of directories into Latin names.

Increase the size of the paging file

There is another case when a failure occurs with the message "Unarc.dll returned error code 12". It may be due to the too small size of the paging file or its disconnection in the system. It is clear that you need to enable it and adjust the size.

Here you have to be extremely sharp, since setting an overestimated or underestimated volume can lead to the complete inoperability of Windows. However, it is also not necessary to set the automatic definition of the file size. Let us proceed simpler.

First, we use the "Run" menu, called Win + R, where we assign the command sysdm.cpl, then in the appeared settings window on the "Advanced" tab we use the parameter button and go to the "Advanced" tab in a new window.

In the virtual memory section, we press the change settings button, and then uncheck the automatic configuration line and specify the size manually. One small tip: in the upper window, where the disks and logical partitions are specified, it is better not to choose a system volume, but to specify a virtual partition with more space as the place. In addition, the original size is not changed, but here's the maximum is the one that is equal to the volume of "RAM". For example, a user has 4 GB memory slots. The corresponding size will be 4096 MB. Remember that 1 GB contains 1024 MB, and not one thousand, as some think. Now it remains to press the size button and save the changes, after which it is desirable to reboot the system (this is not a prerequisite, such a procedure, say, is highly recommended for execution).

Note: you can access the paging file settings from the standard "Control Panel" in the system properties section, however, the command input will be faster.

Checking the RAM

Finally, another problem with the fact that a failure occurs, and the message indicates that Unarc.dll returned error code 12, may be due to incorrect operation of the RAM (too strong and unreasonable load, physical damage, etc.). . Although this situation is rare, it can not be discounted.

In this case, the situation with fixed terminals looks simpler. You just need to take out all the memory slots from the slots on the "motherboard", then insert them in turn, after which each time anew try to perform the installation or unpacking.

But before that, it is extremely necessary to check the "operative". You can use the built-in Windows tools to do this. The verification tool is selected from the administration section in the Control Panel.

However, as practice shows, it's better to use the specialized utility Memtest86 +, which you must first download from the Internet, and then use it to create a boot disk, and only then start with it. This program works more efficiently than the "native" Windows utility.

When the scan is complete, you will be able to find out exactly where the failure occurred and whether it occurred at all. As it is already clear, if the bars have become unusable, they will have to be replaced.

With laptops, the situation is somewhat more complicated, because to reveal them yourself, and even if they are under warranty, certainly not worth it. There is only one way out: contact the service center. You can, of course, try to solve the problem yourself. But this, as they say, at your own peril and risk.

Is it worth downloading bad libraries from the Internet?

Finally, a few words about another solution, which offers some, so to speak, "experts". They recommend simply download the Unarc.dll and ISDone.dll files from the Internet and copy them to the appropriate location on the hard drive. Immediately say: do not do such stupid things. The maximum that can be achieved is only to change the error code, say, 7 or 1. But the above recommendations eliminate the problem by 99%. If it does not work, reinstalling Windows can not be avoided, since the problem can be much deeper.

Conclusion

As you can see, the proposed solutions to the problem are quite simple and accessible for understanding. However, the problems associated with viruses were not considered here. Firstly, they are extremely rare, and secondly, any self-respecting user should know how to test the system for threats and their elimination.