🚀 go-pugleaf

SOLUTION...for a system of ours, anyways...

MY DISCLAIMER (EVERYONE HAS TO HAVE A DISCLAIMER THESE DAYS, VERY SAD...)
THESE INSTRUCTIONS ARE GIVEN IN GOOD FAITH IN AN EFFORT TO ASSIST YOU IN TROUBLESHOOTING AND FIXING THE ADDRESSED ISSUE. I AM HUMAN, AND WILL NOT BE HELD LIABLE IN ANY WAY FOR ANY MISTAKES I HAVE MADE IN THIS POST THAT MAY CAUSE HARM TO YOUR SYSTEM, CAREER OR ANYTHING ELSE. YOU MAY FOLLOW THESE INSTRUCTIONS AT YOUR OWN RISK. THERE, NOW THAT'S OUT OF THE WAY...!!!

I followed the instructions in the following Adobe Knowledgebase, but found it to be not totally complete:

 <http://www.adobe.com/cfusion/knowledgebase/index.cfm?event=view&id=KC.329137&extid=329137&dialogID=2930021&iterationID=1&sessionID=4830d2290e7b6e121403&stateID=0+0+2932034&mode=simple>

My solution for an XP system was to follow through section 2 in knowledgebase article 329137 regarding the setting of registry permissions to their defaults, however, I had to perform a few extra steps that are omitted from the knowledgebase article:

The problem with the Knowledgebase article I experienced was at the step where one is trying to replace the permissions on the PersistentHandler key by choosing the option of "Replace permission on all child objects with entries..." from its parent key ".pdf", I received an error message to the extent that the requested action could not be done (forgot the specific error message...).

I then closed the permission boxes for that key and opened the permissions for the PersistentHandler key. I noted that the Everyone group was the only ACE (Access Control Entry) that was listed in the ACL (Access Control List) box under the heading �Group or user names:�.

Then I selected Advanced.

In advanced, I selected the Owner tab and proceeded to take ownership of that key as administrator (select the administrator account and then select Apply). NOTE: ...if confused, you can check out the owner on other keys around this one, such as .pct or .pdb. <<Just remember to be careful in the registry and as an extra precaution, click "cancel" in the boxes when you are poking around to help prevent inadvertently saving any changes that you mistakenly made.>>

After I took ownership, I was then able to pull down the permission to this key from its parent by selection the Permissions tab in this Advanced Security Settings box and selecting �Inherit form parent the permission entries�� option, then selecting apply. You should see the permissions instantly added to the list above.

Alternatively, after taking ownership as discussed above, you could then retry the steps provided in section 2 of the knowledgebase article and all should work well, now.

FYI... I had to perform these steps on a total of 2 keys mentioned during the installation procedure. The second one that came up for me, immediately following the HKLM\SOFTWARE\Classes\.pdf\PersistentHandler was:

HKLM\SOFTWARE\Classes\CLSID\{B801CA65-A1FC-11D0-85AD-444553540000}\PersistentHandler

Ok, this post is wordy, but I hope it helps someone. :)

James