VST Scan does not work

Try running the scanner from MC7 Preferences > File > VST Settings. Since you have been using all 32bit plug-ins in the past, make sure where possible to have the 64bit versions installed. How far does the scanner get before crashing? Are there any messages associated with the crash. If it is having trouble with particular plug-ins, move them out of the scan path. Are there paths other than the defaults in the scan path? To create a log hold the SHIFT key while starting the scanner. It may provide some useful information.

The paths are shown above the scan button in preferences. The default entries are:
c:\program files\cakewalk\vstplugins
c:\program files\common files\vst3
 

when you install new plugins, it really helps to pay attention to where the installer wants to put the files.  If it gives you the option to choose the destination, be sure to put it where your scanner is already looking.
 
If it's 64 bit and you have 32 bit plugs in it's scan path, it will not find anything.

I would think that it is dying very early in the scan process - usually a VST scanning crash indicates a bridging issue, where for some reason one or more of the 32-bit plugins are failing during the scan's query of each plugin - as it asks each plugin to basically identify itself and to supply some basic info back to the VST Scan utility.
 
You could try temporarily copying off the current list of search paths (so you know what to restore later, potentially), and create a new folder that you can make be the only path searched, and very slowly copy a small number of plugins from the original paths into this new folder, and slowly work your way through adding a couple of plugins at a time into that folder and then scanning, and if it works then add a few more plugins and scan again, and repeat this until you get to one that is failing, and leave that one OUT of that folder and keep on working through the rest of the plugins.
 
At the end of the above process, you will have a folder that contains only those plugins that do NOT crash the VST scan, and more importantly, you will have identified all of the plugins that DO crash the scan process.
 
Then, you can take those identified as failing OUT of the original scan paths, and recreate the original search paths for the scan, and it should now work, because any that caused the failures are no longer present in your search paths.
 
If it wasn't 3:30+ in the morning, I could likely have greatly simplified the comments above, and made it easier to follow.  Hopefully, you will make sense of what I tried to explain.
 
It may be possible that there are perhaps new and improved versions of whichever plugin(s) fail, OR that there may be 64-bit versions of those plugins available, where you could end up with working versions of these plugins to complete your ending up with a complete set of plugins that work in 64-bit operation.
 
Bob Bone
 

Guys, is nobody out there ,who has a solution for this? I need your help !

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.

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.
 
 
 

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.

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.

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