Hello,
I have a few users with Adobe Acrobat 2017, latest patch applied and the Distributable installed as well, able to save Office files as PDF but unable to merge with the same error message as missing Adobe PDF resource. Adobe 2017 pro has been removed using the adobe cleaner and resintalled as well as the O365 applications.

Hello! I have a user who just moved to a new laptop after the old one broke. He was able to combine files as a PDF on his old computer, but on the new one, it has started pulling up this error. We are running Acrobat XI Pro with O365. Of the 5 files he tried to combine, 3 of them worked, but the 2 Excel files were the ones coming back with the error. We have ran up to the newest update and have also installed the C++ runtime linked previously in this forum. Are there any other workarounds for this?

Attached the error for a visual

There is an issue with the latest update of Adobe Acrobat (Version 2017.011.30190) that causes the application to state an error that the application is requiring resource files.- You must have Admin privileges to install these files.

We ran a repair as an Admin, but the issue remained.

Please fix this as the only workaround is to run a complete uninstall and reinstall of a working older version of Acrobat 2017. Which takes about 15- 20 minutes from start to finish.

Can you give us a sense of what the update will look like? Will it just be another Acrobat update like the one that broke it? will that us to a new version like 17.011.30191?

And can you give us a sense of timeframe? will the fix in a day? week? month?

finally, will the fix actually include VC++ as part of the install? or will the fix eliminate the need for VC++ redis to be installed? Could we remove it after we install the fix update? we didnt need it before so hopefully we wont need it after.

worked for me - trying other users now

I just applied to Adobe Pro 2017 and now it works perfectly! thank you for the workaround! It's a good day in the office now.

Hi everyone,

We have idenitifed the cause of the issue and will be providing an update with the fix shortly.

Meanwhile, please install VC++ Runtime from https://aka.ms/vs/16/release/vc_redist.x64.exe

This should solve the issue and conversion should start working.

Thanks for your patience!

Regards

Sagrika

I just applied the VC_redist.x64.exe that was mentioned. Then I upgraded to the 30190 version of Acrobat and my problems are gone on my machine. I am using Office 2016.

FYI to everyone having this issue. I've been working with Adobe support and the below solutions seems to be working for us.

I pushed out Microsoft Visual C++ 2015-2019 Runtime 14.28.29325.2 to four different PC’s that were having the issue, they now are working correctly.
This is with Office 2019 BTW

Same issue started for our standard users on 2/9/2021. Users are able to print to PDF, but can't convert, save as PDF, create form from document, etc. We are Windows 10, Office 2019, with Acrobat 2017. Uninstall/reinstall works as a work-around, but only if you don't check for and run all updates after the reinstall, and if you disable auto-updates.

We noticed this issue doesn't seem to affect the IS team, however. Perhaps this is related to the Admin privileges the error refers to. Will test by adding standard user as an admin to their PC.

Same thing for Office 2016 using Acrobat 17(latest patch).

I would have no issue doing a remote support session with Adobe in order to demonstrate how the latest update breaks the add-in for Outlook and also causes the issues with the other Office products. I am now up to 10 users that I have had to uninstall Acrobat 2017 and then let it only do one update cycle. That includes my machine so that I could verify the workaround worked.

Several Users have issues converting to PDF after 17.011.30190 update. This is a Win10 environment using Office 2013. Most get the attached error. Reinstall has help a few, but for some the problem persists.

We're seeing the same problem with Windows 10 and Office 2019 after installing the 2017.011.30190 update. When does Adobe anticipate issuing an update to resolve this problem?

Environment is Office 2016 Standard and Win 10 both running latest patches from MS.

When end users click file than "Save as Adobe PDF" the receives the attached error that states "Unable to find "Adobe PDF" resource files." This error also occurs if the click the ADOBE tab in the ribbon and choose any option there. This started once patch 2017.011.30190 was installed.

Re-install Adobe will work initially until patch is installed.
Repair has not helped at all.
Re-installing printing has not helped
Clicking Save as than changing file type to Adobe PDF does work.
Uninstalling Adobe plug-in removes option but re-installing does not make a difference.

Any additional troubleshooting or fixes we could implement would be appreciated.

Having same issue company wide since installing patch 2017.011.30190. Environment is Win 10 Office standard 2016. Fresh install of Adobe 2017 standard and everything works. Once the software is patched to 30190 print to PDF button and ribbon tab for Adobe all give same error.

Thanks everyone for reaching out!

We are looking into this issue on priority. The issue is not reproducible on our end hence taking longer to resolve.

Meanwhile, please try any of the below workarounds:

Convert the documents from within Acrobat:
1. Go to Tools->Create PDF->Single File. Select the document to be converted. Click Create
OR
Drag and drop the document in Acrobat.
2. Right click on the document in Windows Explorer. Select "Convert to PDF".

We have seen above workarounds to be working for some of the users. Please let us know if you still get error with these.

Regards

Sagrika Khandelwal

I am getting the same error when trying to save as PDF in PowerPoint and in Word. Please see attached error message.

I have Adobe Acrobat Pro 2017 and have checked for updates. I have also updated Windows.

This is super frustrating as I use Adobe Acrobat Pro all the time. Please share a fix.

Confirmed same issue in our environment on three machines since the update was installed.