Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
1

Unable to unisntall Adobe Reader DC. MSI stuck.

New Here ,
Apr 04, 2022 Apr 04, 2022

Hi All,

 

We are currently upgrading to the latest version of adobe reader via SCCM.

Ive made the usaul pacakge by patching the MSI file and deploying.

Issue ive got is we unisntall the previous version to replace it with the new., t when doing this the unisntaller is getting stuck.

The MSI log shows the following. It sits here until i kill the msi process manually and AcroCef_1 folder is the only folder left in the "C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader" directory . This is the same when using the cleaner tool.

 

MSI (s) (60:5C) [09:40:17:292]: Executing op: CustomActionSchedule(Action=ProcessDeleteRegistryEx,ActionType=3137,Source=BinaryData,Target=ProcessDeleteRegistryEx,CustomActionData=HKEY_CLASSES_ROOT\AcrobatPDXFileType\shell\open\command@@command@@HKEY_CLASSES_ROOT\AcrobatBPDXFileType\shell\open\command@@command@@HKEY_CLASSES_ROOT\Acrobat.aaui\shell\open\command@@command@@HKEY_CLASSES_ROOT\Acrobat.XFDFDoc\shell\open\command@@command@@HKEY_CLASSES_ROOT\Acrobat.XDPDoc\shell\open\command@@command@@HKEY_CLASSES_ROOT\Acrobat.RMFFile\shell\open\command@@command@@HKEY_CLASSES_ROOT\Acrobat.FDFDoc\shell\open\command@@command@@HKEY_CLASSES_ROOT\AcroExch.XFDFDoc\shell\read\command@@command@@HKEY_CLASSES_ROOT\AcroExch.XDPDoc\shell\read\command@@command@@HKEY_CLASSES_ROOT\AcroExch.FDFDoc\shell\read\command@@command@@HKEY_USERS\[USER_SID]\SOFTWARE\Adobe\Acrobat Reader\[RegistryHiveName]\SCA@@-@@HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Low Rights\ElevationPolicy\{A2397324-4D73-4870-A795-995C56F49FBD}@@-@@HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Low Rights\ElevationPolic."

 

This is happening on both 2101120039 and 220120085.

 

Any Ideas?

 

Regards,

Luke

TOPICS
Crash or freeze , Download and install , Windows
3.0K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 07, 2022 Apr 07, 2022

Hi,

 

 

We are also seeing this and I have seen the same issue when manually uninstalling Acrobat Reader DC:

 

Re: Acrobat Reader DC high CPU uninstall issue - Adobe Support Community - 12856973

 

 

 

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Apr 19, 2022 Apr 19, 2022

Hi,

 

exact same problem and MSI-Log entry here aswell.
We have 5k clients and some clients have problems when uninstall the old Acrobat Reader silently.


We are using the uninstall string from the registry: 
HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1031-7B44-AC0F074E4100}
UninstallString = MsiExec.exe /I{AC76BA86-7AD7-1031-7B44-AC0F074E4100}

Since it's just a simple msi command, the problems seems to comming from Adobe.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Apr 25, 2022 Apr 25, 2022

Update:

I opened a support case at Adobe...
They said, that there is already an open bug with the Engineering Team for this problem. At the moment they plan a fix for the next regualr update in june. Till then a workround would be the Acrobat Cleaner Tool, they said.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 25, 2022 Apr 25, 2022

Hi,

Cheers for the update.

Ive currently got a shoddy work around in place.

Not ideal!

Regards,

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Apr 25, 2022 Apr 25, 2022

A shiddy workaround is better than no workaround^^
What do you do in specific?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 13, 2022 Jun 13, 2022

Hi TV01!
Thanks for the update on the response from the engineering team. I've been banging my head against the wall trying to trace through the entire process with Procmon. 😕

Can you post the response? I need something to take to management to let them know this should be fixed in the upcoming update.

Thanks!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 14, 2022 Jun 14, 2022

Here the response from German Adobe Support (simple Google Translation should do the job).

##############   April 25th  ##############

Hallo

Es gibt hierzu bereits einen offenen Bug mit unserem Engineering-Team.
Im Moment ist geplant, dies mit dem nächsten verfügbaren Update im Juni zu fixen.
Bis dahin kann ich leider nur vorschlagen, das Sie das Acrobat Cleaner Tool (https://www.adobe.com/devnet-docs/acrobatetk/tools/Labs/cleaner.html) als Uninstaller benutzen.
Eine andere Lösung gibt es leider bis zur Veröffentlichung des Fixes nicht.


Hallo

Da ich keinen Einfluss auf die weitere Bearbeitung habe und den Fall nicht bis Juni ohne weiteren Input offen lassen kann und Bugs in einer anderen Datenbank verwaltet und bearbeitet werden, werde ich dieses technische Supportticket (TS # E-000601267) nun in unserem System schließen.
Sie werden daraufhin eine automatisch verschickte Email erhalten, die davon spricht, dass ihr Anliegen gelöst wurde. Das bezieht sich nur auf das Supportticket - die Bearbeitung des Bugs ist davon unberührt.
Der Bug selber hat die Nummer ADC-4357458.
Mit dieser Bug-Nummer können Sie bei mir direkt oder indem Sie einen neuen Fall in der Admin Konsole aufmachen, den Status des Bugs abfragen.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 15, 2022 Jun 15, 2022
LATEST

Hi,

This issue has been fixed in our latest release. Please update to the latest version (22.001.20142) and try the scenario. 

 

Regards

Ravi 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines