UAC may be only part of the problem. There are also changes in later Windows versions in how the installed programs are addressed due to limits on where a user (or the programs he is running under his account) can write files. Windows uses aliases for locations that older programs expect to be installed to. If you can run the Sonar installer "as administrator," (which is definitely not the same as installing it from an administrator login account) you may have better luck. Also running Sonar "as administrator" is not the same as disabling UAC, since access of file locations based on user privileges is not the same as the UAC system, but was present in very early Windows versions. Running as administrator gives the program access to locations where it would not otherwise have permission.
http://www.computerhope.com/issues/ch001198.htm So first try actually running Sonar as administrator, and if that does not work consider re-installing it by running the installer as administrator. If that doesn't work rub a penny on the monitor screen while chanting "evil out of the dead man's eyes" three times, and bury the penny in a graveyard by the light of the full moon .