Unarc.dll Returned an Error Code 12: How to Fix Game Installation Failures (2026)

Updated: November 1, 2026 | Operating systems: Windows 11 and Windows 10 | Error type: Game and software installation failure

What Does “Unarc.dll Returned an Error Code 12” Mean?

Many PC games and large applications are distributed as compressed installation packages. During setup, the installer extracts thousands of files onto your computer.

Some installers use unpacking components associated with unarc.dll and ISDone.dll.

If the extraction process fails, a dialog may appear with a message such as:

Another installer may report a CRC check failure or use the number 12 without the minus sign.

The exact wording matters because installers can use different versions of unpacking components.

A failed CRC check indicates that data did not pass an integrity check. That can happen because the downloaded archive is damaged, but memory or storage problems can also corrupt data during processing.

Therefore, error -12 should be treated as an extraction failure requiring investigation, not as proof that one particular DLL file is defective.

Why Does Unarc.dll Error Code -12 Happen?

Fix 1: Verify or Download the Installer Again

The first troubleshooting step is to determine whether the installation files are complete and intact.

A large compressed archive may become unusable if part of the download is missing or damaged.

Even if the installer starts normally, it may fail when it reaches the damaged section.

1. Close the failed installer.
2. Open the official website or game launcher from which you obtained the software.
3. Check whether the publisher provides a file verification or repair option.
4. If available, run the verification tool.
5. Otherwise, download a fresh installer from the official source.
6. Check that all required installation files are present.
7. Run the installer again.

For games installed through Steam, use the built-in file verification feature when appropriate.

If the publisher supplies a SHA-256 checksum, compare it with the downloaded file’s checksum.

In PowerShell, you can calculate a file hash using:

Get-FileHash "C:\Downloads\setup.exe" -Algorithm SHA256

Replace the example path with the actual installer file. Compare the resulting hash only against a checksum published by a trustworthy source.

If the values differ, obtain a fresh copy of the file.

Fix 2: Check Free Disk Space

Compressed installers may require considerable temporary storage while extracting files.

For example, a 30 GB download can expand to a much larger installed game.

The setup process may also create temporary files on the Windows system drive, even if you selected a different destination.

Check both locations:

• The drive where the game will be installed.
• The Windows system drive, usually C:, where temporary files may be created.

To check available storage:

1. Open File Explorer.
2. Select This PC.
3. Review the free space on your drives.
4. Compare the available storage with the game’s published requirements.
5. Leave additional space for temporary extraction files.

There is no universal free-space requirement for every compressed installer. The amount depends on the package and its extraction method.

If space is low, remove unnecessary temporary files through Windows Storage settings and try again.

Fix 3: Install From a Short, Simple Folder Path

Some older or custom installers have difficulty handling complicated folder paths.

Problems may occur when a path contains unsupported characters, excessive nesting or restricted directories.

For a legitimate installer from a trusted publisher, try moving its files into a simple folder such as:

C:\InstallFiles\

Then choose an installation destination such as:

C:\Games\GameName\

Make sure the destination folder is writable and has sufficient free space.

Avoid modifying protected Windows directories or changing system-wide folder permissions.

If the publisher requires a particular installation location, follow those instructions instead.

Fix 4: Check Windows Security Protection History

Security software can block suspicious installation files or quarantine files that appear unsafe.

If an installer suddenly reports that an archive is missing or cannot be read, check whether Windows Security has taken action.

1. Open Windows Security.
2. Select Virus & threat protection.
3. Open Protection history.
4. Review recent actions around the time the installer failed.
5. Check whether a relevant installation file was blocked or quarantined.

If Windows Security detects a threat, do not automatically restore the file.

Verify the file’s source and digital signature where available, and obtain a clean copy from the publisher.

Fix 5: Test Your Computer’s RAM

Decompression can place a significant load on system memory.

If RAM is unstable, the data processed during installation may become corrupted.

Memory problems are more plausible when multiple unrelated installers fail or when the error occurs at different points during repeated attempts.

How to Run Windows Memory Diagnostic

1. Save your work and close open applications.
2. Press Windows + R.
3. Type mdsched.exe.
4. Press Enter.
5. Select Restart now and check for problems.
6. Allow Windows to complete the diagnostic.
7. Review the results after restarting.

A passing basic memory test does not rule out every hardware problem.

If your computer uses memory overclocking or XMP/EXPO settings and you experience broader system instability, consider testing manufacturer-supported default settings.

Only change BIOS or firmware settings if you understand the procedure or have qualified assistance.

Fix 6: Check Windows Virtual Memory Settings

Windows uses a paging file to supplement physical memory when applications need additional committed memory.

Highly compressed installations can require substantial memory resources.

If the paging file has been disabled or configured with an unusually small fixed size, some applications may run into memory limits.

To review the setting:

1. Open Windows Search and type View advanced system settings.
2. Open the matching control panel option.
3. Under Performance, select Settings.
4. Open the Advanced tab.
5. Under Virtual memory, select Change.
6. Check whether Automatically manage paging file size for all drives is enabled.

For most users, allowing Windows to manage the paging file is the simplest approach.

Do not apply arbitrary paging-file sizes from online tutorials. There is no single correct fixed value for every PC.

Restart Windows if you change the configuration.

Fix 7: Check the Storage Drive for Errors

Storage problems can prevent an installer from reading compressed data or writing extracted files.

If error -12 occurs repeatedly, particularly alongside other file errors, investigate the drive.

Start by backing up important files if you suspect storage failure.

Then open Command Prompt as administrator and run a read-only scan of the affected drive:

chkdsk C:

Replace C: with the appropriate drive letter.

For a deeper file-system repair, Windows also supports:

chkdsk C: /f

The repair command may require a restart if the drive is in use. Back up important data before running disk repairs.

CHKDSK checks file-system issues; it is not a complete assessment of SSD or HDD hardware health.

If you suspect physical drive failure, use the storage manufacturer’s official diagnostic tool.

Fix 8: Repair Windows System Files With DISM and SFC

If several unrelated installers fail and Windows is also showing other errors, system-file corruption may be worth checking.

Microsoft recommends running DISM before System File Checker.

Step 1: Run DISM

Open Command Prompt as administrator and enter:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for the process to complete. It may take several minutes or longer.

Step 2: Run System File Checker

After DISM finishes, run:

sfc /scannow

Do not close the Command Prompt until verification reaches 100%.

Restart the computer if repairs were made, then retry the installer.

These tools repair supported Windows components. They do not repair a corrupted third-party game archive, so they should not replace installer verification.

Official Microsoft guide: Using System File Checker in Windows.

Fix 9: Use a Trusted, Compatible Installer

If only one game or application fails while other installers work normally, the package itself may be the problem.

Some heavily compressed or modified installation packages use custom extraction methods.

A damaged or incompatible package can repeatedly produce ISDone.dll or unarc.dll errors.

The safest approach is to obtain the software through its official publisher, supported store or authorized distributor.

For legitimate software, contact the publisher if the installer repeatedly fails after you have verified the download.

Provide the complete error message and the installation percentage at which the failure occurs.

Unarc.dll Error Code 12 vs. -12: Are They the Same?

Online searches frequently omit the minus sign when referring to unarc.dll errors.

For example, a user may search for “error code 12” even when the actual dialog displays “-12”.

However, the exact number and full error message should be preserved when diagnosing the problem.

Different installer builds may use different error descriptions, and the code alone is not a universal diagnosis.

If you contact support, send the precise wording from the dialog rather than a shortened search phrase.

What Is the Difference Between ISDone.dll and Unarc.dll?

Seeing either DLL name does not automatically mean the DLL is missing from Windows.

Should You Download Unarc.dll Separately?

No, not as a routine fix for error -12.

Random DLL download sites can distribute outdated, incompatible or malicious files.

Copying a DLL into System32 or SysWOW64 may introduce additional problems without addressing the damaged archive or failed extraction.

Do not run commands such as regsvr32 unarc.dll unless the software publisher specifically documents that procedure for its component.

For this error, focus first on installer integrity, storage, memory and the software’s official installation requirements.

Why Does Installation Stop at the Same Percentage?

If setup consistently fails at exactly the same percentage, it may be reaching the same damaged archive segment or encountering a repeatable installation problem.

That pattern makes file integrity an especially useful first check.

Verify the installer or download a fresh copy from the official source.

If different installers fail at different percentages, investigate broader issues such as memory stability, storage health and system configuration.

These patterns are diagnostic clues, not proof of one particular cause.

Can Unarc.dll Error -12 Happen With Enough RAM?

Yes. Having 16 GB or 32 GB of installed RAM does not guarantee that extraction will succeed.

Available memory, paging-file configuration, memory stability and the installer itself can all affect the result.

For example, an installer may fail because of corrupted source data even on a computer with abundant memory.

Similarly, a computer with unstable memory can experience extraction failures despite having more than the game’s minimum RAM requirement.

Check the full error message before deciding which component to troubleshoot.

Which Fix Should You Try First?

Official Resources and Further Reading

• Microsoft — Using System File Checker
• Microsoft Learn — Repair a Windows Image
• Microsoft — Windows Support
• Microsoft Q&A — Game Installation and Unarc.dll Errors

Related Windows and Game Error Guides

For additional troubleshooting guides, visit Seminarsonly News and Troubleshooting.

Related topics include Fortnite launch errors, game installation problems, Windows file corruption and game launcher troubleshooting.

Editorial note: Add direct links to existing related articles after verifying their published URLs.

Editorial note: Updated November 1, 2026. This independent guide provides general Windows installation troubleshooting. The exact cause depends on the installer, error text and computer configuration.