Gibbed Won't Open?

"It won't open" covers about five completely different problems, and people waste time because they try the fix for someone else's symptom. A "Source code" mixup and a broken .NET install both look like "nothing happens when I double-click," but the fixes have nothing in common. So before you reinstall anything, figure out which one you've actually got.

First — which symptom is it?

• The folder has no program in it, just files ending in .cs → you got the source code. Jump to #1.
• You double-click and nothing happens, or a window flashes and vanishes → missing files or .NET. #2 and #3.
• A "Gibbed has stopped working" box pops up → almost always .NET. #3.
• The exe vanished on its own → your antivirus took it. #4.

Work down the list in that order. Most people are fixed by #1 or #2.

1. You downloaded the source code, not the editor

This is the most common one, and it's an easy trap. GitHub's big green button hands you "Source code (zip)" — the raw C# project files, not the program. Unzip that and you'll find folders full of .cs files and no editor to run, so it looks like the editor is "broken" when you never actually downloaded it.

The file you want is bl2_saveedit_1.0.46.zip from the release assets, and the program inside is Gibbed.Borderlands2.SaveEdit.exe — the one with Handsome Jack's mask for an icon. If you're not staring at that icon, you don't have the editor yet.

Grab the right file — full walkthrough in how to download safely.

2. You didn't extract all of it

The editor isn't a single standalone exe. It ships with a folder of DLLs sitting next to it, and it needs them. Two ways people break this:

• Running the exe from inside the zip — Windows lets you double-click it, but it can't reach its DLLs from in there. Extract first, always.
• Pulling just the exe out and leaving the rest behind. The exe alone won't run.

Fix: right-click the zip → Extract All → into a normal folder (your Desktop is fine). Keep everything together and launch the exe from there. You'll need 7-Zip or WinRAR if Windows won't open the zip natively.

3. .NET Framework is missing or broken

Gibbed is a .NET app. If the framework it needs isn't there or got corrupted, you get the silent double-click or the classic "Gibbed has stopped working" popup — that exact symptom has its own thread in the issue tracker (#114).

It needs .NET Framework 4.5 or newer. Windows 10 and 11 ship with this built in, so on a modern machine the framework usually isn't missing — it's broken or mismatched. What actually helps:

• Repair or reinstall .NET Framework. Grab the latest 4.x web installer from Microsoft and let it repair the existing install.
• Older Windows? Make sure 4.5+ is actually installed — some older setups only have 3.5 or 4.0.
• The Win10 Creator's Update quirk: a few people hit a .NET 4.7-vs-4.6 conflict around that update that produced the "stopped working" crash. A repair install clears it.

4. Your antivirus quarantined it

If the exe was there a minute ago and now it's gone, your antivirus probably ate it. Gibbed throws false positives — it's a known, explained thing, not a real infection. Restore it from quarantine and add a folder exclusion so it stops happening.

5. Run it as administrator

Simple, sometimes it's the whole fix. Right-click the exe → Run as administrator. Permission quirks — especially if you extracted into a protected location like Program Files — can stop it cold without any error message. Running elevated sidesteps that.

Last resort: compatibility mode

If you're on something old or unusual and nothing above worked, force compatibility settings: right-click the exe → Properties → Compatibility → tick "Run this program as an administrator," and try running it for an older Windows version. This is rarely needed on Windows 10/11 — it's mostly for ancient setups — but it's the bottom of the checklist for a reason.

If it opens fine but a save won't load

Then this isn't your article. The editor launching and a specific save failing to load are two different problems. If the editor opens but throws an error when you try to open a save, that's almost always reencode mismatch (PC saves) or invalid SHA1 hash (console saves). Head there instead.