broken adobe reg key in mfu reg traces?

everytime i launch adobe reader, a registry key appears in "mfu registry traces" section in r-wipe&clean. each time, i clean mfu list and then after i launch adobe reader, this reg trace reappears. after a few mins search, seems it's got something to do w/ adobe reader's "adobe arm".
is there any way to prevent this from being created or activated? using autoruns, i deactivated adobe speed launch and adobe arm which is used for adobe update, afaiu. but this reg trace keeps appearing. and even though i disabled auto update check from adobe reader's preferences options & disabled its autostart for update check from "autoruns", an "arm update log" file is created every time adobe reader is launched which is visible via r-wipe&clean's temporary files section.
thanks.
here's what it looks like:

 

Siberianwolf, supposedly (section 2.4.6), logging can't be disabled and updater invocation is triggered every time a user logs on. It doesn't appear disabling the updater <a'la "bcheckforupdatesatstartup" key creation> will override my opening statement. Section 2.2 covers basic operation.

DirectDwnld PDF -http://kb2.adobe.com/cps/837/cpsid_83709/attachments/Acrobat_Reader_Updater.pdf-

 

As I understand it section 2.4.1 controls the method - update checks still occur. 2.4.2 does nothing more than control the end user interface. 2.4.4 appears to control the update check once invoked. And 2.4.6 - logging, as stated prior and according to their pdf, cannot be disabled. Personally, I wouldn't worry about the reappearance or R-Wipes reporting.