Installed Custom Nodes and Broke ComfyUI? Recover Without Reinstalling

If ComfyUI worked before you installed a custom node, and stopped working after, the custom node is usually not the whole problem.

What actually broke is the environment around it.

That can mean:

• a dependency was added or downgraded
• a package was installed for the wrong Python or CUDA combination
• a plugin import failure now blocks startup
• one fix attempt created a second problem somewhere else

The key point is this:

you usually do not need to reinstall ComfyUI immediately.

What this failure pattern looks like

Users often describe it in one of these ways:

• "I installed a node and now ComfyUI will not start."
• "The plugin folder is there, but the nodes are missing."
• "Everything worked until I updated custom nodes."
• "Now I get red nodes, import failures, or Torch errors."

That usually means the custom node changed something outside its own folder.

Step 1: Confirm whether the breakage is import-level or startup-level

There are two common cases.

Case A: ComfyUI still launches, but the node is missing

That means the environment is partly alive, but the plugin import failed.

Go here next:

• How to Fix ComfyUI Plugin Import Failed Errors

Case B: ComfyUI no longer launches

That means the custom node install likely changed a core package or binary dependency.

Go here next:

• ComfyUI Startup Failed? How to Diagnose and Recover Faster

Step 2: Check what changed

The most useful question is:

What was the last thing installed before the environment broke?

Check:

• the custom node repo you installed
• its requirements.txt
• whether you ran pip install -r requirements.txt
• whether another package changed Torch, numpy, opencv-python, pillow, or transformers

If the break happened right after pip install -r requirements.txt, you should suspect dependency drift first.

Step 3: Repair the minimum possible surface

Do not start by reinstalling every plugin.

Instead:

1. identify the exact custom node you added
2. identify the first error it introduced
3. repair the specific package or dependency set
4. retest startup

That is slower than guessing, but much faster than rebuilding the whole environment from zero.

Why users end up reinstalling too early

The usual loop looks like this:

• install custom node
• get one error
• install another package
• break a second package
• lose GPU acceleration
• assume the whole environment is unrecoverable

That is why a lot of "custom node problems" are really maintenance workflow problems.

A better recovery path

Wonderful Launcher is designed for the point where ComfyUI is already fragile.

It is especially useful if:

• you are moving away from a brittle ComfyUI Desktop install
• you have a portable setup with too much package drift
• you already have workflows, models, or client assets on disk
• you want recovery first, not another clean install

Related guides

• How to Install ComfyUI Custom Nodes Without Breaking Your Environment
• How to Fix ComfyUI Plugin Import Failed Errors
• ComfyUI Dependency Conflicts
• ComfyUI Startup Failed? How to Diagnose and Recover Faster

Want the shortest path?

Try Wonderful Launcher first if your environment is already unstable. If you still cannot recover the machine, move to expert help.

Source References

• ComfyUI troubleshooting overview
• ComfyUI custom node troubleshooting guide
• ComfyUI model troubleshooting guide
• ComfyUI Manager installation guide