Resolution to Error 1328 when installing Adobe Reader DC

[RyanGSteele]

Hi all,

I just resolved a difficult issue I was having with installing Adobe Reader and thought the resolution was worth sharing. The computer lost power while Adobe Reader DC was installing. After that, I was unable to install Reader. I kept getting "Error 1328.Error applying patch to file C:\Config.msi\PTEDE6.tmp" when using the installer from https://get.adobe.com/reader/enterprise/. I tried using the Adobe Reader Cleaner tool from http://labs.adobe.com/downloads/acrobatcleaner.html but it didn't have any effect.

After spending some time examining Process Monitor logs, I discovered the installer was accessing cached Adobe Reader installation files from this folder:

C:\Windows\Installer\$PatchCache$\Managed\68AB67CA7DA73301B744CAF070E41400

After deleting that folder, the installation completed successfully. (You will need to turn on the option in Windows Explorer to "Show hidden files" and turn off "Hide protected operating system files" to access this folder through Windows Explorer.) I suspect the installer had been attempting to use this cache without verifying the integrity of the files within.

Obviously, messing around with system files is not recommended and should only be attempted as a last resort. Make sure you have backups and be prepared to reinstall your operating system.

If anyone from Adobe is reading, perhaps the Adobe Reader Cleaner tool could be updated to remove this folder as part of its cleaning process.

[Adorobat]

Hi RyanGSteele,

We appreciate your taking time to share your finding with us, will forward this to our product team to have a look.

Thank You,

Shivam

[Sam 1234]

Thanks, Ryan Steele,

I was having the same issue with Adobe Acrobat DC.

For DC the file is called: 68AB67CA3301FFFF7706C0F070E41400

after deleting this file, Adobe Acrobat DC was updated without any problems.

Thanks Again,

Sam Gill

[Guest]

Thanks, RyanGSteele!

For Acrobat 2017 (not Reader) it's "68AB67CA3301FFFF7706E01180573600".

I renamed the folder for the update 17.011.30148 and afterwards it's finished.

[fraserd98210706]

Brilliant tip thanks and it worked for me with Acrobat Pro 2017 as well. I used SearchMyFiles from NirSoft to search the C:\Windows\Installer\$PatchCache$\Managed\ for Adobe and got lots of hits for the same folder. I remaned the folder, appending old to it, restarted Acrobat then searched for an update. Acrobat found one, downloaded and installed it perfectly and even recreated the folder that SearchMyFiles had displayed. I deleted the renamed original folder and all is well. Excellent tip, thanks.

[CoathamPier]

I am trying to install the windows 7 version download of  the DC reader on Windows 7 Pro 32-bit.

I get error 1328. Error applying patch to file C:\Config.msi\PTE3E40.tmp"

It's not a patch though - its a new install.  I tried deleting the folders as described above, several times, and it always does this.

ANyone had this stubbrin refusal to install on WIndows 7 Pro?

[CoathamPier]

hmm. I just ignored the first error; got to a second error; ignored that; then erro 1721. There is a problem with this installer package. A program required for this install to complete could not be run.

Is this known to anybody?

[CoathamPier]

I believe the installer has some problem with permissions in the Config.msi folder. This folder seems to be created by the  installer, and after the base installation of the reader is done, the installer tries to update /patch the files up to current date. That is where my error 1328 mesages come from; it looks like the patches are unable to write to the Config.msi folder.

While the installer was paused with an error 1328 message showing, I tried opening the Config.msi folder (only exists during the install) but was denied access, so I cannot even explore the folder. I was able to look at the config.msi folder's properties and see it was set to Read Only, but attempts at clearing that option, although the box remained clear as I clicked 'Apply', did nothing.

Hs anyone found a fix fpr this? Is it a bug in the installer that takes ownership of the config.msi folder and will not allow the patches to access it?

Unfortunately, the whole installer rolls back and does not even leave the base version there.

[CoathamPier]

Latest...

I looked carefully and noticed a discrepancy between the messages I saw. Some said the folder was "C:\Config.msi" and others said it was "C:\Windows\Installer\Config.msi".

So I created both folders myself and checked the access was full for Administrators (me).

I also noticed both folders were set to Read Only by default. I chnaged both but on closing and re-openeing they were set back to Read Only. Drat. Something is changing them back. 

I ran the installer, but after extracting the files it stopped with Error 15021 "Setup was interrupted before Adobe Acrbat Reader could be completely installed".  No files had been created in my folders to that point, so I learned nothing more.

