Skip to main content
Participant
May 20, 2015
Answered

[Acrobat Reader DC] HKCU registry keys are not replicated for each user as for Adobe Reader

  • May 20, 2015
  • 5 replies
  • 49038 views

For Adobe Reader, all the registry keys which are added with the Adobe Customization Wizard are automatically added to each user. Unfortunately, it is not the same with Adobe Acrobat Reader DC.

They registry keys have to be stored in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader\2015\Installer\Migrate to be automatically added in the HKCU of the user at its first launch of the application. But they are stored in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader\[RegistryHiveName]\Installer\Migrate, as we can see on the screenshot below:

The problem is probably coming from one of the custom actions. The variable RegistryHiveName is not translated. I didn't make a lot of research, but waiting on a solution from Adobe, I made a PowerShell script which move the registry keys to the correct place:

Move-Item -Path 'HKLM:\SOFTWARE\Adobe\Acrobat Reader\`[RegistryHiveName`]\Installer\Migrate\*' -Destination 'HKLM:\SOFTWARE\Adobe\Acrobat Reader\2015\Installer\Migrate' -force

(PowerShell has to be executed in 32 Bits)

If Adobe can correct it in the next version, it would be nice !

This topic has been closed for replies.
Correct answer Rave

Hi Maxime,

We have logged a bug for this and working on it.

Regards,

Rave

5 replies

jonathans62717764
Participant
August 18, 2017

Tried setting keys for 17.012.20095 and experienced exactly the same issue.

I know you've only had a couple of years but any chance of a fix Adobe?????????

Participating Frequently
August 22, 2017

Hi Jonathans,

I tried to reproduce this issue at our end but its working fine. Can you please share the command line which you are using to install Reader. It would be a great help if you can also share the .mst file as well.

Regards,
Sourab Sharma

Participant
July 25, 2017

This issues is still not resolved.

Inspiring
February 4, 2016

Whats the status of this issue, any resolution?

Participating Frequently
February 5, 2016

Not hat I've seen. Disappointing to say the least.

Participant
January 18, 2016

An Update would be nice.

Participating Frequently
January 20, 2016
Participating Frequently
January 20, 2016

It's not an issue with the CW, it's a problem inherent to Adobe's MSI for the DC. 

Rave
Community Manager
RaveCommunity ManagerCorrect answer
Community Manager
October 24, 2015

Hi Maxime,

We have logged a bug for this and working on it.

Regards,

Rave

Inspiring
November 2, 2015

Whats the status of this? Having issues with any customisations made in DC Customisation wizard not being applied when deployed through SCCM (default pdf handler etc)

Works when individual user installs from software center, but settings not applied to future users.

Same issue as this, or should i make a new topic.

Rave
Community Manager
Community Manager
November 4, 2015

Hi Bernie,

The engineering team is aware of the issue and working on the fix. I will keep you updated on this thread in case I have any new information.

Regards,
Rave