Just curious if anyone else is seeing these msg's in Win7 64bit Event Viewer?

I got this machine around March 2012 and I never saw this Event Viewer Error until I installed my first Waves Plugin on 8/10/12. Now I have hundreds of them and wondering if it may have somethings to do with the issues I have been having with Waves.

It is in the Error Section and it is an Event 35 SidebySide:

Activation context generation failed for "C:\Program Files (x86)\Waves\Applications\wlc.exe".Error in manifest or policy file "C:\Program Files (x86)\Waves\Applications\WavesQtLibs_4.7.3_Win32_Release\WavesQtLibs_4.7.3_Win32_Release.MANIFEST" on line 8. Component identity found in manifest does not match the identity of the component requested. Reference is WavesQtLibs_4.7.3_Win32_Release,processorArchitecture="AMD64",type="win32",version="1.0.0.0". Definition is WavesQtLibs_4.7.3_Win32_Release,processorArchitecture="x86",type="win32",version="1.0.0.0". Please use sxstrace.exe for detailed diagnosis.

I am just guessing but it appears that it is due to the fact that I am running a 64bit OS and 64bit Sonar but Waves does not have a 64bit component that this is looking for????

I really am trying desperately to get my Waves issues fixed so I can use what I have purchased. Not even sure if this error is a problem but thought I would see if anyone else see's this error.

Kind regards,
Rick

I haven't noticed this error, but I remember having an issue where VST Scan would hang on the 32-bit version of the Waves .dll file.  I didn't need the 32-bit versions of Waves plugins, so I simply moved that .dll file from the 32-bit folder (C:\Program Files (x86)\vstplugins) into a temp folder (not one in the scan list) and the problem went away. 
 
Since your issue seems to involve the 32-bit versions, you might want to try something similar, assuming you won't be using them.  I hope this helps!
 
Cheers,
Eddie

Hi Eddie TX,

Thanks for the reply. I don't have any of the 32bit folders in my scan paths so not sure why it would look at those?

I do know that Waves puts both 32bit .dll and 64 bit .dll individual plugs in a bundle file that I wouldn't know, or want to, how to get at.

I won't attempt to explain Waves' installation architecture, but if you've got nothing to lose (no Waves plugins are working, right?), you could try clearing out any 32-bit Waves files from all folders and rescanning.  You can always re-install from scratch if that doesn't work ... you'll want to set a system restore point before performing major surgery, of course.  Good luck ...
 
Cheers,
Eddie 

Have you sent the message to Waves Support?

Just for grins, try changing the "AMD64" in the manifest file to "x86" and see if that makes the installer happy. Back up the file first just to be safe.

Have you sent the message to Waves Support?

Just for grins, try changing the "AMD64" in the manifest file to "x86" and see if that makes the installer happy. Back up the file first just to be safe.

You gotta love this forum software.

The funny part is that I read both posts #5 and #6 and didn't even realize they were the same at first... (it's rough getting old).

Honestly, I don't even know what the manifest file is.

I really wonder If I am installing this stuff to the right places and ask the other tech that but he swore that there are only Two screens that ask where you want to put things, the 32bit vst and the 64bit vst.

I get three screens and the first one wants to know where I want to install Waves Complete V9r7. It defaults to C:\Program Files (x86)\Waves and that is what I accept. I'm wondering if I should be changing that to C:\Program Files\Waves?

I did call support again and spoke to a different guy because Dave Burman was not there. (Hell, I didn't realize they were in Israel, I thought they were in Knoxville TN.) I will be able to give him a call around 7am EST in the morning.

I'm running out of altitude and ideas if he can't help. Looks like I may be trying to sell some licenses cheap after these sales are over. Then again, maybe the new X2 update will fix things.

Thanks for the reply bit.

Manifest files are XML text files that can be used to specify links to external files, either as part of a software installation or to modify the software's behavior or appearance at runtime. They probably have other uses, but my experience is limited to those scenarios. 

In your case, it's strictly a Waves issue, unrelated to SONAR. Although it could be related to your AMD processor. Either way, you will have to rely on Waves to tell you how to fix it.

Thanks for the Education on the Manifest files!

The interesting thing is, The machine has an Intel I7 processor an Nvidia GTX 560M display adapter so still can't figure out the AMD thing...  

I did talk with Waves this morning and they are going to try and arrange for Q&A (east coast) to do a remote on the machine.

I did get the machine at the desk to work by removing everything Waves, files and registry, and loading the last version (9.1) of the plugs. So far no crashes.  

Kind regards,
Rick