Alex Ruben
How To Resolve the Unarc.dll Error Code 11 in Fitgirl and Dodi Repack (2025)
So, if that pesky “unarc.dll returned error code -11” keeps popping up during your attempts to install a FitGirl or DODI repack, you’re not alone. Honestly, this error is kinda stubborn and can be caused by a bunch of things—missing DLL files, system config issues, virtual memory problems, or outdated redistributables. Usually, it’s fixable with a handful of steps, even if your system isn’t the latest and greatest. The goal here is to get those files in the right place, make sure your system has all the necessary components, and hopefully, get that install happening smoothly without crashes or errors.
Following these steps should patch up the common culprits behind error -11. Fair warning, sometimes a particular fix works on one machine but not another, so a bit of trial and error might be involved. But hey, it’s worth the effort if you want to avoid re-downloading or painfully troubleshooting every time a new error shows up.
How to Fix the Unarc.dll Error -11 When Installing Repack Files
Make sure you’ve got the right DLL files and they’re in the correct spots
This is often the main cause—missing or corrupted DLLs like isdone.dll or unarc.dll. These files handle decompression tasks during installation. If they’re not where they’re supposed to be, or if they’re out of date, errors tend to happen.
- Head over to DLL download sites—but beware, some are shady. The most legit option is usually DLLME or the official repositories. Just make sure to grab the latest version.
- Download both
isdone.dllandunarc.dll. After grabbing them, find them in your Downloads folder. - Extract them if needed (right-click > Extract All) and move those files to your Desktop for easy access.
Now, the tricky part is copying these DLLs into the right directories. Windows uses different folders depending on architecture—System32 for 64-bit, and SysWOW64 for 32-bit (on 64-bit OS). Some say putting both DLLs in both folders works best, especially if you’re not sure what architecture the application expects.
- Open File Explorer and go to This PC > Local Disk (C:).
- Navigate to Windows > System32. Paste
isdone.dllandunarc.dllhere. If you get a UAC prompt, accept it by clicking Continue. - Similarly, go to SysWOW64 and paste those files again. Again, accept any prompts.
This step can help because sometimes, the error is caused by Windows not finding or being able to load the DLLs during extraction. Seems dumb, but it works on some setups, especially with corrupted or mismatched system files.
Install the Visual C++ Redistributable Packages – Because Windows Needs Them Too
This is a classic—lots of errors are caused by missing runtime components, which the DLLs depend on. Grab the latest all-in-one Visual C++ Redistributable package. A good source is this link. It covers all versions, so it’s basically a one-stop-shop.
- Download the ZIP or installer from the link—whatever works better for you.
- Extract if needed (right-click > Extract All), then run
install_all.batfile if it’s an archive, or just run the installer if it’s an executable. - If prompted for administrator rights, give it. Wait for the install to finish. Sometimes it might be a bit glitchy, but on most setups, it just needs a few seconds.
Adjust Virtual Memory Settings, The Overlooked Culprit
Yes, Windows virtual memory (paging file) matters. If it’s too small, the decompression might choke, especially with large files or systems with limited RAM. This is kinda a wild card fix but worth trying.
- Press Win + R, type sysdm.cpl, and hit Enter.
- Switch to the Advanced tab and click Settings under Performance.
- In the new window, go to the Advanced tab and click Change under Virtual Memory.
- Uncheck Automatically manage paging file size for all drives.
- Select your C: drive (or the drive where Windows is installed).
- Choose Custom size. Here’s the part where people get confused: input different values based on your RAM:
- 4 GB RAM: Initial size 2048 MB, Max size 4096 MB
- 8 GB RAM: Initial 4096 MB, Max 8192 MB
- 16 GB RAM: Initial 8192 MB, Max 16384 MB
- 32 GB RAM: Initial 16384 MB, Max 32768 MB
- 64 GB RAM: Initial 32768 MB, Max 65536 MB
- Hit Set, then OK, and restart your PC to make sure the new settings are applied.
It’s a bit of a pain because Windows can be stubborn about applying these changes, but it can really help avoid errors caused by insufficient virtual memory.
Restart and Re-test the Installation
Once everything’s in place—DLLs copied over, redistributables installed, virtual memory adjusted—restart the PC. Sometimes, Windows needs a fresh boot to recognize new files or settings. After reboot, try rerunning your install. If it’s still not working, double-check each step. Missing files or incorrect settings are usually the reason things still fail.
Extra Tips & Common Issues
Make sure your antivirus isn’t blocking the DLL files or the installer. Sometimes, AV software treats new DLLs as suspicious, which makes things more complicated. Setting an exception or disabling AV temporarily might help.
Another thing—if your antivirus or Windows Defender reports the DLL files as suspicious, it’s worth doing a quick virus scan or scanning the files online. Better safe than sorry, and sometimes false positives are annoying.
Wrap-up
This process is a bit of a mess, no doubt, but fixing DLL errors usually boils down to some combination of copying files into the right folders, installing missing runtimes, and tweaking virtual memory. Keep in mind—on some setups, giving Windows a reboot after each step can make a difference. Most folks find that once they get these DLLs in place and the system ready, the install completes without a hitch.
Summary
- Download missing DLL files and copy them into System32 and SysWOW64
- Install the latest Visual C++ Redistributables
- Adjust virtual memory according to your RAM size
- Restart and test the install again