Question

My ideal workflow is to disable the start-up scan and simply do a manual scan after installing, updating or removing a plugin. Most of the times that works well, but the manual scan doesn't see some changes, like a removed dll. Another clear indication that they are not the same is that a new Waves plugin can only be detected/activated with the startup scan. So you have to start the program, change the setting to activate the scan, close the program, start again and remember to deactivate the can again afterwards.

This is a PC issue. I don't know if it also plays on the Mac. I know from a Facebook discussion that more people have encountered this issue.

It can easily be solved if both scans use identical code.

Answer 1

Thank you for the feature request. 

If anyone else agrees or disagrees, please VOTE!

The developers pay close attention to those that are voted on the most. 

You are allowed one vote. You can change your vote later if you choose.

(Here's some helpful info on how to use the voting system)

Please vote the original question / feature request. 

Please DO NOT Vote on THIS response!