Troubleshooting · Setup

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.

Published 28 October 2026 · By Vismantas Šleinota · Data: anonymous setup events from Loomance, 22–28 October 2026

Quick answer: four errors caused most failed setups. EPERM on the downloaded archive (36 people) means a file is being held by antivirus, OneDrive or a leftover process, not that you lack permissions. "7-zip exited with code 2" (28 people) is 7-Zip's fatal error: a damaged or incomplete archive, a full disk, or antivirus blocking the unpack. "self signed certificate in certificate chain" (11 people) means an antivirus with HTTPS scanning or a company proxy is in the middle of the connection. HTTP 400 "prompt_outputs_failed_validation" (21 people) means the ComfyUI version is too old for the workflow. Fixes for each are below.
Where the numbers come from: Loomance (which I build) installs ComfyUI portable and Wan 2.2 automatically and reports anonymous setup events: the error text, no files or personal data. The table counts error messages from one week. It is one installer's data, not all of ComfyUI, but the errors themselves come from Windows, 7-Zip, Node.js and ComfyUI, so they look the same when you install by hand.

The errors, by how many people they stopped

Error messageTimesPeopleUsual cause
EPERM: operation not permitted, open '…\_downloads\ComfyUI_windows_portable_nvidia.7z'15336file held by antivirus or another process
7-zip exited with code 23628damaged archive, full disk, antivirus
ComfyUI rejected the workflow (HTTP 400) … prompt_outputs_failed_validation2421ComfyUI too old for the workflow
read ECONNRESET1612connection dropped during a huge download
aborted1412connection dropped during a huge download
self signed certificate in certificate chain2611antivirus HTTPS scanning or a company proxy
ENOSPC: no space left on device66disk 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:

Fix

  1. Close every ComfyUI and 7-Zip window. If unsure, restart the PC: that releases all locks.
  2. Install into a short folder outside OneDrive, for example C:\ComfyUI, not Desktop or Documents.
  3. Add that folder to your antivirus exclusions (Windows Security → Virus & threat protection → Manage settings → Exclusions).
  4. 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:

  1. 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.
  2. 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.
  3. 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.
  4. Is the path short? Some files in the portable build sit deep inside folders. Unpacking into a short path like C:\ComfyUI avoids 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

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

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

Related articles

VŠ

Vismantas Šleinota builds Loomance, a free local AI animation app, as a solo project in Lithuania, and discusses local AI video as u/noise_to_motion on Reddit. Hit a setup error that isn't on this page? Send it to [email protected].


Frequently asked questions

What does "EPERM: operation not permitted, open" mean when installing ComfyUI?
Windows refused to open a file for writing because something else is holding it: usually antivirus scanning a freshly downloaded archive, a leftover 7-Zip or Python process from an earlier attempt, OneDrive syncing the folder, or a file that was just deleted and is still pending removal. It is rarely a missing permission. Close other ComfyUI or 7-Zip windows, restart the PC, keep the install folder out of OneDrive, and add it to your antivirus exclusions.
What does "7-zip exited with code 2" mean?
Exit code 2 is 7-Zip's "fatal error". When unpacking the ComfyUI portable archive it almost always means the archive is incomplete or damaged, the disk ran out of space, or antivirus blocked files while they were being written. Compare the file size with the size on the GitHub release page, check free space (the extracted engine needs several GB, the Wan 2.2 models about 34 GB more), and download again.
How do I fix "self signed certificate in certificate chain" during setup?
It means an antivirus with HTTPS scanning (or a company proxy) is re-signing secure connections with its own certificate. Browsers trust it because it is in the Windows certificate store, but Node.js and older Python tools do not. Turn off HTTPS/SSL scanning for the download, or point the tool at the certificate: NODE_EXTRA_CA_CERTS or --use-system-ca for Node.js, a recent pip (24.2+) for Python. Never turn certificate checking off.
Why does ComfyUI answer HTTP 400 "prompt_outputs_failed_validation" for a Wan 2.2 workflow?
The workflow uses nodes or options that your ComfyUI version doesn't know yet. In our data every case came from older ComfyUI installs. Updating ComfyUI (update\update_comfyui.bat in the portable build) fixes it.

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