Update & Upgrade Problems

How to Fix Acrobat 2017 Update Error 1309 on Windows 10

Adam DavisAdam Davis Nov 3, 2026 869 views

Question details

The user is experiencing Error 1309 when trying to apply software updates to Adobe Acrobat 2017 on Windows 10.

How to Fix Acrobat 2017 Update Error 1309 on Windows 10
Product
Adobe Acrobat 2017
Device & OS
Windows 10
Scenario
Installing a newer version update for Adobe Acrobat 2017 or Acrobat DC.
Observed behavior
The update process fails and throws Error 1309, indicating a failure to read the wcchromenativemessaginghost file located in the Windows Installer cache.
Before you start

Ensure you are logged into Windows 10 with an administrator account, as you will need permission to access and modify hidden system files in the Windows Installer directory.

Solution 1Recommended

Rename or Remove the Problematic Cache File

Bypass the read error by renaming or deleting the specific file that the Acrobat updater is failing to process.

Error 1309 is often triggered because the installer lacks permissions or fails to read a specific cached file. By renaming the file, you force the installer to ignore the corrupted or locked cache and proceed with the update.

1
Enable hidden items in File Explorer

Open File Explorer, click on the 'View' tab at the top, and check the box for 'Hidden items' so you can see the hidden Installer folder.

2
Navigate to the file path

Go to the exact folder path mentioned in your error message. Typically, this is C:\Windows\Installer\$PatchCache$\Managed\68AB67CA3301FFFF7706E01180573600\17.8.30051\.

3
Rename the file

Locate the file named 'wcchromenativemessaginghost'. Right-click on it, select 'Rename', and change it to 'wcchromenativemessaginghost.old'.

4
Run the update again

Launch the Adobe Acrobat 2017 updater once more. The installation should now bypass the error and complete successfully.

Rename or Remove the Problematic Cache File
Safe Modification: Renaming the file rather than deleting it provides a safe backup. If any unexpected issues occur, you can always revert the filename to its original state.
Free Microsoft Office alternative

Experience Hassle-Free PDF Editing with WPS Office

If you are tired of complex update errors and heavy software installations, WPS Office provides a lightweight, comprehensive, and free alternative. It includes a powerful PDF editor alongside robust Word, Excel, and PowerPoint alternatives, ensuring smooth performance without frustrating installer cache issues.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free, lightweight installer for Windows.
  2. 2. Install quickly: Run the installer. The streamlined setup process takes only a few moments and avoids complex cache dependencies.
  3. 3. Open your PDFs instantly: Launch WPS Office, click on the 'PDF' tab, and open any existing PDF document to start reading or editing immediately.
Built-in, fully-featured PDF reader and editor that operates without heavy background update services.Flawless compatibility with Microsoft Office formats (DOCX, XLSX, PPTX) and standard Adobe PDF files.Lightweight installation process that avoids complex Windows registry and installer cache conflicts.Completely free to use with an intuitive, all-in-one tabbed interface.
microsoft office alternative - wps office

Frequently Asked Questions

What causes Error 1309 during an Acrobat 2017 update?

Error 1309 generally occurs when the Windows Installer service encounters a read error while accessing specific files, such as 'wcchromenativemessaginghost', stored in the hidden Windows Installer $PatchCache$ directory.

Does this Error 1309 fix also apply to Adobe Acrobat DC?

Yes, many users have confirmed that renaming or removing the exact same 'wcchromenativemessaginghost' file in the installer cache resolves Error 1309 when updating Adobe Acrobat DC.

Is it safe to modify files in the Windows Installer $PatchCache$ folder?

While it is usually recommended to leave the $PatchCache$ folder alone to preserve uninstallation and repair capabilities, renaming the single file causing the Acrobat update failure is a proven and localized workaround that generally does not harm the broader system.