Update v. 17.011.30190 broke Adobe PDF printer for MS Office products

[Ulster5DDA]

The most recent update (came out on Feb. 9th) that Adobe put out for their Adobe 2017 product messed up the Adobe PDF converter.  users are getting the error: "Unable to find 'Adobe PDF' resource files. 'Adobe PDFMaker'. Their last release v.17.011.30127 it works fine with, but with the new one v. 17.011.30190 users with in the company I work for are mo longer able to convert files to PDF’s. This updates seems to only effect Office products like Outlook, Word and Excel. It works okay when trying to convert the a .txt or a jpg for example. Users that are on the older update v.17.011.30127 are able to still convert for example Microsft Word documents into PDF. Is their any fixes for this?

I have tried uninstalling, restarting PC and reinstalling Adobe 2017, but didn’t fix the issue. I have also tried uninstalling the Adobe PDF converter printer and reinstalling it, as well as giving full permissions to the user’s Adobe folder in the C:Drive, but both didn’t work. The only way it works currently is by rolling back the update and use the product on the older update v.17.011.30127. 

[Bevi Chagnon - PubCom.com]

That's unfortunate and disastrous for Windows users.

But this is a user-to-user help forum, and Adobe's engineers rarely see these posts.

Please post the bug in the www.Acrobat.UserVoice.com forum where Adobe moderators will see it. And be sure to log it as a bug, not a feature.

[AkanchhaS]

Hi, 

Thank you for reporting and detailed description given. It seems that you have tried almost all the possible troubleshooting steps.

Just wondering, have you tried the exact same steps explained here https://community.adobe.com/t5/acrobat/unable-to-find-quot-adobe-pdf-quot-resource-files/td-p/874959... for adding PDF printer manually or not? 

Let us know if it still didn't work.

Thanks,

Akanchha 

[Ulster5DDA]

Yeah I tried those steps from the link and it's still getting the error.

[Mike1979]

Same issue here, starting today.

[rwtf]

We are seeing this too, multiple users.

To roll-back do you just reinstall the old patch .msu?
Umm 17.011.30127 isnt the immediate patch after .30190, that's 17.011.30188
https://ardownload2.adobe.com/pub/adobe/acrobat/win/Acrobat2017/1701130188/Acrobat2017Upd1701130188.... or
https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/classic/dcclassic17.011december202...

[Mike1979]

In the meantime we've advised users to use Microsoft's PDF printer.

[rwtf]

Had someone need to combine like 12 Excel files with Combine tool and it seems to enforce using that PDFMaker plugin.

But yeah quick workaround is use Export > Create PDF or Save > PDF, etc.

[rwtf]

Update, works for at least 1 of my computers with Office 365, its possible the issues are with Office 2016?

[rwtf]

Works in Office 365, doesn't work in Office 2019 is what I see currently. Can replicate issue.

[jasonk18537953]

Can confirm that we are also beginning to see this in our environment. Running 64bit Office 365 and Acrobat Pro 2017.011.30190. Have been so far unable to resolve.

[kassb62933232]

We're having this issue as well. So far its been with 2019, though on my own computer I'm running 2019 and Acrobat 2017 30127, and its not a problem.

So far, I've been able to resolve by fully uninstalling and reinstalling 

[kassb62933232]

on compters that havn't yet got the 30127 update (and the computers on which I reinstalled), I sent the following command remotely to disable Adobe's automatic updating:

reg add "HKLM\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\1.0\ARM" /v iCheck /t REG_DWORD /d 0 /F

It just replaces this key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\1.0\ARM]
"iCheck"=dword:00000000

There's a similar "Mode" key that you might want to change as well, if you want to be thorough about things.  

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Acrobat\{_____}

[rwtf]

There is no way to roll back, from what I have found. Must uninstall current version and reinstall. It is intermittent though, but not sure the cause.

[Marco5FAD]

Reinstalling Adobe using the Acropro.msi (deactivating) fixes the problem temporarily 

you need to run  Acropro.msi  to install it again.

[itperson000]

We are seeing the same issues with users users with Office 2019 and Adobe 2017 version 17.011.30190.  They cannot use the Office plug in to create pdf files - we can do print to pdf.  We installed Adobe DC for some users and this corrected the issue.  Adobe support also suggested reinstalling 2017 and said they were working on a fix.   

[sagrika]

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:

1. Convert the documents from within Acrobat:
   • 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

[jamesh60429279]

We've been getting the same.  A total reinstall helped some people, but for other's it just comes back.  There is a bug fix report here:  https://acrobat.uservoice.com/forums/590923-acrobat-for-windows-and-mac/suggestions/42713618-acrobat...

[kassb62933232]

are they set to auto-update? I've turned that off until this is resovled 

[mesoscaled53068104]

Same issue here... Office 2017 Acrobat Std 2017, many machines, only fix so far is to reinstall and not let it update to 2017.011.30190... grrrrr

[mesoscaled53068104]

Thank you...  Microsoft Visual C++ 2015-2019 Runtime 14.28.29325.2 has resolved the issue

[rreynolds]

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

[itperson000]

How are you pushing it out?  Is there a KB for the update? 

[rreynolds]

We use PDQ Deploy, highly reccomended!

I believe you can get the runtimes directly from MS

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

[sagrika · Accepted solution]

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