mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1341] [Bug]: Cannot install due to lack of space, even though there is almost 600 GB of space #372
Labels
No labels
area: desktop-app
Bounty
bug
bug-cop:answered
bug-cop:response-received
component: installer
component: preload
custom node
dependencies
Design
documentation
duplicate
enhancement
expected
frontend
good first issue
installation
Low-Priority
performance
Planned
platform: cross-platform
platform: windows
Potential Bug
Potential Bug
pull-request
question
refactor
Release
stale
User Support
V1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/desktop#372
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CallMeDeans on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1341
App Version
ComfyUI Setup 0.4.72 - x64.exe
Expected Behavior
Install normally
Actual Behavior
I have over 600 GB of space on the C:/ drive. I saw an issue similar to mine, however my path to powershell is already correct but I'm still getting the same issue.
Steps to Reproduce
Try to install, select nvidia gpu.
Debug Logs
Browser Logs
unavailable
Settings JSON
unavailable
Other
No response
@dosubot[bot] commented on GitHub (Sep 23, 2025):
Hi @CallMeDeans! I'm Dosu and I’m helping the desktop team.
This is a known bug in ComfyUI Setup 0.4.72 and earlier: the installer can report "Insufficient space" even when you have plenty of free disk space, especially on systems with multiple or large drives. The root cause is a faulty disk space detection check in the installer code. There’s no reliable workaround for 0.4.72, but the bug is fixed in version 0.4.73 and later—upgrading will resolve the issue [details][fix PR].
Running as administrator and verifying your PowerShell path are good steps, but they won’t fix this specific bug. If you need to install right away, you could try the portable version or manual install as a temporary solution [docs].
To reply, just mention @dosu.
Docs are dead. Just use Dosu.
@CallMeDeans commented on GitHub (Sep 23, 2025):
@dosu is there a simple installation for 0.4.73?
@webfiltered commented on GitHub (Sep 23, 2025):
Almost there! Fix is on the way. You may use v0.4.73 (below). I've had a report that this version may not automatically update (to future versions). If that happens it's an easy fix: just download & run a newer version and it'll update itself and fix everything.
v0.4.73 download links:
Mac (Apple Silicon): https://download.comfy.org/250922i0fc1qno0/mac/dmg/arm64
Windows: https://download.comfy.org/250922i0fc1qno0/windows/nsis/x64
@CallMeDeans commented on GitHub (Sep 23, 2025):
Thank you so much!