PhrygianMode :

"I'm considering uninstalling/reloading Windows 7 on the off chance that one of my OS files is corrupted."

I think that is highly unlikely and unless you have a completely empty system not worth the effort.

Are you having any problems with other applications ? If not, concentrate on Sonar.

What registry cleaner did you use? Some of those things do more damage than good. CCleaner is probably the best free one to clean up/fix registry issues but if another program screwed it up already I'm not sure if it can repair it. How about Win updates? Are you up to date?

Just tossing out ideas.

AFAIK this is always a permissions problem. Once you received the original error, unless you cleaned registry of the aborted install, I am not sure running the install again would work. Did you clean the registry before running the installer as administrator? The reinstall attempts should be run without any reference to X2 in the registry.

Paul P: I haven't found any other apps that aren't working. If it's highly unlikely that my OS has a corrupted file, I guess maybe one of my download files has gone over to the dark side. rabeach: I've referred to that article a couple of times the last week or so. I've tried the first two steps. I guess I'll try the 3rd now. Many thanks to all of you that have responded.

At the bottom of http://www.cakewalk.com/s...tion_instructions.aspx are the links to the file lists with hash values for each version of X2. You can use a tool like WinMD5Free from http://www.winmd5.com/ to validate the files.

I have not used CCleaner. I'll try that. I did establish a restore point prior to the date of my ORIGINAL failed installation before my last failed attempt this AM.

Scook, thank you. I'll try that, too.

I doubt it is a bad install file. You can validate them to be sure. Getting the registry back to the state before the original failure would be a good idea. Then try the install running as administrator.

Getting the registry back to the state before the original failure would be a good idea. Then try the install running as administrator.

 
That seems reasonable.  A "bad" registry key (or 2 or 3) might be gumming up the works for every install attempt thereafter.