🚀 go-pugleaf

Folks, I've run into the same problem and seem to have found the solution. The registry tweak from Adobe TechNote 329137 <http://www.adobe.com/support/techdocs/329137.html> is valid but incomplete.

On my WinXP SP2 I had to fix TWO different keys, namely HKLM/Software/Classes/.pdf/PersistentHandler and HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{B801CA65-A1FC-11D0-85AD-444553540000}\PersistentHandler . (The problem with these keys was, they were owned by local administrator account, not by Administrators group). The Adobe note 329137 states (correctly) that one needs to propagate the permissions from the parent key (of the key referred in error message) to all its child objects. However, it fails to mention that it may be impossible to do until one propagates OWNERSHIP from the parent key to the child objects. (Then the two above-mentioned keys become owned by Administrators group rather than the sole local Administrator.) Only then one can do that "Replace permission entries on all child objects...", as described in the note.

After fixing the two registry keys, the installation completed without a glitch.

We use SMS for Adobe Reader deployment but so far I have encountered only one machine hit by this problem. I therefore cannot guarantee that the keys in problem always have exactly the names as referred above. I'm curious to hear from those who had this problem on XP if in their cases the key names were same.