Fix a Cropped iZotope RX Window in Adobe

If an RX plug-in opens in Premiere Pro or Audition but half its controls are cut off, save your work, quit Adobe and test a fresh RX instance with the affected Windows display set to 100% Scale. This has helped RX 11 users, but it is a workaround to test on your system, not a confirmed universal RX 12 fix.

The return step matters. An Audition user restored normal scaling while Audition stayed open and said the problem returned after quitting. A separate Premiere user reported success after a resolution-change and restart sequence. Do not combine those reports into a promise that one reset permanently repairs both applications.

Confirm that the controls are cropped

The relevant symptom is a plug-in that appears in the effects list and opens, but its internal interface is clipped. Enlarging the surrounding window reveals empty space instead of the missing buttons. Compare a screenshot of the entire host frame with the controls you cannot reach.

An April 2025 Premiere report describes RX 11 Repair Assistant cropping after an upgrade from Premiere Pro 24.6.3 to 25.2.3, build 4, on Windows 11. A May 2025 Audition report describes partial rendering of RX 11 Advanced Voice De-noise in Audition 25.2.0.123. These establish reported symptoms on those versions, not a measured failure rate or a diagnosis for every newer build.

If RX is absent from the effects list, start with the RX plug-in discovery guide. If Adobe closes or hangs when loading it, use the RX crash troubleshooting guide. A blank panel, disabled controls and a cropped interface can require different investigations.

Try the Windows 100% Scale sequence

Use a small test project or a saved project copy. Keep the production effect instance intact: a new instance may not inherit its preset, learned noise profile, routing or automation.

1. Save the work. Save the Adobe project or Audition session and any modified audio files. Keep the original project and media available.
2. Record display settings. Note the affected monitor, its resolution and its Scale value before changing anything.
3. Quit the Adobe host. Close Premiere Pro or Audition normally, including other projects open in that application.
4. Select the affected display. Open Windows Settings > System > Display and select the monitor where the RX window will open.
5. Set Scale to 100%. In Scale & layout, temporarily select 100% Scale. Leave the display resolution unchanged for this first test.
6. Open one test instance. Launch Adobe and load the affected RX VST3 in a small test project or saved copy on that monitor.
7. Check visibility and interaction. Confirm that the missing controls appear and that the pointer operates the control it is over. Test playback and bypass on expendable audio.
8. Restore and observe. For the Audition session workaround, restore the original Scale while the host remains open, then check RX again. If it fails, restore a usable display setup and use a fallback.
9. Check the next launch separately. After saving, close and reopen Adobe when convenient. Record whether cropping returns; a working current session does not prove a permanent fix.

Microsoft's display-settings instructions confirm the path and per-display selection. Microsoft normally recommends the recommended scale; 100% here is a temporary diagnostic and may make text too small to use comfortably.

What the Audition workaround actually proves

In the RX 11 De-click discussion, a Windows 11 user reported that 100% Scale stopped the cropping. The original poster thanked them but did not confirm a successful retest in the visible replies. That is one reported result, not a verified fix for everyone in the thread.

In a separate RX 11 Audition discussion, a respondent described changing 125% to 100% before launch, opening a plug-in and returning to the original scale without closing Audition. They said the benefit disappeared when Audition closed. The original poster had instead switched to the Audio Editor.

If the controls return at 100% but disappear after restoring your preferred scale, stop there and note both outcomes. Do not leave an unreadable desktop in place just to satisfy the test. The useful result is a reproducible display dependency that support can investigate, even when it does not give you a comfortable working session.

Why launch order and monitor choice can matter

Microsoft's explanation of desktop DPI handling describes how display changes can leave applications incorrectly sized unless their interface responds appropriately. It identifies mixed-scale monitors and changing scale during an application's lifetime as relevant scenarios. It does not establish which component causes a particular RX/Adobe fault.

A clean host launch makes the scale test easier to reproduce; it does not prove that a particular cache was cleared. Closing only the RX window may leave the host running. Save and quit normally before the initial test, rather than ending background processes or deleting preferences.

