ComfyUI Common Issues and Fast Fixes

If you are dealing with one obvious error and need a quick answer, start here.

If the environment keeps breaking after plugin installs, or startup fails repeatedly after you "fix" one package, switch to a deeper guide instead of repeating random command-line repairs:

• How to Fix ComfyUI Plugin Import Failed Errors
• ComfyUI Startup Failed? How to Diagnose and Recover Faster
• ComfyUI Dependency Conflicts: Fix Them Without Reinstalling
• ComfyUI Reconnecting Error: Causes and Fast Fixes

Installation Issues

"CUDA is not available" or "Torch not compiled with CUDA"

Cause: PyTorch was installed without CUDA support, or the CUDA version doesn't match your NVIDIA driver.

Fix:

1. Check your NVIDIA driver version: run nvidia-smi in Command Prompt
2. Confirm the Python that launches ComfyUI has a CUDA-enabled Torch build:

python -c "import torch; print(torch.__version__); print(torch.version.cuda); print(torch.cuda.is_available())"

3. If you're using the portable package, make sure you downloaded the NVIDIA version and are running run_nvidia_gpu.bat
4. If it prints False, follow the full Torch not compiled with CUDA enabled repair guide before installing more plugins

ComfyUI Desktop shows "Unsupported device"

Cause: ComfyUI Desktop on Windows requires an NVIDIA GPU with CUDA. AMD and Intel GPUs are not supported in the Desktop version.

Fix: Use the Portable Package or Manual Install instead.

Installer or app blocked by antivirus

Cause: Windows Defender or third-party antivirus flagging ComfyUI as suspicious.

Fix:

1. Add ComfyUI's install directory to your antivirus exception list
2. For Windows Defender: Settings → Privacy & Security → Virus & Threat Protection → Manage Settings → Exclusions
3. Re-download and try again

7-Zip extraction fails

Cause: The downloaded file is blocked by Windows or the path is too long.

Fix:

1. Right-click the .7z file → Properties → check Unblock → Apply
2. Extract to a short path like D:\ComfyUI instead of a deeply nested folder
3. Make sure you're using 7-Zip, not Windows built-in zip

"Permission denied" or package install failures

Cause: Running ComfyUI or its installer as Administrator, or installing to a system-protected folder.

Fix:

1. Never run ComfyUI as Administrator — this causes Python package permission conflicts
2. Do not install to C:\Program Files, C:\Windows, or C:\ root
3. Use a non-system path like D:\ComfyUI or C:\Users\YourName\ComfyUI

Windows Long Path Limit

Cause: Windows has a default 260-character path limit. Deep folder structures in custom nodes can exceed this.

Fix: Enable long paths in Windows 10/11:

1. Press Win + R, type regedit, press Enter
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
3. Set LongPathsEnabled to 1
4. Restart your computer

Or run this in PowerShell (as Administrator):

New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force

Runtime Issues

CUDA Out of Memory

Cause: Your GPU doesn't have enough VRAM for the model or resolution you're using. See System Requirements for VRAM guidance per model type.

Fix (try in order):

1. Close other GPU applications (browsers, games, other AI tools)
2. Reduce the image resolution (e.g., 512×512 instead of 1024×1024)
3. Add --lowvram flag to your launch command
4. Use GGUF quantized models (see Download Models)
5. For video models: reduce frame count and resolution

If the log says MemoryError, DefaultCPUAllocator, MPS backend out of memory, or the machine still fails after basic --lowvram changes, use the full ComfyUI Out of Memory guide to separate VRAM, system RAM, and allocator issues.

Red Nodes in Workflow

Cause: The workflow uses custom nodes that you haven't installed.

Fix:

1. Install ComfyUI Manager
2. In Manager, click Install Missing Custom Nodes
3. Restart ComfyUI

"No checkpoint found" / Empty model dropdown

Cause: No model files in the checkpoints folder, or files are in the wrong location.

Fix:

1. Download a model (see Download Models)
2. Place the .safetensors file in ComfyUI/models/checkpoints/
3. Click Refresh in the model dropdown, or restart ComfyUI

For LoRA, VAE, ControlNet, Flux, GGUF, and text encoder folders, see Where to Put Safetensors in ComfyUI.

Browser shows blank page or title only

Cause: Browser incompatibility.

Fix: Use the latest version of Google Chrome. Some browsers (especially older Edge or Firefox versions) may not render the ComfyUI interface correctly.

If the terminal mentions comfyui-frontend-package, see ComfyUI Frontend Package.

ComfyUI keeps reconnecting

Cause: The browser lost its live connection to the ComfyUI server. The server may have crashed, a custom node may have broken the frontend, or a firewall/proxy/browser extension may be blocking the websocket connection.

Fix: First check whether the terminal is still running. Then test with custom nodes disabled and open ComfyUI from http://127.0.0.1:8188 before testing LAN or proxy access. See ComfyUI Reconnecting Error for the full diagnosis path.

