Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

Bug/Issue in Reader DC 19.010.20069 with printing/saving PDF files.

Community Beginner ,
Feb 06, 2019 Feb 06, 2019

We have found that after after our clients auto-upgrade from version 19.010.20064 to version 19.010.20069 we can not longer print PDF files or save them.

We have approximately 80 identical Windows 10 PCs that are all using 19.010.20064.  As they upgrade themselves to version 19.010.20069 they are no longer able to fill out PDF forms from a shared network folder and print or save the form.  When printing the form, the only thing that prints is the data they have input and not the form itself.  When they try and save the form they get an access denied error.   The print preview window only shows the form data the user filled in and not the form so it is an accurate reflection of what prints.   This problem is not dependent upon the printer because we have machines at different sites with different printers/drivers.

I have done some testing.  I loaded several new PCs from scratch using windows 10 build 1809 and ran a full windows update.  Then i installed version 19.010.20069 and opened the PDF form and filled it out.  The problem occurs as I described above.  I then uninstalled 19.010.20069 and installed 19.010.20064 and the problem is gone.  I also tested just installing 19.010.20064 on a fresh build and the problem doesn't occur.  

Unfortunately, the update to 19.010.20069 is installing automatically on the machines i have downgraded to 19.010.20064.  So our users are having issues daily.

I know i can stop automatic updates from installing, which I might do for the short term.  However, in the long term a solution must be found because I can't go without updates for very long.  My auditors will eat me alive.

I also tested the PDF files using Foxit Reader and Edge and both do not exhibit the problem.

Has anyone else seen this issue?  Does anyone have any suggestions?

843
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 07, 2019 Feb 07, 2019

Bump.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 08, 2019 Feb 08, 2019

Anyone?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 11, 2019 Feb 11, 2019

Anyone at Adobe Listening?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Mar 11, 2019 Mar 11, 2019
LATEST

We switched all of our machines to FoxIt reader.  The problem seemed to be with Adobe.  Since Adobe doesn't seem to care enough to respond it looks like we made the right choice.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines