Bug: VST3 Scan progress is lost on app restart / PC reboot

Replies

• SoyNoisAuthorOct 28, 2026#2

  Hi! Just to clarify, I was already using the latest version of Patchd when I did the clean test and found these issues: 1. Waves Bug: Without Waves, Patchd saves the plugin scan progress perfectly. When Waves is installed, the plugins work, but they break the saving process on shutdown, wiping the VST3 scan history so it forces a full rescan on the next launch. 2. PatchWork Bug: BC PatchWork loads, but its GUI (plugin window) won't open, so it can't be used.

  👍0👎0
• PatchdOct 28, 2026#3

  With Waves installed, Patchd isn't keeping the VST3 scan list between launches, so every relaunch or reboot scans from scratch, while without Waves the list is kept. Thank you for the information, that helped. We've found two ways the list can be lost when Waves is installed, and we're fixing both for the next update.

  To confirm which one you're hitting:

  1. Run a plugin scan and wait until Patchd says it's finished. 2. Close Patchd and open it again. 3. Right away, go to Settings > Beta: Send Report and send one.

  Also tell us here whether Patchd seemed to keep disconnecting and reconnecting after you reopened it.

  BC PatchWork loading but its window not opening is a separate problem. The next update also makes Patchd log why a plugin's window doesn't open, so we can see what PatchWork is doing there.

  👍1👎0

  • SoyNoisAuthorOct 28, 2026#4

    Hi! I've followed your instructions, but I can't find the **Settings > Beta > Send Report** option.

    In my Settings, I only see the community section under Get Help, where I can post questions with the topic set to Beta. There doesn't seem to be a separate option to send a diagnostic report. Could you please let me know if there's an alternative way to send it?

    Here is the feedback from my testing:

    1. Patchd itself works perfectly. It doesn't disconnect or reconnect when reopened.

    2. When the complete Waves bundle is installed, none of the plugins open, either before or after restarting Patchd. After rebooting the computer, WaveShell appears as "(missing)" and the dropdown list is completely empty.

    3. Interestingly, when I install only standalone plugins (WLM Plus, Playlist Rider and DeEsser), they open and work flawlessly every time, even after restarting Patchd or rebooting the computer.

    Thank you guys for your help! I really appreciate it.

    👍1👎0
  • PatchdOct 29, 2026#5

    Your retest showed us exactly what's wrong. A Waves bundle keeps all of its plugins inside one file, the WaveShell, and Patchd remembers a plugin only by its file. So every Waves bundle plugin looks like the same plugin to Patchd, and loading one tries to open the whole bundle, which takes too long and never finishes. That's why none of them open, while the standalone ones (WLM Plus, Playlist Rider, DeEsser) each have their own file and work.

    The empty list and "(missing)" after a reboot come from the scan: scanning a whole WaveShell takes minutes, and Patchd only saved the list once a full scan finished.

    The next update fixes both. Patchd will remember each Waves plugin inside the bundle and open only that one, and it saves scan progress as it goes, so a restart keeps what was already scanned. There's nothing you need to do until then.

    About Send Report: it's only available to accounts in the US, which is why you don't see it. We suggested it before we knew where you were. You don't need it for this one. What you've told us is enough to fix the Waves problem.

    BC PatchWork is different. Its window opens on our machines, so we don't have enough yet to fix it. The next update makes Patchd record what happens each time it asks a plugin to open its window, to help us track it down.

    👍1👎0