Troubleshooting

"This computer is not activated"

Open the Litesum Launcher and sign in. It activates the computer once, and every Litesum application shares that activation. Litesum Enhance cannot sign you in itself — that is the Launcher's job, and keeping it there is what makes the two-computer allowance count computers rather than installations.

Everything already enhanced can still be viewed and exported. Nothing is deleted, locked or watermarked.

"The subscription needs re-checking"

Your computer has been offline longer than the licence allows. Connect to the internet and press Check again. If it still fails, open the Launcher.

Setting the clock back does not extend the offline period, and will produce this message.

Enhance is greyed out

Three possible reasons, and the status bar always says which:

1. No image is open.
2. The job is too large. The Output section shows why and names a scale that will work.
3. This computer is not activated, or the subscription needs attention. See above.

It says "CPU (Classical)" instead of a graphics card

Enhancement is running on the processor, which works but is roughly twenty times slower — and if it says Classical rather than CPU (ONNX Runtime), the AI models are not loading at all and you are getting a conventional resize.

This should now fix itself: at every start the application checks its AI models, rebuilds the record from files already on your computer when it can, and downloads only what no local file can supply — you will see the progress in the status bar. Photographs keep working either way: at 2× they use the faithful classical method by design, and at 4× — where they normally run Litesum's fidelity-trained network — the classical method stands in until the model is restored, clearly labelled as such in the result.

If it still reports a problem, open About and press Check models. It will tell you whether a model file is missing or damaged and offer to repair it — trying the local rebuild first, downloading only if that cannot help.

If the models are fine and it still uses the processor, your graphics driver may not support DirectX 12. Updating the graphics driver is the usual fix.

The result looks worse than the original

Look at 100 %, not Fit. At Fit everything looks good.

Then check the image type. The most common cause is a photograph being processed as Low Resolution, which is deliberately assertive, or artwork being processed as a photograph. Turn off Choose settings automatically and pick the type yourself.

If it is a photograph of dense foliage, fur or a clear sky, you may be running into a genuine weakness rather than a setting — see what Litesum Enhance can and cannot do.

Small text came out unreadable

Expected, and unavoidable. Letters are enlarged, not read. If the strokes are below about two pixels in the source there is nothing left to reconstruct from.

The enhanced image looks slightly different in colour

Check the Colour profile line in the Image panel. If your source had an embedded profile it is preserved, and an application that ignores profiles will show it differently from one that respects them.

An image in a batch failed

Open the report in the destination folder. Each failure is listed with its reason. Common ones: the file is not a valid image, the format is not supported, or the job needed more memory than was free.

Out of memory

Litesum Enhance refuses jobs it cannot finish, so this should be rare. If it happens, close other applications and try again, or use a smaller enlargement.

Memory needed grows with the square of the enlargement: 4× needs four times what 2× does, not twice.

Sending a diagnostics report

About → Copy diagnostics. It contains your operating system, processor, memory, graphics backends, installed models and their state.

It contains no image data and no file names from your work.

Windows says the publisher is not recognised

The installer is not yet code-signed; a certificate is being obtained. Until then, check the SHA-256 of your download against the one published beside it.