Invalid Serial Number - Acrobat Pro - Known good number

[Guest]

I am reinstalling Acrobat Pro XI on a machine to try to fix an error that appeared apparently after a recent Adobe update.

(Error was:  There is a problem with Adobe Acrobat/Reader.  If it is running, please exit and try again (4:4)) - Opening links in IE 11.  Turning off Protected mode at startup caused a 1:104 error)

We get the "Invalid Serial Number.  This is not a valid serial number" message. 

The SN is our known good corporate license one we bought from our very reliable VAR.  It installs on other machines. 

The option to select evaluation mode cannot be selected (program hangs). 

When I try to install Adobe Reader (as an alternative), I get "Error 1719.  The Windows Installer Service Could not be accessed".

Some other MSI files seem to work correctly.  Exe files install correctly (I was able to install a competitor's reader app temporarily).  Windows installer Service is up. 

Machine:  Windows 7 SP1 new build

This recurs after:

*     Adobe Cleaner program
*     System Restore

*     Re-registering MSIEXEC

*     SFC /SCannow

*     Admin vs. Non Admin account installation

Could someone please advise?  I checked for Windows Update 3139923, not installed on machine.   Is there a Windows patch missing or something else we need to do on the system side?

[Guest · Accepted solution]

The issue has been resolved.  For those who run into similar in future after checking their SNs out, here is what happened.

*  Removed Microsoft patch KB3139923

(KB 2918614 was also named as problematic for Windows Installer but this machine didn't have it

*  Full windows update of other "older" patches (this was a new install and didn't have much on it besides SP1 ... partly us because we rolled out a new WSUS server recently and "older" stuff wasn't approved yet)

* Reboot

* Next installation attempt with Acropro.msi threw an error message about "Microsoft Visual C++ 2010 x64 Redistributable will not be installed".

*  Downloaded and installed this redistributable

*  Next installation attempt worked as normal

The machine was a new build so apparently didn't have all it needed to support the installation.  We ran into the S/N problem recently with a machine that had been restored to factory as well so this makes a lot of sense.