scook

AAX is a Protools plug-in extension. They are not VST plug-ins. These plug-ins do not get installed by default in the two paths defined in default settings. This begs the question, how did these plug-in get installed under "C:\Program Files\Cakewalk\Vstplugins" and "C:\Program Files\Common Files\VST3?" Were these paths populated using the manufacturers installers or copied from somewhere?

contact support@cakewalk.com

That is good news. The scanner ran to completion but the log does not appear to be a VST reset just a regular scan. The log does indicate there should be 23 plug-ins listed in the VST2 and VST3 folders when using the "Sort by Type" layout. This is progress from the OP and the other scan failure message. Now all you need to do is find where your plug-ins are installed.

A current log from a freshly run VST reset should not contain 1280 DLLs or there will be a similar count of plug-ins listed in CbB. If the scan completes it will be noted at the end of the log. Run a VST reset and generate a fresh log. If the reset does not find your 3rd party plug-ins and you do not remember where you installed them, you can run the installers again and take note of the paths used by the installers. Every plug-in installer lists the paths used by the installer as part of the install process.

If the log indicates the scanner is running to completion. It may be a good idea to run a Reset, the button next to the scan button in preferences. This will clear out the VST inventory in the registry and rebuild it from scratch. May want to create a log for the reset. After a successful reset, Waves support should be able to help get those plug-ins back.

The Sonitus plug-ins are DX format and have nothing to do with the VST scanner. The PC modules should be available. These do get scanned. All 64bit VST3 install by default into C:\Program Files\Common Files\VST3. They should be there. It is up to you to know where 3rd party VST2 plug-ins installed. A few possibilities have been mentioned above. By default, Cakewalk installs the few VST plug-ins bundled with it into C:\Program Files\Cakewalk\Vstplugins What does the scan log show now?

Set up the scan path in preferences EXACTLY like the image shown in the help. Run a scan and we can deal with anything else later.

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.