Skip to main content
Inspiring
October 30, 2024
Question

VST Plugin Scanner Fails Entirely When Single Plugin Missing/Invalid

  • October 30, 2024
  • 2 replies
  • 396 views

When launching Premiere Pro after the latest update, the VST plugin scanner fails completely if it encounters any single problematic plugin. The scanner provides no option to skip individual plugins and continue scanning, forcing users to either:

1. Cancel the entire scan
2. Locate the missing plugin
3. Remove all references to the problematic plugin


Impact:
- Blocks access to all VST plugins when just one is problematic
- Particularly severe for professional audio users with large VST libraries (500+ plugins)
- Prevents workflow until the issue is resolved


Expected Behavior:
- Scanner should provide a "Skip" button for individual problematic plugins
- Scanning should continue for remaining plugins after skipping
- System should log skipped plugins for later resolution


Steps to Reproduce:
1. Install latest Premiere Pro update
2. Launch application with missing/invalid VST plugin
3. Observe scanner behavior when plugin issue detected


Environment:
- Latest Premiere Pro version [25.0.0 Build 61]
- Windows 11 Pro [23H2]
- Professional audio setup with extensive VST library


Thanks.

PS: When opening menu "Help" ► "About ----" in any Adobe app, copy & paste is deactivated, making it impossible to copy and paste the version number for forum requests. Why on earth would you restrict copy and paste in the about display? Adobe, please stop being sooo UX unfriendly and restrictive... 

This topic has been closed for replies.

2 replies

Community Manager
October 31, 2024

Can you post a screen shot of your Plug-in Scanner so we can see how it is configured?

IanB_360
Community Manager
Community Manager
October 31, 2024

Hi @Red Point 

Welcome to the Premiere Pro forums! We are glad to see you here. We need a few more details to try to help with the issue. Please see, How do I write a bug report ?

And thank you for the already thorough details supplied to us. That will help as I reach out to someone in Audio on the team for researching this issue for you. It does seem like there is something with how Premiere Pro is reading the plugin but I will make sure our Audio team gets this so it can be inspected with greater knowledge and detail. 

Thanks for submitting your bug report. I hope we can help you soon. Sorry for the frustration!

Thanks,

Ian