Adobe Acrobat Reader DC

Hello!

I have upgraded to the latest Reader (v2015.007.20033) today and have found out that if the below items are deleted (found by registry cleaner) the Reader needs to itself reconfigure during the first start up upon deletion of the said registry entries. I have put these entries into exceptions as a temporary workaround.

post-28604-0-07129100-1431511544_thumb.png

Also please include this new version of Adobe Reader among applications which are cleaned.

Thanks & regards!

Piriform staff, it's a bug and you need to address it.
Furthermore, as this new version of Adobe reader supersedes all previous and becomes Adobe's prime (cross platform) reader application, it needs to be included in the cleaner module.
Hmm, it looks like a lack of communication ...

I believe that a full appraisal of the new Adobe is ongoing with devs.

Hopefully. Any feedback is welcome.

It's a shame that the new version doesn't include a fix for this issue and Adobe Acrobat Reader DC isn't included in the cleaning module. I'm disappointed, heavily.

Hi, the team is aware of the issues with Adobe Reader DC and is working on getting it fully supported in CCleaner. :)

Thanks for the info but it means that we will have to wait a month or so until next routine monthly update in June is released. :-(

Hi,

Unfortunately, we haven't been able to reproduce this problem.

When deleting these Registry entries, Adobe Reader DC still works as expected.

The application is not requesting to be installed/reconfigured by removing those Registry keys.

Would you be able to provide us with a video or set of snapshots to illustrate the problem?

Thanks

I tend to think it has something to do with the Czech localized version of Adobe Acrobat Reader DC. Please test it (v2015.007.20033).

I forgot to give you also these entries. Please checkt what happens if deleted.

HKCR\CLSID\{98D9A6F1-4696-4B5E-A2E8-36B3F9C1E12C}

HKCR\CLSID\{D38406DA-E8AA-484b-B80D-3D3DBDCC2FB2}

@MrT

Any news in relation to my above two posts of May 29?

Hi, I'm having the same problem.

These are the steps to reproduce the problem:

- Clean the registry.

- Open Adobe Reader DC from the app icon, not by opening a PDF document. It will reconfigure itself again.

I'm using Adobe Reader DC 2015.007.20033 in Spanish.

These are the keys that are being deleted:

ActiveX/COM Issue LocalServer32\"C:\Program Files (x86)\Adobe\Acrobat Reader DC\AcroRd32Info.exe" /PDFShell HKCR\CLSID\{98D9A6F1-4696-4B5E-A2E8-36B3F9C1E12C}
ActiveX/COM Issue LocalServer32\"C:\Program Files (x86)\Adobe\Acrobat Reader DC\AcroRd32Info.exe" /PDFShell HKCR\CLSID\{D38406DA-E8AA-484b-B80D-3D3DBDCC2FB2}
Missing TypeLib Reference IAcroAXDoc - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{08A9E040-9A9C-4F42-B5F5-2029B8F17E1D}
Missing TypeLib Reference CAcroApp - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3E6-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroPDDoc - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3E7-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroAVDoc - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3E8-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroAVPageView - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3E9-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroPDPage - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3EA-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroPDAnnot - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3EB-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroPoint - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3EC-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroRect - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3ED-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroTime - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3EE-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroPDTextSelect - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3EF-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroHiliteList - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3F0-4981-101B-9CA8-9240CE2738AE}
Missing TypeLib Reference CAcroPDBookmark - {E64169B3-3592-47D2-816E-602C5C13F328} HKCR\Interface\{9B4CD3F1-4981-101B-9CA8-9240CE2738AE}
Sorry, I could attach them in a txt file but I did not see the option.
Thanks.

Don't remove registry entries unless you know they are not needed (see my signature)

It's a nice advice but not solution of this CC bug.
When I started this thread I was alone reporting this bug but now look at this thread and the second, this bug starts to be identified by more users. One thing you need to keep in mind, only a small fraction of CC users comes to this forum. So you can be sure that this bug plagues many more users.

This bug isn't solved in v5.07 yet.

I don't think it is a bug in CC (CC found faulty registry entries only). The culprit seems to be the installer of AAR. I can reproduce this problem on one PC only, but I don't know why this happens. On 4 other PCs this problem doesn't occur!

Exclude the following registry key and the problem is solved:

HKCR\Interface\{9B4CD3E6-4981-101B-9CA8-9240CE2738AE}

Exclude the following registry key and the problem is solved:

HKCR\Interface\{9B4CD3E6-4981-101B-9CA8-9240CE2738AE}

Thanks. It indeed works.

Thanks. It indeed works.

Great! Maybe Piriform can add this registry key to CCleaners internal exclude-list?

So far we have been unable to reproduce the issue internally. Thanks for the additional info. :)

Same problem here. I am running CC v 5.07.5261 (64bit) in a new clean install of Win7 64bit.

Also just to be clear, removing those reg keys does not cause Reader DC to re-install. It just does a reconfigure or setup. But, certian things I set in Reader Prefs persist across the Cleaner fix and the restart of Reader. So it is not clear what it is doing when it needs to re-setup, as those items in prefs do not go back to default.

Also #2: I excluded the suggested key:

HKCR\Interface\{9B4CD3E6-4981-101B-9CA8-9240CE2738AE}

and it had no effect. Issue is still there.

But, I am running USA/Eng versions of all of the above, so perhaps the key is different.

AND, here is the kicker. When I first installed Reader DC, and then used CC none of this was going on. After about 2 or 3 weeks of this new install running the problem came up. I wish I could pin it down to some change, but I don't run the Reg cleaner part of CC that often.

bc