Knowledge base › Troubleshooting

Why the output has a demonstration mark

Two causes, easy to tell apart: no key reached the engine, or the key does not cover this platform.

The mark means the engine is running unlicensed. That is a normal state -- it is how evaluation works -- so seeing it after you installed a key means one of exactly two things.

The key is not reaching the engine. Check that it is passed before any document is created, that the string was copied whole, and that the code path setting it actually runs in the configuration you are testing.

Or the key does not cover the platform you are on. A key names the package it was bought for, and the engine refuses it on a platform that package does not ship binaries for. This is the one that catches people who develop on one operating system and deploy to another: it works on the laptop and marks the output in production.

It is never a maintenance problem. A build inside your window stays inside it permanently, so a licence that worked yesterday cannot stop working today.

Last updated 2026-09-09.

Related

• Reading the build stamp in the changelog Each release prints the date its binary was cut. That is the number your licence window is compared against.