Lmcq Runtime Model Decryption

This is the simplest of the pack's decryption nodes, and that's not an accident: it only has two fields. Point it at a model encrypted with LmcqRuntimeModelEncryption, give it the matching key, and it hands back the same MODEL/CLIP/VAE trio you'd get from any normal checkpoint loader. No password server, no license code, no network call - it's designed to work entirely offline.

The two fields. model_name is a dropdown of the encrypted checkpoints it finds locally. key is the password the creator set at encryption time - exact match required. That's the whole configuration surface. Notably, there's no machine_codes field here to fill in yourself; if the file was locked to specific hardware at encryption time, that check runs automatically against the machine you're on. If your hardware wasn't on the authorized list when the file was encrypted, decryption fails regardless of whether your password is correct - and there's nothing you can adjust locally to fix that, since the check exists specifically so you can't route around it.

Why this is deliberately the "dumb" option compared to Auth decryption. The pack's LmcqAuthModelDecryption ties into LMCQ's cloud auth server for real-time validation - usage limits, expiration, remote revocation. This node has none of that. Per the README, the tradeoff is what makes it attractive for a certain kind of distribution: the model only ever exists in decrypted form in memory during the run, is never written back to disk unencrypted, and a working internet connection is never required to open it. If you're distributing to people who might be offline, or you don't want your buyers' access to depend on LMCQ's servers staying up indefinitely, this is the more resilient choice - at the cost of not being able to revoke or extend access remotely once you've shipped the file.

Installing it. Through ComfyUI Manager (search "ComfyUI-LMCQ") or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/sebord/ComfyUI-LMCQ

Restart ComfyUI afterward.

Troubleshooting, in the order that actually matches how people get stuck. First: is the node showing up at all? This pack has a well-documented, recurring bug where a compiled runtime module the protection nodes depend on goes missing after install, throwing ModuleNotFoundError: No module named '...runtime.model_protection' at ComfyUI startup. That failure happens inside the pack's shared __init__.py, so it takes down every Lmcq node at once - if this decryption node is missing, check your console for that error before assuming your key is wrong. The pack's January 2026 changelog has the fix: copy the runtime files matching your Python version into the runtime folder, delete the ones that don't match, restart.

Second, if the node loads fine but decryption fails: rule out a mistyped key first (copy-paste rather than retype it), then check the file wasn't corrupted in transfer. If both of those check out and it's still failing, the most likely remaining cause is a machine-code mismatch - the file was locked to hardware that doesn't include yours, and the only fix is asking whoever encrypted it to add your machine code (from LmcqGetMachineCode) and re-issue the file. There's no local workaround for that by design.