Deployment Failed: Downloading the Resource Package

If your launcher stops at Downloading resource package, the problem is usually not ComfyUI itself. It usually means the first-run deployment path could not finish downloading the managed install payload from GitHub or another upstream host.

The most common blockers are:

• unstable GitHub download speed
• proxy configured in the browser but not in the launcher path
• firewall or school/corporate network restrictions
• not enough free disk space for extraction

Symptoms

During the first deployment of a ComfyUI environment, the progress stalls at the "Downloading resource package" step and then reports a deployment failure.

Cause

The deployment process needs to download the ComfyUI installation package from GitHub. Slow or unstable access to GitHub is the most common cause of failure. Specific reasons include:

• Network restrictions: Direct connections to GitHub can be slow with high packet loss, causing large file downloads to time out
• Proxy misconfiguration: A proxy tool (Clash, v2rayN, etc.) is installed but the system or Git is not routing traffic through it
• Firewall blocking: Corporate or school networks may block GitHub domains
• Insufficient disk space: The installation drive does not have enough free space (at least 5 GB is required)

What this failure blocks

If this step fails, the managed environment never reaches a stable deployed state. Many users call that "ComfyUI startup failed," but the more accurate diagnosis is:

deployment failed before ComfyUI finished installing

That means it is usually better to solve the download path first than to start repairing Python packages or plugin dependencies.

Solutions

Fastest triage order

If you want the shortest path, check the failure in this order:

1. Confirm the proxy tool is really running
2. Confirm the launcher proxy is set correctly
3. Test whether GitHub itself loads and downloads normally on the same machine
4. Check disk space on the target drive
5. Retry deployment after fixing only one blocker at a time

That sequence usually separates network-path problems from local machine problems quickly.

Option 1: Configure a proxy in Wonderful Launcher (recommended)

If you already use a proxy tool (Clash, v2rayN, Shadowrocket, etc.), you just need to tell Wonderful Launcher to route traffic through it.

1. Open the Settings page in Wonderful Launcher
2. Find the Network Proxy setting
3. Enter your proxy address, then retry the deployment

Common local proxy addresses:

Option 2: Set system environment variables (proxy all programs)

If Option 1 does not work, you can set proxy environment variables at the system level.

Temporary (current terminal session only):

Open PowerShell and run:

$env:HTTP_PROXY = "http://127.0.0.1:7890"
$env:HTTPS_PROXY = "http://127.0.0.1:7890"

Or in CMD:

set HTTP_PROXY=http://127.0.0.1:7890
set HTTPS_PROXY=http://127.0.0.1:7890

Replace 7890 with the port your proxy tool actually uses.

Permanent (write to system environment variables):

1. Press Win + R, type sysdm.cpl, and press Enter
2. Go to the Advanced tab and click Environment Variables
3. Under User variables, create two new entries:
   • Variable name: HTTP_PROXY, Value: http://127.0.0.1:7890
   • Variable name: HTTPS_PROXY, Value: http://127.0.0.1:7890
4. Click OK, then restart Wonderful Launcher and retry the deployment

Option 3: Configure a Git proxy

The deployment process uses Git to clone repositories from GitHub. If Git is not using the proxy, the deployment can still fail even when GitHub loads fine in a browser.

Set a global Git proxy:

git config --global http.proxy http://127.0.0.1:7890
git config --global https.proxy http://127.0.0.1:7890

Proxy only GitHub traffic (recommended — leaves other repos unaffected):

git config --global http.https://github.com.proxy http://127.0.0.1:7890

Use a SOCKS5 proxy:

git config --global http.https://github.com.proxy socks5://127.0.0.1:7891

Verify the configuration:

git config --global --get http.proxy

Remove the proxy setting (to revert):

git config --global --unset http.proxy
git config --global --unset https.proxy

Option 4: Make sure the proxy tool is running

Often the issue is not configuration but that the proxy tool itself is not active. Check the following:

1. Open your proxy tool (Clash Verge, v2rayN, etc.) and confirm it is running
2. Confirm that System Proxy or Global Mode is enabled (not rule-based mode only)
3. Visit https://github.com in a browser to confirm it loads
4. If the browser works but deployment still fails, the proxy is not reaching Git — see Option 2 or Option 3

Option 5: Check disk space

Deploying ComfyUI requires at least 5 GB of free disk space.

Check free space in PowerShell:

Get-PSDrive -PSProvider FileSystem | Select-Object Name, @{N='Free(GB)';E={[math]::Round($_.Free/1GB,2)}}, @{N='Used(GB)';E={[math]::Round($_.Used/1GB,2)}}

Check in CMD:

wmic logicaldisk get name,freespace,size

If space is low, free up disk space or change the installation directory in Wonderful Launcher settings to a drive with more room.

Option 6: Retry the deployment

GitHub connection quality can fluctuate, and occasional timeouts are normal. Close the deployment dialog and click deploy again to retry. Try during off-peak hours for better results.

How this page relates to other startup and install failures

This page is for the resource package download step in first-run deployment.

If the launcher gets past the resource package but fails later while cloning ComfyUI-Manager, use:

• Deployment Failed: Installing ComfyUI-Manager

If the environment already deployed and now ComfyUI itself fails to boot, use:

• ComfyUI Startup Failed
• Fix No module named errors in ComfyUI

Still not resolved?

If none of the above methods work, contact support through the Contact Us button inside the app and include:

• Your network environment (home broadband / corporate network / school network)
• Whether you use a proxy tool, and its name and version
• A screenshot of the error message shown when deployment fails

Source References

• Wonderful Launcher GitHub repository
• ComfyUI GitHub repository
• ComfyUI GitHub releases