mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1350] updating comfy desktop to 0.4.75 causes custom nodes to be unrecognized #373
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#373
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 @manassm on GitHub (Sep 30, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1350
I tried reverting it to pervious verison but it didn't work.
Any help would be appretiated. Thank you.
┆Issue is synchronized with this Notion page by Unito
@dosubot[bot] commented on GitHub (Sep 30, 2025):
When custom nodes become unrecognized after updating Comfy Desktop, it's often due to a mismatch between the location of your custom nodes and the configuration file that tells ComfyUI where to find them. In v0.4.74, the app relies on the
extra_models_config.yamlfile—specifically thedesktop_extensions.custom_nodesentry—to locate custom nodes on disk. If this config is missing or points to the wrong directory, nodes won't load, even if you revert versions source.Here’s what you can do:
ComfyUI/custom_nodes).extra_models_config.yamlfile in your user data directory and verify that thedesktop_extensions.custom_nodespath matches the actual location of your custom nodes.pip install -r requirements.txtfor each node source.If you still see missing nodes, try disabling all custom nodes from the settings menu, then re-enable them one by one to isolate any problematic node source.
Let me know if you need help with any of these steps!
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
@manassm commented on GitHub (Sep 30, 2025):
I simply fixed it by reinstalling all missing nodes.
Thank you for your help.
@webfiltered commented on GitHub (Sep 30, 2025):
@manassm I'm very sorry to hear that! Did you happen to notice anything that seemed strange or out of place during the update?
@manassm commented on GitHub (Sep 30, 2025):
I haven't recognized anything particularly different than previous updates.
It's working fine after reinstalling the nodes.
Thank you for your interest.