ComfyUI and Wan 2.2 Setup Errors on Windows: EPERM, 7-Zip Code 2, Self-Signed Certificate (What Causes Them)
Setting up ComfyUI and the Wan 2.2 models on Windows means a ~2 GB archive, about 34 GB of models and a lot of unpacking. Most guides only cover what happens after that. Here are the errors that actually stopped people during setup in one week of real data, what each one means, and how to get past it.
The errors, by how many people they stopped
| Error message | Times | People | Usual cause |
|---|---|---|---|
EPERM: operation not permitted, open '…\_downloads\ComfyUI_windows_portable_nvidia.7z' | 153 | 36 | file held by antivirus or another process |
7-zip exited with code 2 | 36 | 28 | damaged archive, full disk, antivirus |
ComfyUI rejected the workflow (HTTP 400) … prompt_outputs_failed_validation | 24 | 21 | ComfyUI too old for the workflow |
read ECONNRESET | 16 | 12 | connection dropped during a huge download |
aborted | 14 | 12 | connection dropped during a huge download |
self signed certificate in certificate chain | 26 | 11 | antivirus HTTPS scanning or a company proxy |
ENOSPC: no space left on device | 6 | 6 | disk full |
For scale: in the same week about 270 people started a setup (counted once per person per day) and 67 finished it. Not every failure above was final; some people pressed Install again and got through.
1. "EPERM: operation not permitted, open …"
The name sounds like a permissions problem, and that's why it's confusing: in our data the folder had just been created and written to without trouble. The error came when the installer tried to open the same archive again, for example on a retry. On Windows a file can't be opened for writing while another program holds it, and a file that was just deleted can stay "pending delete" for a while if something still has it open. The usual suspects:
- Antivirus (including Windows Defender) scanning a freshly downloaded 2 GB archive. Scanning a big .7z can take a while.
- A leftover 7-Zip, Python or ComfyUI process from an earlier attempt that is still running in the background.
- OneDrive syncing the folder. Desktop and Documents are often inside OneDrive.
- Controlled folder access (Windows Security → Ransomware protection), which blocks unknown programs from writing to Documents, Desktop and Pictures.
Fix
- Close every ComfyUI and 7-Zip window. If unsure, restart the PC: that releases all locks.
- Install into a short folder outside OneDrive, for example
C:\ComfyUI, not Desktop or Documents. - Add that folder to your antivirus exclusions (Windows Security → Virus & threat protection → Manage settings → Exclusions).
- If you download by hand, delete the old partial file first or save the new one under a different name.
2. "7-zip exited with code 2"
7-Zip's exit codes are documented: 2 means "fatal error" (1 is only a warning, 8 is "not enough memory"). The message doesn't say which fatal error, so check these in order:
- Is the archive complete? A download that stopped early can still leave a file that looks fine. Compare its size with the size shown on the ComfyUI release page. If it's smaller, download it again.
- Is there enough free space? The unpacked engine needs several GB on top of the archive, and the Wan 2.2 models need about 34 GB more. Plan for about 40 GB free.
- Is antivirus removing files while they're unpacked? The portable build contains thousands of Python files and DLLs. Add the folder to exclusions and unpack again.
- Is the path short? Some files in the portable build sit deep inside folders. Unpacking into a short path like
C:\ComfyUIavoids Windows' old 260-character path limit.
3. "self signed certificate in certificate chain"
This one has nothing to do with the download being unsafe. Antivirus products with HTTPS or SSL scanning and many company networks open every secure connection, inspect it, and re-sign it with their own certificate. They add that certificate to the Windows certificate store, so the browser keeps working. But Node.js and many Python tools don't read the Windows store by default, so to them the connection looks forged, and they stop.
Fix
- Easiest: turn off HTTPS/SSL scanning in your antivirus for the length of the download, or try another network (for example a phone hotspot).
- Node.js tools: point Node at the certificate with the
NODE_EXTRA_CA_CERTSenvironment variable, or use the Windows store with--use-system-ca/NODE_USE_SYSTEM_CA=1(Node.js 22.19+ and 24.6+), as described in the Node.js guide. - pip: since pip 24.2 the system certificates are used by default (pip docs), so upgrading pip inside ComfyUI's embedded Python often fixes package installs.
- Don't disable certificate checks (
NODE_TLS_REJECT_UNAUTHORIZED=0,--trusted-hosteverywhere). That makes every download unverified.
4. HTTP 400 "prompt_outputs_failed_validation"
This one appears after setup, on the first render: ComfyUI received the workflow but refused it because a node or an option in it doesn't exist in that ComfyUI version. In our data it came from older ComfyUI installs running newer workflows. In the portable build, run update\update_comfyui.bat, or install a current release. ComfyUI's full error response names the node that failed, which tells you what it doesn't recognise.
The other two: dropped connections and a full disk
- ECONNRESET / aborted: the Wan 2.2 model files are 10–15 GB each, and many connections drop at least once during that. Use a downloader that can resume (a browser can, plain scripts often can't) instead of starting from zero.
- ENOSPC: the C: drive is usually the fullest one. Check before you start; the models alone are about 34 GB.
What Loomance 0.2.1 changes
These numbers are why version 0.2.1 (released 28 October 2026) changes how setup works: a locked archive is downloaded again into a new folder instead of failing; an incomplete download is detected and resumed before 7-Zip ever sees it; a failed unpack is retried and then downloaded fresh once; and after a certificate error downloads switch to the Windows certificate store, the same way a browser connects. If something still fails, the message now says what to check. Loomance 0.2 also updates older installs to ComfyUI 0.40, which ends the HTTP 400 error. Whether the fixes work as intended will show in next week's data, and I'll update this page with it.
Sources
- 7-Zip command-line exit codes
- Node.js: enterprise network configuration (NODE_EXTRA_CA_CERTS, --use-system-ca)
- pip: HTTPS certificates
- ComfyUI and its releases
- Wan 2.2 twice as fast: what changed in Loomance 0.2
- Wan 2.2 on an 8GB GPU: what hardware you need before you start
Related articles
- Wan 2.2 on an 8GB GPU: what real tests show about VRAM and RAM
- Wan 2.2 twice as fast: SageAttention + split CFG, measured
- Loomance vs ComfyUI on Wan 2.2
Frequently asked questions
Skip the manual setup
Loomance installs ComfyUI and Wan 2.2 for you, checks your PC first, resumes dropped downloads and handles the errors above. Free to use (ad-supported), renders locally on your NVIDIA GPU.
Download free