mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1431] Can't Comfyui 0.5.8 be installed in the same folder? #403
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#403
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 @3qyemo on GitHub (Nov 23, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1431
Due to an update issue with Comfyui version 0.5.5, I have re downloaded version 0.5.8. During installation, everything worked fine and ran successfully. However, when I closed Comfyui and ran it again, the above error interface appeared. The interface displayed: Base path Cannot open the base path. Please select a new one. I don't know where the problem occurred. I installed Comfyui in the same folder, and version 0.5.5 ran normally, but version 0.5.8 encountered an error.
┆Issue is synchronized with this Notion page by Unito
@dosubot[bot] commented on GitHub (Nov 23, 2025):
Installing ComfyUI 0.5.8 in the same folder as 0.5.5 is not supported and can cause issues like the "Base path Cannot open the base path" error. This happens because the updater wipes the entire install directory during updates, which can delete your config and model files if your base path is set inside the application folder. When you restart, ComfyUI can't find or access the expected files, triggering the error source.
To fix this, select a new base path outside the application directory (for example, in your Documents folder), move your user data (models, configs) there if needed, and update ComfyUI to use that new base path. For future upgrades, always install new versions in a separate, empty directory and use the migration option if you want to bring over your data source.
A future update will improve validation and migration for base paths, but for now, manual migration is required. If you need help recovering lost files or further troubleshooting, let me know.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@TignishPEI commented on GitHub (Nov 24, 2025):
Can someone answer WHAT needs to be moved to a "new directory"? In plain language? I can't get it to do anything except throw errors. Either the base path one, or a generic "Unable to start Comfy"
@3qyemo commented on GitHub (Nov 25, 2025):
@TignishPEI The installer and model folders can run normally if installed on different drives; for example, the installer is on the C drive by default, and the model files can be placed on the D or E drives. However, I don't like version 0.5.8; it has quite a few bugs.
@benceruleanlu commented on GitHub (Dec 1, 2025):
The frontend change to let users know what the exact issue was about the base path was accidentally left out of two versions, it has been fixed in the last few versions.
The issue about the base path was that some base paths were known to be cleared on every update, and there were a few reports of that happening. To prevent users from losing data, those paths were set up so users were alerted if their user data path was in any of these folders.
The unable to start ComfyUI desktop screen isn't supposed to be shown, only when there is an actual fatal error that the maintenance screen can't fix. It might be pretty late, but feel free to leave your log files for someone to look into deeper.
There are a lot of known issues and features that need to be fixed or implemented in terms of the desktop distribution. We're very aware of them, and we're working to make desktop better.