Premiere Pro launch failure after major upgrade: automatic plug-in quarantine or manual disable

Premiere Pro does not document whether incompatible third-party plug-ins are automatically quarantined on the first launch after a major-version upgrade or remain enabled until the user opens Plug-in Manager and disables them manually. This matters when the application crashes during playback or effect rendering and the crash log identifies a specific plug-in module without offering an in-app option to disable it.

Assume a major-version upgrade, such as 24.x to 25.x, with third-party effects installed. The user needs to know whether the application isolates the faulty plug-in automatically or requires manual intervention before the next launch. The uncertainty affects recovery time and whether a full preference reset is necessary.

Does Premiere Pro automatically move incompatible plug-ins to a disabled or quarantine folder after a detected crash on launch? If not, which Plug-in Manager setting controls this behavior, and does skipping the manual disable step cause repeated crashes on every subsequent launch?