Jeff,

I'm a software engineer as well as a video producer, creator, animator, etc.  I know a thing or two about permissions on a Windows OS.

Creating a "new" user account is NOT a good idea, it will basically put an "end user" into a new context -- meaning they will only see their applications (and in some cases drivers) that were installed under full trust or if they selected "everyone" for any of their other applications (leaving them with a new desktop with nothing available).  Either way, it's most likely only going to confuse people if they take your suggestion.

There is another "Administrator" account for Windows 7, but to make it "active" requires what I would consider an OS hack and not a good idea.

Another possible solution is to uninstall CS6 (everything) and then right click on the Installer file and select "Run as administrator" ... but if that is required to make the CS6 installer work, then that clearly points to an installer problem and not an end user problem.

Before suggesting end users do anything to their computer, it would be nice to have an Adobe QA person or Adobe Installer Engineer confirm that their is not a problem with the CS6 installer.  I know it gets ugly when there is a problem with the installer and fixing a bad permissions setting can be a nightmare as standard "updates" can't fix an installer.  But either way, lets get positive proof this is a permissions problem before coming up with possible solutions.

I have plenty of applications installed on my computer (Visual Studio, MS SQL, Cinema 4D, etc. etc.) all under the same user account and none of these products are having permission issues.  If there were a permissions problem with my user account, I can assure you Visual Studio 2010 would be affected, it isn't, it's working perfectly.

I know this is going to be difficult issue to resolve, about the only additional information I can provide on my side is that I did have CS4 Photoshop Extended installed prior to installing CS6 Production Premium suite.  When/If I have more time, I'll try to trace execution and see if I can find the thread source that's repeating this "update registration" process and try to provide more info as I discover it.  But in the mean time it would be most helpful if you can get an Adobe Engineers attention on this matter and hopefully bumped up in priority ... assuming of course that the registration process governs application usage?

If I were a hazard a guess it's one of two things:

1.  Security exception when communicating with a web client (aka via Browser) and not get any results back from a completed registration

2.  Security exception when trying to write a valid registration return value to a registry location that the application account isn't permitted to access under current user account's permissions

Thanks, Rob.