Acrobat 2019 Update Fails on Windows 10

[wrolison]

Hi,

We are now having issues upgrading older Acrobat 2015 classic to newer 2019 continuous builds.

Older build we are upgrading from:

When we try and install any 19.... build it is giving 2 odd errors:

if I click on ignore the update seems to install just fine. But this is a problem since silent installs are failing silently. I obvious cant click ignore on 5,000+ machines.

Now has happened on a doze machines.

Happening on Windows 10 1607, 1703, 1709, and 1803.

Relative log:

MSI (s) (B8:3C) [14:16:14:440]: Error: Wrong Long Path Name: C:\Windows\Installer\$PatchCache$\Managed\68AB67CA3301FFFF7706C0F070E41400\15.7.20033\wcchromenativemessaginghost.

MSI (s) (B8:3C) [14:16:14:440]: Error: Wrong Path Name: \\?\C:\Windows\Installer\$PatchCache$\Managed\68AB67CA3301FFFF7706C0F070E41400\15.7.20033\wcchromena...

MSI (s) (B8:3C) [14:16:14:440]: Error: This file path is updated, hence failing to create: C:\WINDOWS\Installer\$PatchCache$\Managed\68AB67CA3301FFFF7706C0F070E41400\15.7.20033\wcchromenativemessaginghost.

MSI (s) (B8:3C) [14:16:14:440]: Note: 1: 1310 2: 110 3: C:\WINDOWS\Installer\$PatchCache$\Managed\68AB67CA3301FFFF7706C0F070E41400\15.7.20033\wcchromenativemessaginghost.

MSI (s) (B8:3C) [14:16:14:441]: Executing op: CacheRTMFile(SourceFilePath=C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\Browser\WCChromeExtn\WCChromeNativeMessagingHost.exe,FileKey=wcchromenativemessaginghost.,,ProductCode={AC76BA86-1033-FFFF-7760-0C0F074E4100},ProductVersion=15.7.20033,Attributes=16384,,,,CopierFlags=0,,,,,,)

MSI (s) (B8:3C) [14:16:14:441]: Executing op: RegisterSharedComponentProvider(PatchGUID={AC76BA86-A440-FFFF-A440-0C120B4E4300},MediaCabinet=#PCW_CAB_ACR,File=wcchromenativemessaginghost.,Component={B7C991AF-7B32-44CF-8DCC-F24C9AC11607},ComponentVersion=18.11.20035.2003,ProductCode={AC76BA86-1033-FFFF-7760-0C0F074E4100},ProductVersion=15.7.20033,PatchSize=35584,PatchAttributes=0,PatchSequence=10493,SharedComponent=0,IsFullFile=0)

MSI (s) (B8:3C) [14:16:14:442]: Executing op: CacheRTMFile(SourceFilePath=C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\Browser\WCChromeExtn\manifest.json,FileKey=manifest.json,,ProductCode={AC76BA86-1033-FFFF-7760-0C0F074E4100},ProductVersion=15.7.20033,Attributes=16384,,,,CopierFlags=0,,,,,,)

MSI (s) (B8:3C) [14:16:14:444]: Executing op: FileCopy(SourceName=WCCHRO~1.EXE|WCChromeNativeMessagingHost.exe,SourceCabKey=wcchromenativemessaginghost.,DestName=WCChromeNativeMessagingHost.exe,Attributes=16384,FileSize=145904,PerTick=65536,,VerifyMedia=1,,TotalPatches=1,,,CheckCRC=0,Version=18.11.20035.2003,Language=1033,InstallMode=327417856,,,,,,,)

MSI (s) (B8:3C) [14:16:14:444]: File: C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\Browser\WCChromeExtn\WCChromeNativeMessagingHost.exe; Patch targets existing file.; Smart patch; Existing file is a lower version

[kglad]

2015 doesn't update to 2019.

if you have a current subscription, uninstall your acrobat 2019 and install the cc desktop app from here https://creative.adobe.com/products/creative-cloud and use it to install your adobe subscription and trial programs.

[wrolison]

I've been doing updates this way for over a year and been working fine. I think it might be a Windows Update that has broken it.

It's never been an issue. Plan to test by removing this past Tuesday's updates.

And to be clear the update goes thru just fine after clicking ignore and I see nothing not working correctly after words.

[wrolison]

Good morning,

I believe I have resolved the issue for now. Not the
best option but looks like the correct one for now.

Just FYI, if curious.

It’s happening with latest Chrome 72. Google changed
something with extensions so that is what is failing during the install now.

I changed the installer by adding two new command-line
options:

ENABLE_CHROMEEXT=0

EULA_ACCEPT=YES

So first one says don’t install the Chrome Extension and
then accept the EULA so user does NOT have to agree to terms first time.

The Adobe Chrome extension is and has never been required as
Chrome has its own build in PDF viewer which is being used by default anyways.

After the change, the install is now once again successful.

[sbsysadmin]

We are seeing this exact same behavior.  Except we're not even trying to udpate to Acrobat 2019.  We're just trying to apply the latest patches to our Acrobat DC 2015 Perpetual licenses.  I tested thoroughly last night after first thinking something was corrupt on our end. . . the problem does indeed seem related to a Windows update not playing well with Acrobat.

Reproducing the issue. . .

1. Install Windows 10 Enterprise Build 1803 and fully patch Windows (as of Feb 20, 2019) via Microsoft Update.
2. Fresh Install of freshly downloaded Acrobat Pro fails to patch to latest version (2015.006.30475).  Same error as described by OP above. 

Confirming that it's related to a (very) recent Windows Update. . .

1. Install Windows 10 Enterprise Build 1803 and do not patch Windows at all.
2. Fresh Install of freshly downloaded Acrobat Pro sucessfully updates to latest version (2015.006.30475).  No errors.

This is likely to become a problem for more and more people as more people try to patch/update their installs of Acrobat since the latest Windows Updates were released.

[wrolison]

Thank's for confirming.

I take it Chrome is NOT install at all and still happens?

Tried installing on fully updated Win10 1803 using the Adobe command line option ENABLE_CHROMEEXT=0 to see if it installs correctly then. Just to confirm you see same behavior with that as well.

Thanks again

[sbsysadmin]

Doesn't seem to matter whether Chrome is installed or not.  When I first encountered the problem yesterday afternoon, Chrome was installed on the computer(s) where I first encountered it.  For my testing and confirmation that a Windows Update was involved, the computers were otherwise completely clean.  Just installed Windows, then installed Acrobat Pro (2015), then patched Acrobat Pro.  The only variable there being whether I first updated Windows or not.

[wrolison]

Thanks for update.

Ever find which update?

[sbsysadmin]

Credit where due.  In prior threads, subhadrav38507044 had already determined that the latest cumulative update for Windows 10 was related to this issue and has reportedly logged a bug.

[wrolison · Accepted solution]

FYI, this was finally fixed by Microsoft with the May 2019 Update:

https://support.microsoft.com/en-us/help/4499167