RX problems: installs, authorization, missing plugins, crashes

Start with the symptom: RX will not open, a plug-in is missing, playback is silent, or repaired audio never returns to the DAW. Record the RX version and edition, host, operating system and exact error. Protect the original audio and recoverable edits before changing installation or recovery settings.

Separate installation from authorisation

The right installation route depends on the licence. Native Instruments documents serial registration through Product Portal, while current iZotope subscriptions use Native Access. A product missing from one manager does not establish that its licence is missing. Use the installation and licence guide to distinguish download, installation, entitlement and activation problems.

Check the RX 12 authorisation instructions for the message you actually see. A trial or demo restriction deserves a licence check; it does not explain every silent output or failed launch.

Find the right plug-in and host route

First confirm that the requested tool exists as a plug-in. The RX module and plug-in tables are separate: owning an Audio Editor module does not guarantee a DAW version. Elements contains six plug-ins without the Audio Editor; Standard and Advanced include the editor.

Then match the format to the host and inspect its installation, scan and validation results. The AU, VST3, AAX and ARA guide maps those routes; the missing-plug-in checklist covers discovery. ARA has its own host and placement requirements, so use the Spectral Editor ARA troubleshooting guide for that integration.

For a failed round-trip, identify whether the host uses RX Connect or an external audio editor. The Connect manual distinguishes Reference, which cannot send audio back, from Repair. A successful transfer still needs the host-specific commit step. Follow the RX Connect checks before assuming a partial update caused the failure.

Diagnose silence, crashes and slow work separately

If RX opens but stays silent, use the playback checklist to separate file and transport problems from the output device, driver and routing. The RX Monitor manual explains the specific case where a DAW holds the audio driver: Monitor routes editor playback through the host. It is not a repair for every no-audio problem.

For a failed launch, follow the startup and crash guide. Session data supports undo and session recall, so preserve recoverable work before clearing it. For sluggish work, distinguish display drawing, playback and processing: the Preferences manual describes different controls for each. The performance guide helps choose a targeted test. A cropped interface in Adobe belongs to the window-scaling guide, not automatically to the crash branch.

Check compatibility before making changes. Test one adjustment on a protected copy, record its result and keep the least disruptive solution that works. The linked guides provide the host-specific steps; this hub helps choose where to start.

RX troubleshooting questions

Should I reinstall RX when a plug-in is missing?

First confirm that the tool has a plug-in version, that the host supports its format, and that installation, scanning and validation succeeded. An editor-only module will not appear merely because you reinstall it.

Does every iZotope licence use Product Portal?

No. Serial registration instructions use Product Portal, while current iZotope subscriptions use Native Access. Check the licence and installation route before treating a missing entry as lost ownership.

Why can I send audio to RX but not return it?

Reference mode is one-way. Repair mode supports a return, but the host still needs its own commit step. Confirm the supported host workflow before treating the problem as an installation failure.