647 results found

1. Add Indigenous Languages to Acrobat

   From an inclusion lens, there's a significant population of Indigenous peoples whose language is not represented in any Adobe products. More Indigenous languages should be added to Acrobats language capabilities to inform screen readers of how to properly output Indigenous words.

   There are two problems with how Adobe is approaching its lack of inclusion of Indigenous languages.

   1. There should be more Indigenous languages added.
   2. The mono-language setting for a document is limiting and doesn't allow for the diversity of multiple languages to help communicate the message appropriately.

   There are over 70 Indigenous languages in Canada. Adobe is a leader in the community for reviewing PDFs however right now screen readers are not supported by Adobe's language capabilities by including Indigenous languages. Screen readers are limited to only speaking in either English or French in a document rather than interpreting the information properly and outputting Indigenous pronunciations. From an accessibility perspective, it's mandatory to set the language of a PDF document so that screen readers can interpret the information properly however if your document is in a language that's not available in Adobe's language settings then it's impossible to truly make that document accessible.

   Mono-language is a limitation imposed by Adobe's software where we can only set one language for the entire document. This is limiting because often when working with information for Indigenous people there's a need to have both their Indigenous language represented and also a translation of that as well into most often English or French. Screen readers are not able to detect a language, then switch partway through the document, and Adobe's language settings are not robust enough to account for Indigenous languages since it's not equipped with them. The result is that the section with the Indigenous language gets read in the set language of the document which can lead to confusion on the user end since there's incorrect pronunciation and no indication that there's been a language change.

   There's definitely an option to do better and provide more flexibility here by offering more Indigenous languages available as well as creating a feature to add multilingual language settings within a document.

   From an inclusion lens, there's a significant population of Indigenous peoples whose language is not represented in any Adobe products. More Indigenous languages should be added to Acrobats language capabilities to inform screen readers of how to properly output Indigenous words.

   There are two problems with how Adobe is approaching its lack of inclusion of Indigenous languages.

   1. There should be more Indigenous languages added.
   2. The mono-language setting for a document is limiting and doesn't allow for the diversity of multiple languages to help communicate the message appropriately.

   There are over 70 Indigenous languages in Canada. Adobe is a leader in… more

   71 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   14 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Fix Issue: Protected Mode prevents 3D PDF rendering hardware acceleration with NVidia graphics

   If using a PC with NVidia graphic cards, hardware acceleration is automatically deactivated if protected mode on startup is active. This slows down 3D PDFs significantly.

   Deactivating Protected Mode on Startup allows for hardware acceleration again.

   50 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   14 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Build in an EPUB Reader and Allow for EPUB Embedding

   The Reader app (all platforms) should be more generalized to allow "reading" of both EPUB or PDF documents.

   Similarly, we should be able to embed an EPUB into a PDF file. (PDF has a robust method that allows it to embed other file formats.)

   Then, we should have a switch in Reader that would let a user to switch from PDF to reflowable EPUB and back again.

   While I understand that Adobe is investing heavily in Liquid Mode, this EPUB method would be far more reliable for people who need to control the design of both static and reflowable modes.

   36 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Under review  ·  AdminAyush Jain (Lead Software Engineer, Adobe) responded

   Hi,

   Thanks for reaching out to us for your concerns.

   We have no immediate plans to work on this FeatureRequest.

   We will let you know if this get prioritized for our Future versions.

   Thanks
   Ayush Jain

