Well perhaps that's the problem, then: somehow the Waves installer thinks you have an AMD processor.

At this point I should probably keep my mouth shut but I never could resist an open door.

I think the real problem is that, it is Waves. 

I also have the same Waves messages in my Applications Event log, so you aren't the only one.  I am getting them on initialization of the VST (I have the Gold package), because I am working in projects that don't currently have any Waves plugins in them.  I'm surprised that more people haven't noticed this, but then I don't suppose a lot of people check their Event logs, so they probably don't know they have them.  Incidentally, I am running a quad-core Intel platform on a Gigabyte motherboard, so nothing AMD-related about my system.  Odd.  I will have to look at the manifest file and see if there's anything in there that might give a clue as to why this is happening.

Thanks leapinlizard!

Really appreciate you taking the time to have a look see. At least I know it is not just me that receives this msg.

Kind regards,
Rick

I think Bit nailed it ... the manifest file has a line that reads 'processorArchitecture="x86"', and I suspect some component of Waves is set to expect 'processorArchitecture="AMD64"' instead, thus producing the error.  I suspect that when they went to 64-bit they forgot to change both the manifest and the software component to 'processorArchitecture="x64"'.  Programmers tend to forget little things like that, but things manage to work in spite of the oversight.

Rick, I have the same message but Waves seems to be running okay. I checked Event Viewer because my issue seems to be with Amplitube 3 lately but that's for another thread.

@ leapinlizard,

Bit is a super knowledgeable guy and always takes time to help out. I'm thankful for his presence and kindness on the forum.

Thanks for taking the time to check this out and for having the knowledge to understand what is going on.

@ MrMook

Thanks for confirming that you are seeing this also and it is not causing you problems with Waves. That gives me another data point and leads me to believe that is probably not the root of my problems.

Sorry to hear you're having issues with Amplitude 3 and hope it gets worked out soon for you.

Kind regards,
Rick

I know it's a bit of a necro-post, but I've stumbled across this same error in my Event Viewer while trying to make my Win8 computer rock-steady, and this was the first thread that came up.
 
Fun fact: AMD64 is a nickname, just like x86 is.
 
x86 means that the processor instruction set and architechture is compatible with the 86-series processor instruction set that came out ages ago -- the 386, 486, etc. "x86" processors have added quite a few extensions since then (SSE, MMX, etc.) and aren't truly 86-series compatible anymore, but the name stuck as essentially meaning a 32-bit processor.
 
If you recall, there was a time when AMD was ahead of the game in the home processor world. They were the first to bring 64-bit compatible processors to the consumer market in the early 2000s. Windows programmers put the appropriate drivers/etc. in a folder named "AMD64", and the rest is history. In many sections of programmer-speak (especially when drivers are concerned), "AMD64" simply means "64-bit".
 
As far as the actual issue is concerned, it seems that this error is caused by SxS (Side by Side), whose job appears to be to select a 64-bit DLL when available and fall back to a 32-bit one when necessary. It looks to me as though Waves may have planned a 64-bit version of the License Center and never ended up writing one. The "error" should probably be sitting in the "information" or "warning" category, because it's really not that critical (at least for this application!).
 
-Ki
Salem Beats

Thanks for the education, Salem. And signing up for the forum just to do so!

Salem Beats
I know it's a bit of a necro-post, but I've stumbled across this same error in my Event Viewer while trying to make my Win8 computer rock-steady, and this was the first thread that came up.
 
Fun fact: AMD64 is a nickname, just like x86 is.
 
x86 means that the processor instruction set and architechture is compatible with the 86-series processor instruction set that came out ages ago -- the 386, 486, etc. "x86" processors have added quite a few extensions since then (SSE, MMX, etc.) and aren't truly 86-series compatible anymore, but the name stuck as essentially meaning a 32-bit processor.
 
If you recall, there was a time when AMD was ahead of the game in the home processor world. They were the first to bring 64-bit compatible processors to the consumer market in the early 2000s. Windows programmers put the appropriate drivers/etc. in a folder named "AMD64", and the rest is history. In many sections of programmer-speak (especially when drivers are concerned), "AMD64" simply means "64-bit".
 
As far as the actual issue is concerned, it seems that this error is caused by SxS (Side by Side), whose job appears to be to select a 64-bit DLL when available and fall back to a 32-bit one when necessary. It looks to me as though Waves may have planned a 64-bit version of the License Center and never ended up writing one. The "error" should probably be sitting in the "information" or "warning" category, because it's really not that critical (at least for this application!).
 
-Ki
Salem Beats

This forum is wonderful. I love it for information like this.
 
Waves support, despite an incredibly fast response time, couldn't explain what happens and why ... and suggested the usual "fix": uninstall, manual clean and reinstall ...