scook

I suspect there may be plug-ins in other locations but would like to get the defaults set up first then deal with the other locations once CbB and the scanner function normally.

That is correct. These are the default entries that point to specific folders under C:\Program Files. C:\Program Files\Cakewalk\Vstplugins is the default path setup in CbB for VST2 plug-ins C:\Program Files\Common Files\VST3 is the path defined in the VST3 specification for 64bit VST3 plug-ins. The problem in this image is "C:\Program Files." This causes the scanner to dive down through every folder under this path trying to load every dll it finds. Most of the files are not VST2 or VST3 plug-ins and will cause all kinds of problems for the scanner. Aside from causing the scanner to load VST2/3 plug-in related files, it causes the scanner to scan all other folders in the scan path that are under "C:\Program Files" multiple times. This too can cause problems. If you want to get CbB usable again, start by changing the VST settings back to the default values in preferences.

They are in the track inspector (Q in the image below)

The problem was caused by having "C:\Program Files" in the scan path. That makes the scanner go through everything in "C:\Program Files" loading every dll it finds. Set the scan path in preferences to look just like it does in the help with the addition of "C:\trigger_2_r112_win" if that contains a plug-in dll. Then run a scan.

I am sorry this makes no sense. The logs are created by the vstscan.exe while performing a scan. The log details all the plug-ins the scanner tried to load and the results of the load. If the scanner ran to completion, it will indicate the results of the scan at the end of the log.

The second path "C:\Program Files" is most definitely a problem. That should never be in the scan path. I have no idea what "C:\trigger_2_r112_win" contains. It could be a problem. Uncheck the Re-scan options Also you should be running the scanner from preferences not from the Plug-in Manager.

For the iLok plug-ins make sure the Pace serviice is running To find the offending dll, It may the the last on in the log If it is not in the log, one way to isolate scan problems is by removing all the folders from the scan path and adding the back until the problem reappears. For example, assuming the default scan path C:\Program Files\Cakewalk\Vstplugins 1) rename this path 2) create a new empty C:\Program Files\Cakewalk\Vstplugins 3) move 1/2 the contents of the old C:\Program Files\Cakewalk\Vstplugins (now renamed) into the new C:\Program Files\Cakewalk\Vstplugins 4) run the scanner if the error shows up move 1/2 the contents of C:\Program Files\Cakewalk\Vstplugins back to the old C:\Program Files\Cakewalk\Vstplugins (now renamed) repeat step 4 If the scan runs error free repeat steps 3 and 4

No, the zip extracts into a folder containing the installer, readme and a couple of extra folders of stuff.

The Pace software should launch when the PC starts up. If you are having trouble with iLok see https://www.ilok.com/#!resource/windows_troubleshooting The iLok License Manager comes in a zip file called LicenseSupportInstallerWin64.zip. It is available on https://www.ilok.com/#!license-manager

Contact support@cakewalk.com

This shows the run as administrator setting on the context menu and permanent setting in the Properties Compatibility tab but not sure why this is being discussed. No plug-in should be trying to load a driver. Usually drivers are started when the OS starts up or a piece of hardware is attached. Time would be better spent trying to isolate the dll that generated the error, validating the scan path and running/reviewing the scan log.

I suspect the most recent error is not a permission problem but a scan path issue. It is possible to run CbB as administrator if you wish. The setting in on the CbB icon context menu (right-click the CbB icon). It may be permanently set on the Compatibility tab of the context menu.

Usually more than enough to run CbB and the VST scanner. There are some users who must run as administrator (a higher setting) in order to use XP era plug-ins that write to protected parts of the registry or plug-ins, such as those created using synthedit, that write to areas of the HD which require elevated privileges.

Is the scanner trying to load dlls that are not VST plug-ins? This can cause all kinds of problems. May want to verify the scan path contains only VST binaries. Other types data in the scan path are OK but unexpected dlls can be trouble. Also may be a good idea to generate and review scan logs. The log setting is in preferences.

It is possible with a little registry work to scan as many or as few plug-ins as one wishes as long as the plug-ins are native VST2/3 plug-ins. It may not be possible with plug-ins like the ones from Waves because of the way they are implemented and copy protected. There is no way to avoid scanning all Waves plug-ins when the license count or plug-in shell changes. It is just a matter of editing the scan path and VST Inventory areas of the registry and merging the new data with the original entries.

deselect "Preview at Host Tempo" in the Browser menu on the Media tab (B in the image below)

Not sure if retaining this installer after the next production release has merit. It is not production and may only be applied to 2019-07 build 70.

If you save installers and in this case it is easy because the installer is a direct download, the full version number is part of the installer name. In this case the installer is Cakewalk_by_BandLab_Update_Setup_25.07.0.72.exe. This is the installer for Version: 2019,07 (Build 72, 64 bit) where 25.07 refers to the version and the trailing 72 is the build.

It is a little difficult to reply without knowing exactly what the error messages say. If the messages provide an option to enable the plug-in regardless of the condition it should be OK to do so. At least, I cannot recall a time when I took the enable option and experienced a problem with a "known good" plug-in like TH3. There are a couple of things which one can do to make the scan process more robust. Make sure both "Rescan Failed Plug-ins" and "Rescan All Plug-ins" in preferences are not checked. These are disabled by default and should stay that way unless trying to resolve a specific problem. Once resolved, the options should be immediately turned off so that they do not interfere with future scans. Plug-ins only need to be scanned once. Make sure "Scan in Sandbox" is enabled. Prior to having this feature, it was common for scanner to report problems scanning plug-ins. Often the problem was caused by a plug-in or plug-ins corrupting memory prior to the one reported the problem. The "Scan is Sandbox" was added to address this issue. This option is also on the VST Settings preference page. If the problem persists, it may be helpful to post the scan path as shown on the VST Settings preference page.

IOW temporarily uncheck Allow Only One Open Project at a Time

The following themes have been updated for 2020.04 Tuncury Tuncury Light Green Mercury Light Green All may be found on my Google page. Edit: modified for 2020.04

The image is too small to be really useful. The forum resizes uploaded images. Please do not upload large images to the forum. Instead use an image server (ex. imgur.com) and embed links in posts. Linked images are not resized and do not count against the per-user 50MB image quota. The issue mentioned in the OP may be the result the synth set to Enable MIDI Output (see image below, this is the default for synths that generate or pass through MIDI) and Always Echo Current MIDI Track being enabled (I believe this is the default). If DrBeat was made with Synthedit like other plug-ins made by this developer, it is running in BitBridge so, the standard header is in a second window. To open the standard header for 32bit plug-ins, hold down the ALT key when inserting the plug-in or opening its UI. Usually the header opens behind the plug-in UI. If it is a SynthEdit plug-in, finding a replacement plug-in is a good idea.

Apology noted but your assumption is wrong. There are better ways of handling this too.

Of course there is, hardware, audio interface and OS seem like the basic info support may need to know.