I installed the 64 bit version with the Command Center and there were no apparent problems. But, the 32 bit version, as you know, has to be installed manually from the Sonar update exe file in the ProgramData folder, and that's where I ran into trouble.  I opened the file as Administrator and somewhat into the install I received the following prompt:
 
                    "An error occurred while trying to replace the existing file."
                         "Delete File Failed: code 5"
 
The first file to trigger the prompt was:
                    "C:\Program Files[x86]\Cakewalk\Sonar Platinum\DShowProx"
        
The prompt gave me the choice to abort, or skip "[not recommended]".  So, I aborted the install.  I removed the offending file and placed it on my desktop.  Then I reattempted to install.  I repeated that process with several prompted files in the following order:
                      "C:\Program Files[x86]\Cakewalk\Sonar Platinum\Stretch.ax
                       "C:\Program Files[x86]\Cakewalk\Shared Plugins\Dewire.dll
                        "C:\Program Files[x86]\Cakewalk\Shared Utilities\NullProxy


The next prompted file was a Sonitus dll.   What is happening here and how can I fix it? Thanks.
 

You stated that " I opened the file as Administrator" did you right mouse on the installer application and choose "run as administrator".

Thanks for responding, rabeach.  Yes I did as you described.

Did you choose where it was to be installed or did you let the installer use the default. I ask because your errors show that the installer is trying replace existing files.

No, mudgel, since the Sonar X series began, I've been using the standard cakewalk default installation.  Could it have something to do with the fact that I installed the 64 bit version first via the CCC?

Reboot. Don't open any applications. Disable your virus scanner.

If that does not work:
https://www.cakewalk.com/...d-code-5-access-denied

Ok, that worked.  I never had trouble with Sonar and Kaspersky before, so maybe it just needed a restart.  I should have remembered to do that.  Somehow I had left behind continual rebooting back in XP.  Nice to know it still works.  Thanks everyone for responding.