The add-on doesn't appear in CorelDRAW

CorelDRAW scans a plugin folder at startup and loads whatever it finds there. If nothing shows up, the file is not in the folder CorelDRAW is actually reading — or CorelDRAW never restarted.

How loading works

There is no registry entry and no service. On startup CorelDRAW scans its own Draw\Plugins64 folder (or Plugins for the 32-bit X-series) and loads every .cpg it finds. Two consequences:

The file has to sit in the folder of the version you are running. Installing into 2021 does nothing for a 2020 session.
CorelDRAW reads the folder once, at launch. Installing while CorelDRAW is running changes nothing until you restart it.

Three checks, in order

Restart CorelDRAW fully. Closing the document window is not enough — quit the application.
Confirm the version. Help → About. Then look at which installer you ran. A mismatch here is the usual answer.
Look at the folder. Open C:\Program Files\Corel\CorelDRAW Graphics Suite <year>\Draw\Plugins64. You should see dtzCdrPlugin.cpg and a dtzCdrTool folder next to it.

Portable & trimmed installsGreen/portable builds and some cut-down editions ship without a writable Plugins64 folder, or with the folder in a different location. Run the installer, note the path it reports, and confirm that path belongs to the CorelDRAW you actually launch — not to an older copy still on the disk.

More than one CorelDRAW installed

Very common on shop machines: 2019 from years ago, 2023 added later. They have separate plugin folders. Installing for 2023 and then double-clicking a shortcut that starts 2019 gives you exactly this symptom. Check the title bar of the running window, or Help → About, before assuming the install failed.

If the file is there and it still fails

An antivirus may have quarantined the .cpg. Check the quarantine list.
Windows may be blocking the extracted files. Right-click the installer → Properties → Unblock, then reinstall.
If a previous version is half-removed, see Uninstall and reinstall.

Still nothing

Send us the folder path, the exact version from Help → About, and the installer filename you ran. With those three we can usually tell you the cause in one reply.