You updated ComfyUI, probably to chase one of the new video models, and now your LTXVideo nodes are gone. Maybe the loader node is simply missing from the menu. Maybe you get a loading error on startup, or an unknown model complaint pointing at a LoRA that was working yesterday.

You did not break your install. This is a dependency conflict, it has a one line fix, and it has been quietly eating people’s evenings since June.

What is actually happening

Updating recent versions of ComfyUI pulls a library called kornia forward to version 0.8.3. The LTXVideo node pack cannot import against that version, so the whole pack fails to load. Because the failure happens at import time rather than when you run something, the nodes do not error. They just are not there.

That distinction is why it is so confusing. A node that throws an error tells you where to look. A node that never registers looks like you installed something wrong.

The GitHub issue is open, and its title does not mince words: “You broke ComfyUI-LTXVideo and countless other nodes by forcing the update to Kornia 0.8.3.” It was filed on 5 June. It is still open now.

The fix

In the Python environment your ComfyUI actually uses:

pip uninstall -y kornia
pip install kornia==0.7.3

If you run a portable install, use the embedded Python that ships inside it rather than whatever pip your terminal finds first. Getting the wrong environment is the most common reason this appears not to work.

Restart ComfyUI and the nodes come back.

The part nobody mentions

Rolling kornia back to 0.7.3 works, and it is not free.

Kornia 0.7.3 was released in June 2024. Version 0.8.3 came out in May 2026 and is still the current release. So the fix asks you to sit on a version of that library that is roughly two years old, along with everything that has been fixed in it since. For a machine whose job is running video models that is usually an easy trade. It is still a trade, and you should know you are making it rather than discovering it later.

Why it is biting people this week

The issue is three months old, but the pain is fresh, and the reason is that a lot of people are updating ComfyUI right now to run the newer video models. Updating is exactly what triggers it, so an old bug is meeting a new wave of users.

We ran into this ourselves in the middle of August while benchmarking LTX-2.5, and published the pin in that write-up at the time. We are not claiming we found it. The issue predates our bench by two months and other people were there first. What we can tell you is that it is real, it is reproducible, and the fix above is the one that worked on our machine.

The wider habit worth stealing

The reason this cost us an afternoon rather than a week is that we were not testing on the install we depend on.

Our production ComfyUI kept rendering the entire time. The bench ran in a completely separate install, on a different port, with the model folders shared by junction so nothing was duplicated on disk. When the new node pack turned out to need pinned dependencies and refused to run our older graphs, none of that touched the machine that publishes a video every morning.

If you have a setup that people rely on, or that you rely on to get something out on schedule, do not upgrade it to try something. Stand a second one up next to it. Disks are cheaper than a broken pipeline on a deadline, and this dependency conflict is a perfect example of the kind of thing that has nothing to do with your skill and everything to do with which directory you ran the update in.

A daily note from our news radar. The week gets the full treatment in the DIY AI Brief every Monday.