Core updated but nodes or templates are missing: check component versions separately

Symptoms and scope

Core source, Desktop shell, frontend package, templates and custom nodes are not one indivisible version. An update can leave some components behind.

Error fragments for search; IDs, values and filenames may vary:

workflow templates
comfyui-frontend-package
comfyui-workflow-templates

Source-supported context

Official update instructions distinguish installation types and their components. A successful git pull does not prove that Python requirements, frontend and template packages were synchronized. Source 1 Source 2

Cases to distinguish

1. Core code changed while the frontend or templates remained old.

2. Updated files belong to another directory but the launcher still runs the old instance.

3. A tutorial needs a particular node/core version rather than merely a refreshed template browser.

Diagnostic sequence

The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.

Step 1. Record the running path, core, frontend, template package and required node versions, not only the application shell version.

Step 2. Check the tutorial's actual requirements and date to distinguish missing discovery UI from a missing execution class.

Step 3. Back up, then follow this installation type's official component update path without replacing the whole Torch stack for one template.

Step 4. Obtain a workflow from its original template source if needed, then inspect dependencies. A standalone JSON bypasses discovery, not version requirements.

Completion check

Both the template and its nodes are available in the intended instance, and previously working workflows pass a regression check.

Limitations and cautions

Update to latest is not a precise compatibility statement. Automatic compatibility with every future node is not promised.

Original sources

• How to update ComfyUI — original record checked 2026-09-21.
• Install custom nodes — original record checked 2026-09-21.

Localization prepared: 2026-09-22. The source-check dates above were inherited from the existing article; this translation does not claim they were all rechecked today. No GPU run, minimum-memory measurement or runtime guarantee is supplied.

Related troubleshooting and guides

• Back up before updating ComfyUI: a source rollback is not an environment rollback
• ComfyUI missing nodes: distinguish absent packages, failed imports and unregistered classes
• Blank ComfyUI screen after an extension update: separate frontend and backend failures