I ran the Adobe Cleaner and restarted. Downloaded and ran the installer again. Same error 15021.

Maybe the installer does not like the fact that I have created the config.msi folders already; maybe it needs to create the folder with its own full control permissions and fails when it finds the folder already there with my permissions. Or maybe that persistent default 'Read Only' permission on my folder cannot be overidden by the installer.  Anyway, Adobe makes it impossible to troubleshoot.

Please, does anybody have a definite answer and fix for this/

All I want to do is install the reader on my laptop. Is that such a bad thing?

[CoathamPier]

This time, I deleted my C:Config.msi folder, but left my "C:\Windows\Installer\Config.msi" folder.

This time the installer ran and created its own folder  C:\Config.msi.  Once again, it is inaccessible to me, so no help.  However, this proves that the installer requires that it creates its own folder with its own permissions; effectively an impenetrable lock on its contents!

It ran until the first error 1328 about applying patch to "C:\Config.msi\PT48D9.tmp".

I then left the error message while I copied the entire contents of C:\ Program Files\Adobe\ to a new folder.

I exported the registry at this point. My expectations being that this state represents the initial installation of the reader and it is only the patch/updates that are failing.

Aaagh. After copying the Adobe folder back to Program Files and importing the registry- it said it could not replace all registry keys because some files are in use.

I ran it again and checked through the registry. There are manyAdobe keys there now, so hopefully the required keys were added. No programs menu entry or  Add/remove programs entry though.

So I ran the installer again, hoping that this time it will repair the install and finish properly.

Ah.. it reached further than before... it installed registry entries and a shortcut to the desktop... a start menu entry right at the top...optimised.... Setup completed. An entry is now in the 'Uninstall or Change a Program' list too.

The reader runs and Itried running its 'Repair Installation' option, just to be sure.

It did throw up three errors about AdobeCollabSync.exe not locating the procedure entry point WinHttpWebSocketCompleteUpgrade in WINHTTP.dll, but otherwise completed.

I also opened Programs and features and selected Adobe Reader and selected repair. It popped up te same three errors, so they are possibly existing errors in this version. They shouldn't stop Reader from reading pdfs.

So- what a palava just to get thye reader installed.

[AnandSri · Accepted solution]

Hello @CoathamPier

I hope you are doing well. Thank you for taking all the extensive steps and sharing the details here.

Error 1328: "Error applying patch to file C:\Config.msi*.tmp"

This typically occurs when the installer tries to apply a patch to a file that has already been modified or is locked.
It’s often linked to corrupted cached files in C:\Windows\Installer\$PatchCache$ or permission issues in C:\Config.msi.

Error 1721: "A program required for this install to complete could not be run."

This is a Windows Installer error indicating that a custom action (like a script or executable) failed to execute properly.

Error 15021: "Setup was interrupted before Adobe Acrobat Reader could be completely installed."

This is a generic rollback error, often triggered by earlier failures, such as 1328 or 1721.

Run the Acrobat Cleaner tool to remove the installed app and all the related folders. Restart the machine, and download the compatible version of Acrobat Reader from the direct link, which supports Windows 7. Right-click the installer and choose “Run as administrator”. Ensure your user account has full administrative privileges. After installation, disable automatic updates:

Open Reader, then go to Menu > Preferences > Updater and uncheck 'Automatically install updates'.

If feasible, upgrading to Windows 10 or later will resolve these installer and WebSocket errors completely. The latest versions of Acrobat Reader are optimized and supported only on Windows 10 and Windows 11. 

I hope this helps.

Thanks,

Anand Sri.

[CoathamPier]

Thanks for your reply Anand Sri.  Actually I did try the Acrobat Cleaner tool, as I said a couple of posts above.  I also used that same location in the link you provided, to download the WIndows 7 variety of the Reader.

My user account is the Admnistrator, as well.

Anyway, it's Ok now. My last post described how I managed to arrive at a working installation.

I just think there must be a hidden problem in the installer when used on Windows 7, as many other people have had a problem too.

But it doesn't matter now- I got it to work eventually.

By the way, I must use Windows 7 because of legacy Automotive diagnostic software that only works on Windows XP or Windows 7.

So, we can leave this case now, thank you, My installation does work.

If I need to reinstall it at some time I will be sure to follow your guide steps though.

[AnandSri]

Hello @CoathamPier

I am glad that you were able to get this working. Thank you for trying those steps and sharing them here. Please feel free to reach out if you need any assistance.

Regards,

Anand Sri.