Sorry Hans,  No issues with VST scan here.
I have had problems in the past where Windows Update failed to apply an update, but completed.  I have had to force Windows updates to get Sonar products to work in the past.  You may want to check your Windows Update logs and look for failed updates.

Short of that, you may need to go through the process that Bob recommended above.

glen

unfortunately, the process of elimination is the only way I can think of to determine what's going on as well.
 
I'd start by eliminating all of the x64 folders and making sure it gets through the x32 ones first.  if it doesn't, then start eliminating there using Bob's suggestion.

@scook : I held the shift key while starting the scan, but a log doesn`t pop up (?)

It has been some time since having the vstscan.exe released with MC7 on my machine. Logging was added to the scanner around July 2015. It is possible the feature did not make it into the scanner bundled with MC7. You could ask support for a newer version of the scanner or get it by loading a demo of a newer product. Demos update all the shared utilities.
 
The approach suggested by Beagle and Bob might be just as fast in determining what plug-ins are the problem.
 
 
 

You mean i should download and install a demo of Sonar? Unfortunately the support takes very long to reply, at least that is my personal experience.

If you do, it will install the latest shared utilities. NOTE: This probably will not solve the problem. I suspect the issue is with some 3rd party 32bit plug-ins or a bad scan path. The methods described above should help you narrow down the source of the problem. Newer utilities may a few bug fixes and the scanner would have the logging feature.
 
In the past, Cakewalk support has supplied updated shared utilities when they though it would help resolve a scanning issue.
 
Avoiding 32bit plug-ins when running a 64bit host is always a good idea.

 Ok, i will give it a try. But since i already ran the scan without the 32bit plugin path, and it did not find most of the 64bit plugins anyway (only a few 3rd party effects, but none of the 3rd party instruments), i doubt that the 32bit plugins are the problem here :-(  What do you mean by bad scan path?

If 32bit programs are not in the path and it still fails then we do not know anything about the 32bit plug-ins.
All we know at this point is some 64bit third party effects and no third party instruments are getting found by the scanner. We have no idea what plug-ins are involved, how or where there were installed. There is no mention of whether the running with the factory defaults works. There are no details provided about the scan path other than it includes more than factory defaults. Examples of bad paths are

• including multiple paths to the same folder (for example C:\folder and C:\folder\subdir would both scan subdir)
• including paths that contain dlls which are not VST plug-ins.

This reads like you`re saying that i did not provide enough info`s for you guys to analyse the problem?

Yes - the multiple things that scook explained about us not having any info on is exactly that - we do not yet have enough information on exactly what your configuration/setup is, so it is really just a guessing game on our part - at the moment.
 
1) Please detail exactly what VST search paths you have specified for the 64-bit install of MC7.
 
2) Please consider that IF a single 32-bit plugin (effect or instrument), OR a dll that is NOT a plugin, are present in any of the folders specified in your VST search path (and this includes all sub-folders to any of those folders) - then you could be going belly up early in the scan and thus not getting anything coming back for your 64-bit scan.  One way around this is to create a new folder - perhaps C:\Program Files\Plugins-Temp or something like that, and just for testing purposes, make THAT folder the only folder specified in the VST Scan Paths for MC7.  Then, take something that you are absolutely SURE is a 64-bit plugin, and do a COPY/PASTE to place a copy of it in the new Plugins-Temp folder, and then run your VST Scan.  If THAT fails, then there really is something quite wrong going on.  It SHOULD work like a champ.  Then, if that works, add a small number of additional 64-bit plugins into that same Plugins-Temp folder and rescan the VST plugins again.  If it works, repeat the process of adding a few, and scanning.  If any one set of plugins ends up to where the scan fails, then one or more of THAT small set of plugins last added to the Plugins-Temp folder is a problem child for some reason.  You can then remove just that last set of plugins, then add them back in one at a time and scan, and repeat, until you figure out which one(s) fail.
 
Eventually, using the above approach, you should be able to build as complete set of 64-bit plugins that work as possible, in that Plugins-Temp folder, and will have not added any failing ones to it.  THEN, you can either replace all the plugins in the path you USED to use, and repopulate that folder from the Plugins-Temp folder, then alter the VST search paths to point just to that original folder again (with its successfully scanned plugins), and be all good to go - with a final scan.
 
The above is a methodical approach, where the ones that work are collected, and no bad ones are allowed to remain there, and at the end, you will have a complete set of plugins that all do get past the scanning process.
 
Bob Bone