Failed to fetch server logs

Cause: The browser interface tried to read logs from the ComfyUI server, but the request failed. This can happen when the server crashed, a firewall blocked the request, or a custom node/frontend extension broke part of the UI.

Fix: Find the real terminal log first. If the server still responds at http://127.0.0.1:8188, check browser DevTools and test with custom nodes disabled. See ComfyUI Failed to Fetch Server Logs.

"Prompt has no outputs"

Cause: The workflow has no output node (Save Image, Preview Image, etc.), or the output node is muted or disconnected.

Fix:

1. Make sure a Save Image or Preview Image node is connected at the end of your node chain
2. If nodes are greyed out, select them and press M to unmute
3. If nodes are red (missing custom nodes), install them via ComfyUI Manager → Install Missing Custom Nodes
4. If the workflow still looks correct but the queue refuses to run, use the full ComfyUI Prompt Has No Outputs Fix guide to check muted branches, disconnected output chains, and imported workflows with missing nodes

Generation is extremely slow

Cause: ComfyUI may be running on CPU instead of GPU.

Fix:

1. Check the console output — it should show your GPU name on startup
2. If using portable: make sure you're running run_nvidia_gpu.bat, not run_cpu.bat
3. If using manual install: verify PyTorch has CUDA support:

python -c "import torch; print(torch.cuda.is_available())"

Should print True. If it prints False, reinstall PyTorch with CUDA.

If you have more than one NVIDIA GPU and ComfyUI is using the wrong card, see ComfyUI Multi GPU for --cuda-device, separate ports, and two-instance setup.

"No module named 'triton'" or Triton unavailable

Cause: Triton is an optional acceleration backend for SageAttention, torch.compile, and some custom nodes. If ComfyUI opens and normal workflows run, this is usually not the root problem.

Fix: Do not install the normal triton package blindly on Windows. If a workflow really requires Triton, use ComfyUI's exact Python and install the Windows package path from ComfyUI No Module Named 'triton'. For portable builds, that usually means python_embeded\python.exe, not system Python.

GPU-Specific Issues

RTX 50 Series (5070 Ti / 5080 / 5090)

See GPU Compatibility for the full driver-CUDA-PyTorch matrix. The RTX 50 series requires CUDA 12.8+ and specific PyTorch builds:

1. Update your NVIDIA driver to the latest version
2. Install PyTorch with CUDA 13.0:

pip install torch torchvision torchaudio --extra-index-url https://download.pytorch.org/whl/cu130

3. For the portable package, use the latest release with CUDA 13.0 support

Common 50-series issues:

• SageAttention compilation errors — see ComfyUI No Module Named 'sageattention' before adding acceleration packages
• Nunchaku plugin failures - use the Nunchaku Missing in ComfyUI guide and choose an official wheel that matches Python, Torch, CUDA, and GPU
• xformers crashes — use PyTorch's built-in attention (--use-pytorch-cross-attention)

AMD GPUs on Windows

See GPU Compatibility for full AMD support details. AMD support on Windows uses DirectML, which has limitations:

• Some custom nodes don't support DirectML
• Performance is lower than CUDA
• Use the portable package with run_cpu.bat and add --directml flag

Network Issues

Hugging Face model download fails

Cause: ComfyUI, a custom node, or a launcher could not download a model file from Hugging Face. The root cause may be network routing, proxy settings, gated model access, an invalid token, offline mode, or a wrong model path.

Fix: First test the exact Hugging Face URL in a browser and terminal. If the browser works but ComfyUI fails, check whether the ComfyUI process has the same proxy and HF_TOKEN environment variables. See ComfyUI HuggingFace HttpRequestException for the full diagnosis path.

pip install hangs or times out

Cause: Network restrictions, firewall, or proxy blocking Python package downloads.

Fix:

1. Try a mirror:

pip install -r requirements.txt -i https://pypi.tuna.tsinghua.edu.cn/simple

2. If behind a proxy, configure pip:

pip install --proxy http://your-proxy:port -r requirements.txt

3. In ComfyUI Desktop: change the mirror settings in the setup wizard

Git clone fails

Cause: GitHub is blocked or rate-limited in your region.

Fix: Use a mirror or download the ZIP directly from the GitHub release page.

How Wonderful Launcher helps

Wonderful Launcher can detect and fix this issue automatically. It manages your ComfyUI environment safely — isolating dependencies, recovering broken installations, and preventing conflicts.

Download Wonderful Launcher — it's free.

Not Finding Your Issue?

Try the Troubleshooting Decision Tree for a systematic diagnosis approach. For complex multi-plugin environments, see Dependency Conflicts and Workflow Environment Setup.

Still Stuck?

If none of the above solutions work, try Wonderful Launcher to recover your environment without reinstalling from scratch.

Source References

• ComfyUI troubleshooting overview
• ComfyUI custom node troubleshooting guide
• ComfyUI system requirements