could simply be a case of your security descriptors for the registry key being knackered up. I haven't made the jump to the newer OS's yet, but it should follow a similar process as in XP.
In XP, you would load regedt32 and navigate to the key in question (I'm guessing a Blizzard or World of Warcraft key under HKLM/Software) and right-click the key then select Permissions. Click the Advanced button and go to the Owner tab and check who has it--should likely be Adminstrator, or the Administrators group. If this is something other than your account, the Administrator, or the Administrators Group, then you likely need to change it. Before applying the change, make sure to check the box for applying it to all subcontainers and objects. After veifying/updating the owner, close that panel (OK button) to get back to the main Security panel. You should see that owner acount with full permissions (should be Administrators by default, unless it was your account), and possibly your user name there if it wasn't the owner. System should also be present by default with full permissions. If neither are there, add them both and grant your account at least Read permissions (giving it full permissions could pose a security risk, so normal users often don't get full control). Apply the changes to this panel then open the Advanced panel one more time to force the changes to propogate to all subcontainers and objects by checking the lower box that says to "Replace entries on child objects..." and clck the apply button.
This should force the Administrators and the System group to have full control of everything in that folder (so when you run as admin, it is not blocked), and also give your user account read-only permissions (which sometimes is a fix for having to run as admin all the time).
Raist