Hello,
 
  I have tried using the Addictive Drums plugin provided with the Platinum release of Sonar. Every time I try to insert AD as a soft synth I get a popup saying 'SONAR.PLT' has stopped working and then sonar exits. Every other VST2 plugin is working fine. Any ideas anyone? ALl the software is installed and updated through the Cakewalk command centre.
 
Config is:
 
  samsung laptop - i5 processor 2.6GHz
  Windows 8.1 64 bit
  4GB memory

Try a reset and rescan (make sure you do both) of your VSTs.
 
If that doesn't help, use the XLN Audio Installer to verify/update your AD install.
 
*Edit - I previously suggested uninstalling/reinstalling Addictive Drums, but after reading Bassman's post below, I realized the best approach with AD is to always try its own installer first.  That's what I always do, yet totally forgot that while thinking about the Command Center.  Doh! 

Had the same problem today - AD not recognising the computer id, followed by a Sonar crash.  I had to update the XLN Audio installer, which required me to be logged in to my XLN account.  Two minutes later, all was well, computer id recognised, AD 2 working perfectly, no more Sonar crashes.
 

Hello,
 
 Just back from holiday. Thanks for the replies. I tried the reset/rescan and got a new crash (Teleport stopped working - just on the AD standalone support?).
 I will try to reinstall AD via the XLN installer and see where this gets me.
 
 Chris

Hello Again,
 
  Reinstalled AD through the XLN installer rather than the SONAR console - seems to have fixed it.
 
  Tx for the help, much appreciated.
 
  Chris
 

I will chime in, since I've had a similar issue recently: AD2 in Sonar Platinum had worked for some time, then suddenly any project containing AD would crash Sonar on open. If an AD instance was added to a new project, Sonar would crash as soon as an output from AD was routed to a channel.
 
In my case, the problem was solved by designating Sonar to Run as Administrator. I'm leaving the solution here, in case it helps anyone else experiencing similar issues.
 
System specs, for reference:
Win 10 Home 64-bit
Intel i7-6400K
16GB RAM
ASIO4All audio driver

I have had the same issue as Faza. It always seems to follow a new Windows 10 update. something to do with "computer id not the same" or some biz like that. Run as Administrator, or reinstalling fro
m XLN's site have both done the trick.

I have had the same issue as Faza. It always seems to follow a new Windows 10 update. something to do with "computer id not the same" or some biz like that. Run as Administrator, or reinstalling fro
m XLN's site have both done the trick.