Hi,
I normally don't encounter these issues if the 32-bit version of Acrobat is manually installed not using the CC Desktop app on 64-bit version of Microsoft Windows 10.
Since you are content creators, I assume that you must be signed in consistently to the Creative Cloud but I don't use it at all.
If you notice the CC Desktop app will install 64-bit programs only, and more specifically they all install to C:\Program Files.
Conversely, if you choose to manually install the 32-bit version of Acrobat separately from the CC app, it will install to C:\Program Files(x86).
The CC desktop app seems to be faulty when deploying 64-bit modules and dynamic link libraries(.dll) .
It makes sense to me to see this conflict arise since a handful of Creative Cloud background processes share the same libraries and folder paths as Adobe Acrobat (64-bit).
Which is why you'll notice a repetition of these background processes names listed in the Task Manager.
What is key here, is to not install Adobe Acrobat Pro using the Creative Cloud desktop app.
With that said, you must also look into Microsoft's initiative to move Microsoft Windows to a 64-bit only world (like Apple did with macOS).
Unattended Windows updates are now enforcing upgrades to 64-bit only apps, plug-ins, drivers, and programs.
What used to work before is now deprecated or completely removed with these new system updates (this is true for those of you that upgraded from Microsoft Windows 10 to 11 version on the same machine).
In which case, it won't hurt to review if the WOW64 subsystem is working properly.
I would say to test Adobe Acrobat in compatibility mode (for an older version of Windows, like Windows 8, for example).
Additionally, any changes that have worked for you before using Admin rights must be done with the Windows built-in Administrator account globally; not with the current user account with Administrator rights.
I hope any of this helps and makes sense to point you in the right direction.
25
Replies
AdChoices