4. BUG - Adobe Reader is Corrupting URL Links

   Adobe Reader DC corrupts URLs in external links when the PDF is encrypted.

   This does not happen in other PDF readers.

   We create password protected PDFs which contain links to external URLs.
   These links work fine when we view the generated PDFs in chrome and firefox.
   But the links are getting corrupted by Acrobat Reader.
   One or more characters are getting corrupted (e.g "https://mywebiste.com/1234567" is trying to link to "https://mywebiste.com/123:567" or "https://my?ebiste.com/1234567")

   I have attached a sample file.

   This problem persisted when there was only one link at the location and if a longer password was added.

   It is the latest version of adobe reader - 2022.003.20282

   Adobe Reader DC corrupts URLs in external links when the PDF is encrypted.

   This does not happen in other PDF readers.

   We create password protected PDFs which contain links to external URLs.
   These links work fine when we view the generated PDFs in chrome and firefox.
   But the links are getting corrupted by Acrobat Reader.
   One or more characters are getting corrupted (e.g "https://mywebiste.com/1234567" is trying to link to "https://mywebiste.com/123:567" or "https://my?ebiste.com/1234567")

   I have attached a sample file.

   This problem persisted when there was only one link at the location and if a longer… more

   • 

   32 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   6 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. The Renderer of Acrobat Reader DC 64-bit

   [Problem]
   Comparing Acrobat Pro/Reader 32-bit, the PMI and the outline of 3D model are unclear on Acrobat Reader DC 64-bit.
   (Please find the attached sample PDF and captures, test01-03.)

   "DirectX 9" is able to be selected from the renderer option on Acrobat Pro/Reader 32-bit.
   (Edit -> Preferences -> Multimedia & 3D -> Preferred Renderer)
   However, it doesn't exist on Acrobat Reader DC 64-bit. So, only "Software" is available.
   Therefore, the PMI and the outline of 3D model are unclear.
   (Please find the attached captures #1&#2.)

   [Tested Acrobat Version]
   Acrobat Reader DC 64-bit: 2021.011.20039
   Acrobat Pro 2020 32-bit (classic): 2020.004.30020
   Acrobat Reader DC 32-bit: 2021.007.20099

   [Request]
   Please make “DirectX 9” selectable on Acrobat Reader DC 64-bit.

   [Problem]
   Comparing Acrobat Pro/Reader 32-bit, the PMI and the outline of 3D model are unclear on Acrobat Reader DC 64-bit.
   (Please find the attached sample PDF and captures, test01-03.)

   "DirectX 9" is able to be selected from the renderer option on Acrobat Pro/Reader 32-bit.
   (Edit -> Preferences -> Multimedia & 3D -> Preferred Renderer)
   However, it doesn't exist on Acrobat Reader DC 64-bit. So, only "Software" is available.
   Therefore, the PMI and the outline of 3D model are unclear.
   (Please find the attached captures #1&#2.)

   [Tested Acrobat Version]
   Acrobat Reader DC 64-bit: 2021.011.20039
   Acrobat Pro 2020 32-bit (classic): 2020.004.30020
   Acrobat… more

   •  

   •  

   •  

   •  

   •  

   • 

   31 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Please stop adding desktop shortcut when Reader is updated

   Already using the application, hence it being updated, don't need desktop shortcut to re-appear every time the application is updated.

   28 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   14 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Acrobat Reader unable to access files via junction reparse points

   Acrobat Reader is unable to correctly interpret some mountpoint reparse points (junctions). In practical terms: Acrobat Reader is unable to access PDF files from file systems mounted as directories and this is the root cause of the problem.

   Junctions are special symbolic links that are used in many scenarios; an important one is when a file system is mounted as a directory rather than a regular drive. Junctions contain 2 paths: a “substitute” path which must be a path in the NTOS namespace (not a Win32 path) and a “print” path, which is to be used for display to the user.

   A junction that is used to mount a file system on a directory might have a target like \Device\Volume{GUID}, which might be a file system device. Unfortunately targets such as \Device\Volume{GUID} appear to create problems for Acrobat Reader because it interprets them as the Win32 path C:\Device\Volume{GUID}, which is incorrect.

   For more information on this problem please see this GitHub issue:
   https://github.com/billziss-gh/winfsp/issues/274

   I am the author of the WinFsp software, which can be used to create file systems and I am happy to answer any questions you may have about this problem.

   Acrobat Reader is unable to correctly interpret some mountpoint reparse points (junctions). In practical terms: Acrobat Reader is unable to access PDF files from file systems mounted as directories and this is the root cause of the problem.

   Junctions are special symbolic links that are used in many scenarios; an important one is when a file system is mounted as a directory rather than a regular drive. Junctions contain 2 paths: a “substitute” path which must be a path in the NTOS namespace (not a Win32 path) and a “print” path, which is to be used for display to… more

   25 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   5 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Fix Multi-PDF issue from Win2019 DFS share to Win10 clients..... please.

   The DFS bug has shown it's head again. Win 2019 servers offering DFS fileshares to Win10 clients will no longer allow multiple PDFs to be opened from the OS interface, because of Protected Mode.

   Any other combination works fine (non-Win2019, non-Win10, non-DFS shares, disable Protected Mode).

   Now that the vastly popular Win 2008r2 is out of support, many more organizations are upgrading to Win 2019. Disabling Protected Mode via registry GPO is a poor workaround.

   Please fix!

   19 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   10 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Bug? Problem with Color Management (wide gamut monitor)

   When viewing PDF documents containing images on my wide gamut monitor using Acrobat Read DC (Windows 10), images have oversaturated colors.
   The same PDFs looks OK when opened in Photoshop or previewed in Bridge.

   See also this thread:
   - https://community.adobe.com/t5/acrobat-reader/problem-with-color-management-wide-gamut-monitor/m-p/10982293

   I have done some systematic testing. There seems to be a color management problem/error in the (urrent Windows version of Acrobat Reader DC:

   Procedure

   I have made two test images:

   • image-AdobeRGB.jpg: - a JPEG image file with an Adobe RGB (1998) embedded color profile
   • image-sRGB.jpg: - a JPEG image file with a sRGB IEC61966-2.1 embedded color profile

   For each image I have generated a PDF document using both Bridge and Photoshop. This results in 4 PDF files:

   • image-AdobeRGB-BRIDGE.pdf: - image-AdobeRGB.jpg has been used in the Output module of Bridge
   • image-AdobeRGB-PHOTOSHOP.pdf: - image-AdobeRGB.jpg has been used in Photoshop ("Save As": Photoshop PDF)
   • image-sRGB-BRIDGE.pdf: - image-sRGB.jpg has been used in the Output module of Bridge
   • image-sRGB-PHOTOSHOP.pdf: - image-sRGB.jpg has been used in Photoshop ("Save As": Photoshop PDF)

   Each of the 4 PDFs has been opened in three applications:

   • Bridge (10.0.3.138 x64)
   • Photoshop (21.1.1 20200312.r.121 2020/03/12: c839971b587 x64)
   • Adobe Acrobat Read DC (20.006.20042)

   The process is shown in the attached two diagrams (as JPEG image files):

   • diagram-AdobeRGB http://jjohanson-test.com/acrobat-readerdc/diagram-AdobeRGB.pdf
   • diagram-sRGB http://jjohanson-test.com/acrobat-readerdc/diagram-sRGB.pdf

   FINDINGS

   This has produced 12 sets of findings (4 PDFs times 3 apps).
   A summary:

   1) Previews in Bridge and Photoshops looks OK for all 4 PDFs.
   2) With two exceptions (see diagrams and *) Bridge and Photoshop indicates that the correct color profile is present.
   3) For all 4 PDFs Acrobat Read DC shows identical and wrong (oversaturated) colors.

   *) Bridge shows "Untagged" for the PDFs generated by Bridge. However, according to this:
   - https://community.adobe.com/t5/acrobat-reader/does-acrobat-reader-support-color-management-systems/m-p/11006133?page=1#M64420
   at least the the image in the Adobe RGB (1998) version of the PDF seems to have the correct profile.

   Speculation

   Since Acrobat Reader DC (ARDC) shows identical previews for all four PDFs (regardless of the image color profile used that also seems to be present in the PDF files), it seems reasonable to assume that ARDC takes the input profile into account (the profile(s) embedded in the PDFs). However, it seems that the output profile (in this case the profile generated while calibrating my Eizo wide gamut monitor) is not taken into account. This behavior mimics the behavior of some native Windows applications like the Edge browser and the Photos app (images with different embedded profiles are rendered identically, but with oversaturated colors on my monitor). It is interesting to note that both the Adobe RGB (1998) files and the sRGB IEC61966-2.1 files preview identically (to my eye) in both Acrobat Reader DC, the Edge browser (non-chromium) and the Windows Photos app. When using "standard" gamut monitors it will often be difficult to see that the colors actually are not correct.

   Test files for download

   All files can be downloaded here:

   • http://jjohanson-test.com/acrobat-readerdc/image-AdobeRGB.jpg
   • http://jjohanson-test.com/acrobat-readerdc/image-AdobeRGB-BRIDGE.pdf

   • http://jjohanson-test.com/acrobat-readerdc/image-AdobeRGB-PHOTOSHOP.pdf

   • http://jjohanson-test.com/acrobat-readerdc/image-sRGB.jpg

   • http://jjohanson-test.com/acrobat-readerdc/image-sRGB-BRIDGE.pdf

   • http://jjohanson-test.com/acrobat-readerdc/image-sRGB-PHOTOSHOP.pdf

   • http://jjohanson-test.com/acrobat-readerdc/diagram-AdobeRGB.pdf

   • http://jjohanson-test.com/acrobat-readerdc/diagram-sRGB.pdf

   My system details:
   - Adobe Acrobat Reader DC - 2020, Version 20.006.20042
   - Adobe Photoshop Version: 21.1.1 20200312.r.121 2020/03/12: c839971b587 x64
   - Bridge Version: Adobe Bridge 2020: 10.0.3.138 x64
   - Adobe Camera Raw Version: 12.2.0.386
   - Monitor: Eizo CG2730 (calibrated regularly with Xrite i1 Display)
   - Windows 10 Pro x64 version: 1909 - Os build 18363.752
   - Graphics driver: Driver version: 442.19 (GeForce GTX 1060 3GB)

   When viewing PDF documents containing images on my wide gamut monitor using Acrobat Read DC (Windows 10), images have oversaturated colors.
   The same PDFs looks OK when opened in Photoshop or previewed in Bridge.

   See also this thread:
   - https://community.adobe.com/t5/acrobat-reader/problem-with-color-management-wide-gamut-monitor/m-p/10982293

   I have done some systematic testing. There seems to be a color management problem/error in the (urrent Windows version of Acrobat Reader DC:

   Procedure

   I have made two test images:

   • image-AdobeRGB.jpg: - a JPEG image file with an Adobe RGB (1998) embedded color profile
   • image-sRGB.jpg: - a JPEG image file with a sRGB IEC61966-2.1 embedded color profile

   For each image… more

   •  

   •  

   14 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. v3 third-party update catalogs for MS Software Center

    Please create a v3 third-party update file for SCCM, so we are able to automatically download en deploy Adobe software updates to endpoints.

    More information about this new feature of SCCM 1910 see:
    https://docs.microsoft.com/en-us/configmgr/sum/deploy-use/third-party-software-updates#bkmk_1910

    13 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Bug - PMI cross-highlighting not working for 3D PDFs using 64 bit Adobe Reader DC

    Cross-highlighting of PMI is not working in the 64 bit version of Adobe Reader DC. This is the functionality that will highlight a surface(s) that the PMI is related to when selecting the PMI. A 3D PDF opened in the most current version of 32 bit Adobe Reader DC is working correctly, the same 3D PDF opened in the latest 64 bit version of Adobe Reader DC will not work.

    It's my understand that Adobe added this functionality around 2013, in Adobe Reader 11, I believe. It seems that 64 bit Adobe Reader DC has reverted back to pre Adobe Reader 11 functionality in this area.

    Cross-highlighting of PMI is not working in the 64 bit version of Adobe Reader DC. This is the functionality that will highlight a surface(s) that the PMI is related to when selecting the PMI. A 3D PDF opened in the most current version of 32 bit Adobe Reader DC is working correctly, the same 3D PDF opened in the latest 64 bit version of Adobe Reader DC will not work.

    It's my understand that Adobe added this functionality around 2013, in Adobe Reader 11, I believe. It seems that 64 bit Adobe Reader DC has reverted back to pre Adobe… more

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    5 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Windows 10 preview pane and # pound signs/hash tags

    Since the March 7th update, the Windows 10 File Explorer preview pane will display a directory listing instead of a preview of a pdf if a # (hash tag/pound sign) is in the directory name or the file name. Not all special characters have been tested.

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    7 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Very slow after window is resized or moving between monitors

    Adobe Reader is very slow after I resize the window on my Windows 10 laptop. This includes maximizing and restoring down a window. If I only open one document, it usually takes 1-3 seconds to respond, depending on how complicated the document is. This is already significantly slower than Firefox and Chrome. Furthermore, if I open two documents, resizing takes 3-6 seconds, and longer when more document tabs are opened. This is a big performance issue. Looks like Adobe Reader is rendering all the documents synchronously after the window is resized, which is completely unnecessary; it should only render the current tab synchronously and render the other tabs in the background.

    The two problems add up and cause significant performance issue when I try to move the window between monitors. The window often get stuck for at least 10 seconds, because it will do the inefficient rendering several times; one time for resizing the window on one monitor, one time for changing the scaling because two monitors have different DPIs, and one final resizing for maximizing the window on the new monitor. This results in an unacceptable "not responding" freeze.

    I do hope Adobe could improve the performance of PDF rendering. The current version is really wasting me so much time waiting for the frozen window.

    Adobe Reader is very slow after I resize the window on my Windows 10 laptop. This includes maximizing and restoring down a window. If I only open one document, it usually takes 1-3 seconds to respond, depending on how complicated the document is. This is already significantly slower than Firefox and Chrome. Furthermore, if I open two documents, resizing takes 3-6 seconds, and longer when more document tabs are opened. This is a big performance issue. Looks like Adobe Reader is rendering all the documents synchronously after the window is resized, which is completely unnecessary; it should only render the… more

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. BUG - "Acrobat Quit Unexpectedly" Message

    Adobe Acrobat Reader v2023.006.20320 64 bit.
    After the Windows September 2023 updates (Windows 11 Pro 22H2 22621.2283) I started getting the message "Acrobat quit unexpectedly" message.
    I get this message several times a day.
    I get the error even if I do not do anything related to Adobe Reader DC.
    I have a feeling this is related to the "Enable PDF thumbnail previews in Windows Explorer". I am saying this because if I turn off that setting, I do not get the error.
    I tried the troubleshooting steps but that did not help.
    Following the suggestion to enable the CrashDumps did not help. No CrashDumps are created when this message pops up.
    I also uninstalled Adobe Reader DC and used the cleanup tool. Then I reinstalled the latest version of Adobe Reader DC and the error message started showing up within minutes.
    There is an ongoing thread at https://community.adobe.com/t5/acrobat-reader-discussions/adobe-reader-quit-unexpectedly/td-p/14091441.

    Adobe Acrobat Reader v2023.006.20320 64 bit.
    After the Windows September 2023 updates (Windows 11 Pro 22H2 22621.2283) I started getting the message "Acrobat quit unexpectedly" message.
    I get this message several times a day.
    I get the error even if I do not do anything related to Adobe Reader DC.
    I have a feeling this is related to the "Enable PDF thumbnail previews in Windows Explorer". I am saying this because if I turn off that setting, I do not get the error.
    I tried the troubleshooting steps but that did not help.
    Following the suggestion to enable the CrashDumps… more

    •  

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Need Info  ·  9 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Bug: FlatDecode does not work for all PNG images in Acrobat Reader

    Using Adobe Acrobat Reader PDF DC (21.001.20138) on Windows 10 to open the attached PDFs crashes. We create PDFs ourselves with several hundreds of images and embedding them using FlatDecode to reduce the size of the PDFs however very few images seem not to work in Adobe Acrobat PDF viewer ONLY. Opening the PDFs in Google Chrome as an example works.

    •  

    •  

    • 

    • 

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Got problems after updating to 24.002.21005 version

    Since updating Reader to version 24.002.21005, some PDFs or PDFs from clients have been displaying font issues. However, the same files open correctly using other programs (Acrobat Pro, Chrome, Microsoft Edge, PDF Xchange, Abby, etc.). Please help us identify and resolve this issue, as it greatly affects us. Thank you.

    • 

    •  

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Mouse/cursor changes in reader window to a specific Reader mouse/cursor

    ... and I am not referring to the distinction between hand and select tool. I am referring to another problem:

    I have set my own cursor scheme for Windows (Lefty Scheme) in Windows system settings. Every application accepts that but Adobe Reader. Whenever using the reader the mouse changes from a white arrow pointing to the upper right corner (lefty scheme) to a black arrow pointing to the upper left corner.

    How can I change this? I want the Reader to use the Windows System setting.

    I am using Windows 10 Pro 64 Bit, Version 1709, OS Buils 16299.431 and Adobe Reader 2018.011.20038

    Many thanks for your help. Much appreciated

    ... and I am not referring to the distinction between hand and select tool. I am referring to another problem:

    I have set my own cursor scheme for Windows (Lefty Scheme) in Windows system settings. Every application accepts that but Adobe Reader. Whenever using the reader the mouse changes from a white arrow pointing to the upper right corner (lefty scheme) to a black arrow pointing to the upper left corner.

    How can I change this? I want the Reader to use the Windows System setting.

    I am using Windows 10 Pro 64 Bit, Version 1709, OS Buils 16299.431 and… more

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Sign in prompt Microsoft purview information protection

    When opening protected PDF's Adobe Acrobat prompts to enter user ID for authentication. It would be really great if the prompt is suppressed and the credentials can be taken from windows login session.

    This is very beneficial for enterprise customers who are currently suing non persistent VDI's which avoids them to enter the details on every login when trying to open protected pdf's

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Bug: Links to a rotated page fail to hit the right page

    With pdflatex we've created a document with a single rotated page. We've tried several PDF viewers, which work as expected, but Acrobat Reader (tested version 2024.001.20604 and some others) jumps to the wrong page when any of the hyperlinks are clicked on the TOC, the navigation bookmarks, or in the text.

    We've created a MWE that can be generated in overleaf (https://www.overleaf.com/read/yfwhpwjdcfvk#3d8e17). I attach also the PDF document showing the problem.

    Other PDF viewers tested, which work fine are: okular, evince, google PDF viewer, Edge PDF viewer, some Android and iPhone viewers, which jump fine to the expected page. Acrobat Reader jumps to one page after the desired one, but depending on the LaTeX code (using pdflscape, for example), it might jump to the weirdest places.

    With pdflatex we've created a document with a single rotated page. We've tried several PDF viewers, which work as expected, but Acrobat Reader (tested version 2024.001.20604 and some others) jumps to the wrong page when any of the hyperlinks are clicked on the TOC, the navigation bookmarks, or in the text.

    We've created a MWE that can be generated in overleaf (https://www.overleaf.com/read/yfwhpwjdcfvk#3d8e17). I attach also the PDF document showing the problem.

    Other PDF viewers tested, which work fine are: okular, evince, google PDF viewer, Edge PDF viewer, some Android and iPhone viewers, which jump fine to the expected… more

    • 

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Bug: quick print fails to print (non-default permissions)

    Failing in 32 & 64 bit versions 2023.001.20093 and 2023.001.10143 on Windows Server 2019 Remote Desktop Session Host (untested on other environments)

    Brief: Users with print rights assigned via a group, not direct permissions (see caveat below), quick print will open Reader but does not send a job to the printer (only Acrobat Reader, file types to other apps quick print fine)

    Extensive details (I have procmon captures too)

    Normal printing works fine. If they open a file with any application and file > print or CTRL+P etc. it prints successfully. Quick print opens Acrobat Reader, but in non-working scenarios the file doesn't ever show up visible but the recent says it was opened just now (working scenarios you see it open for a short period)

    Environment:
    - Windows Server 2019 Remote Desktop Session Host server with printers installed locally
    - Everyone group removed from printer and replaced by group user is a member of with print rights
    Note: this is a requirement, every printer cannot be visible/usable by all users.
    - Adobe Acrobat Reader DC (latest patches) is default for PDFs
    - Outlook Quick Print, right click > Print, or a custom app trying to quick print PDFs opens Acrobat Reader but does not print

    Working Scenarios:
    - Printer has the LOCAL groups Interactive, Users, or everyone added with read permissions and print (read alone is not enough)
    - Printer has the direct Active directory user added with read permissions and print (read alone is not enough)

    Failed Troubleshooting Tests
    So far I have found no other working scenarios. I have tried the below, and probably much more, with no success.
    - User with nested membership to Active Directory Domain Local security group with read/print
    - User with direct membership to Active Directory Domain Local security group with read/print
    - User with nested membership to Active Directory Global security group with read/print
    - User with direct membership to Active Directory Global security group with read/print
    - Assuming maybe a background item needed permissions, I tested with the following built-in local security principals with permissions ranging from read/print to all permissions (local): Authenticated users, LOCAL SERVICE, NETWORK, NETWORK SERVICE, SERVICE, SYSTEM
    - Active Directory computer account with read/print, manage docs, and manage printer

    Important notes:
    - Acrobat Reader must be closed between tests or after a successful test, if you remove the rights that made it successful, it will continue to work. However, after closing and re-opening it will fail again.
    - Best I can tell, restarting the print spooler doesn't matter. There was a period where I was restarting it regularly.

    • Windows Server 2012 R2 Remote desktop session host, locally installed printers with the same version of Acrobat Reader DC works with non-default permissions. Same with Windows 10 network printing to a server 2016 print server (non-default permissions).

    Extra info + description of attachments:
    The larger image is a side by side of procmon during a successful test, user is directly there with print permissions, (on the right) and a failed attempt, user has print access via a group (on th left). The Spooler-Between.png is the exact same in both scenarios and occurs JUST before the other image deviates from one another. Best I can tell it's not helpful.

    The default printer has been set via the legacy way, modern way, and set to let Windows manage (acrobat closed, user logged off and back on) and the issue persists.

    Failing in 32 & 64 bit versions 2023.001.20093 and 2023.001.10143 on Windows Server 2019 Remote Desktop Session Host (untested on other environments)

    Brief: Users with print rights assigned via a group, not direct permissions (see caveat below), quick print will open Reader but does not send a job to the printer (only Acrobat Reader, file types to other apps quick print fine)

    Extensive details (I have procmon captures too)

    Normal printing works fine. If they open a file with any application and file > print or CTRL+P etc. it prints successfully. Quick print opens Acrobat Reader, but in non-working scenarios… more

    •  

    •  

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close