With multiple monitors, begin on the display selected in Windows Settings and keep both Adobe and the test plug-in there. Record each screen's scale and resolution. If cropping occurs only after moving the plug-in to another screen, include that transition in the support report. Matching display scales is an optional comparison, not an established RX cure; restore the original arrangement afterward.

Premiere fallback: test a temporary 1080p desktop

The Premiere reporter described a different sequence: quit Premiere, change a 4K desktop to 1920 × 1080 and return magnification to normal, launch Premiere and load RX 11, then quit again, restore the original display settings and relaunch. They reported a complete interface afterward. This is evidence for that user's RX 11 setup, not proof of persistence on RX 12.

Try this only if the simpler scale test fails and 1920 × 1080 is offered by your display. Change the Windows Display resolution, not your Premiere sequence dimensions or Program Monitor playback resolution. Keep the original desktop settings recorded and return to them after the test.

A lower resolution can soften or stretch text and add borders, as Microsoft explains. If the workaround works only at the temporary setting, use it only while the screen remains comfortable and usable. A different repair route is preferable to repeatedly rearranging a production desktop without a reproducible benefit.

Check versions without assuming an update fixes this bug

The RX Standard release notes, checked September 5, 2026, list RX 12.0.0, released April 28, with Adobe Premiere Pro 2026 and Audition 2026 among supported hosts. They list Windows 11 24H2 and 64-bit VST3 support. That compatibility list does not certify every display arrangement.

Historical entries are more specific: RX 11.2 added Windows HiDPI support; RX 11.3 fixed a clipped Export Screenshot window; RX 11.4 fixed a plug-in-module GUI issue inside the RX app. None of those statements says that all cropped Adobe plug-in windows are fixed. The Ableton Auto-Scale Plug-In Window note is also host-specific; do not search Premiere for an Ableton menu command.

Compare your exact installed builds with the vendor's current supported releases. Preserve presets and a working project copy before testing an update, and change one application at a time where practical. Opening an old project in a newer host should be a controlled test, not your only remaining copy.

Check Adobe's issue scope, including Windows ARM

Audition's known-issues page documents flickering and glitches when resizing an effect window on Windows ARM devices. That is a specific platform report, not confirmation that every RX crop on an Intel or AMD PC has the same cause.

Premiere's known and fixed issues should likewise be read against the exact symptom and build. A fix for a video panel, a media browser or an unrelated plug-in crash does not establish an RX interface fix.

The Windows Scale steps do not transfer directly to macOS. For a Mac failure, record the macOS, Adobe and RX builds, display arrangement and plug-in format, then test a saved copy with supported versions. The Windows user reports alone cannot validate a Mac-specific scaling recipe.

Maximize Frame is a different control

Premiere's panel-maximizing instructions enlarge the panel under the pointer. Use the assigned Maximize or Restore Frame command; the key can differ with keyboard layout.

This can help if the Adobe panel itself lacks room. If the outer frame grows but the RX drawing remains clipped, repeated dragging is not revealing more of the interface. Return the panel to its previous size and continue with the display test. Program Monitor zoom and video crop effects address the picture, not the audio plug-in's controls.

Rescan only when discovery needs attention

Audition's plug-in manager documentation covers scanning, enabling valid effects and reloading an entry marked Not Working. It also describes rescanning existing plug-ins after an update. Those are legitimate discovery tasks; they are not documented as a cropped-canvas repair.

If an RX instance already opens, preserve that evidence before reinstalling or resetting anything. If a maintenance update leaves RX missing, handle that separate scan problem and then retest its window. Avoid changing the plug-in format, project, display settings and installation together, because you will not know which change mattered.

Use Premiere's exposed parameters cautiously

A participant in the longer Adobe RX discussion reported adjusting exposed parameters in the Audio Track Mixer despite the cropped vendor interface. Treat this as an emergency option for controls that are actually available, not a guarantee that every RX control will appear.

Adobe's track-effect instructions show Window > Audio Track Mixer, Show/Hide Effects and Sends, effect selection and parameter adjustment. Available parameters depend on the effect. A track insert affects audio passing through that track, so test on a dedicated track or project copy and avoid duplicating processing already applied to the clip.

Without the vendor's full display, do not guess at hidden learning or monitoring states. Make small changes, compare bypass at similar perceived loudness and listen through the result. If a necessary control is inaccessible, choose another route rather than approving a repair you cannot inspect.

Move a protected audio copy to RX Audio Editor

The standalone Editor requires RX Standard or Advanced; RX 12 Elements provides plug-ins. If you own Elements only, use a working host or an available Adobe effect for the immediate job, or pause that repair until the interface problem is resolved. Installing the same edition again does not add the Editor.

The current RX Connect manual separates Premiere's external-file workflow from Audition's Connect workflow. Its Premiere example reveals the source file and overwrites it after editing. For this display problem, work on a separate audio-file copy instead. A duplicated timeline clip may still reference the same original media.

Export or copy the intended audio with enough surrounding material to check transitions. Preserve its timing, sample rate and channel layout. Open that copy in RX, turn Instant Process off before selecting, preview the necessary repair and undo test renders before applying the final processing once. Return removed-signal monitoring to normal output if the chosen module provides it.

Use File > Export to write a new audio filename. Save overwrites an open WAV or AIFF; an RX Document preserves editing history but opens only in RX. Place the exported audio at the correct position in a project copy and avoid applying the same restoration twice. Listen through the full returned file and sequence for sync, channels, peaks, fades and missing audio before delivery.

The Editor and plug-in workflow comparison helps choose the route. For normal clip and track integration, use the RX workflow in Premiere guide; a window workaround should not become the entire editing process.

Keep a useful result log for support

Record the exact RX edition and version, Adobe build, operating system and processor type, plug-in format, GPU/driver, monitor resolutions and scales. Include the full host frame in the screenshot, plus whether the pointer reaches the visible controls and whether playback works.

Separate three results: the initial launch at 100%, restoration of normal scale within the same session, and a later host restart. Add whether a fresh instance and an existing instance behave differently. This is more useful than reporting only that the window is cut off.

Keep saved projects, original media and original display settings available. Stop repeating a test that changes nothing. No registry edit, new Windows account or broad preference deletion is needed to establish these results. The Fix iZotope RX hub routes failures outside this specific interface problem.

Frequently asked questions

Why does RX show only half its window in Premiere Pro?

RX 11 users have reported an interface that stays cropped while the host frame resizes. Display scaling is a useful diagnostic, but those reports do not establish one confirmed cause for every RX and Adobe build.

What should I try first on Windows?

Save your work, quit Adobe, record the affected display's settings and temporarily set its Scale to 100%. Reopen the host and test one RX instance in a small project or saved copy.

Should I close Audition before restoring normal scaling?

The reported Audition session workaround restored normal Scale while Audition remained open. That user said cropping returned after quitting, so test the next launch separately rather than assuming the change is permanent.

Should I change my screen resolution?

Try Scale first. A Premiere RX 11 user reported success with a temporary 1920 × 1080 desktop and restart sequence. Use it only if the display offers that resolution, and restore the original settings afterward.

Will maximizing the Adobe panel reveal the missing controls?

It may help a panel that is simply too small. If the host frame grows while the same RX controls remain clipped, panel maximization has not corrected the internal interface.

Should I rescan the RX plug-ins?

Use scanning for a missing, disabled or failed plug-in, or when an update requires discovery again. It is not a documented fix for an RX interface that already opens but is cropped.

Can RX Elements use the standalone Editor fallback?

No. RX 12 Elements supplies plug-ins; the standalone Audio Editor is included with Standard and Advanced. Elements users need a working host or another available repair tool.

Is the 100% Scale workaround a confirmed RX 12 fix?

No. The specific success reports cited here concern RX 11. Test the same symptom on your actual RX 12 and Adobe builds, and record the current-session and restart results separately.