- or
8 results found
-
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 -
Protected Mode prevents opening Links to PDFs on DFS
Linking in the PDF to another PDF on the DFS doesnt work. Acrobat Reader Resolves the Path right because the Security-Warning shows the path behind the DFS.
When opening the PDF from the UNC path the links work
After disabling the option "Enable Protected Mode At Startup" the link works from the DFS too
Adding the Servers/Domain Name to the Trusted Sites doesnt work.
1 vote -
Can't open more than 1 file at a time
Clients with Windows 10 1809 or more (or Win2019) trying to access a PDF via a DFS that is stored on a Windows server 2019 server are not able to open more than 1 pdf.
Can this please be fixed as Windows Sever 2019 is being used more widely.
8 votes -
Bug report: cannot save PDF in Windows 11
When a PDF file is opened from a mapped share e.g. N:\test.pdf which is mapped to a Windows 2022 DFS share e.g. \contoso.com\dfs\myshare\test.pdf. In Windows 11 when saving this file adobe reader prompts the message: "This document could not be saved. Cannot save to this filename. Please save the document with a different name or in a different folder". And the app suggests a temp folder on the computer with at temp file name. This issue only happens in Windows 11 and not in Windows 10. The issue has been tested with the same user account on both…
12 votes -
FIX Problem security with Adobe Reader WIN10
No reaction when trying to open a .pdf file from a network share available under DFS with a previously running .pdf document locally.
The problem with .pdf files not working properly in correlation with DFS is the Adobe Reader application bug.Bug exist from begin od 2018.Adobe products cannot cope with distributed file systems.The observed bug occurs in WIN SRV 2016 and 2019 systems, and unless it is explicitly stated anywhere that the reason is the change in the SMB authentication method, this is indicated by (logically) the AR logs.this is a link to a thread on this topic https://community.adobe.com/t5/acrobat-reader/can-only-open-1-pdf-at-a-time-from-dfs…1 vote -
Protected Mode prevents opening a second PDF from an SSHFS-Win/WinFsp network drive
Steps to reproduce:
1. Enable "Protected Mode at startup" in Adobe Acrobat Reader.
2. Completely exit Reader.
3. Open File Explorer and navigate to an SSHFS-Win/WinFsp network drive mapped as Z:.
4. Double-click a PDF. It opens normally.
5. Leave Reader running.
6. Return to File Explorer and double-click a different PDF on the same Z: drive.Environment:
- Windows 11
- Adobe Acrobat Reader Continuous Release 2026.002.21931, 64-bit
- SSHFS-Win / WinFsp
- Network drive mapped as Z:
- Windows reports the remote path as \sshfs\kalmer@192.168.1.173....Expected result:
The second PDF opens in the already running Reader…1 vote -
Acrobat Reader crashes when opening printer properties for RISO ORPHIS FT5230
Adobe Acrobat Reader crashes consistently when I open the printer properties for a RISO ORPHIS FT5230 printer.
Steps to reproduce:
- Open any PDF file in Adobe Acrobat Reader.
- Open the Print dialog.
- Select RISO ORPHIS FT5230.
- Click the printer “Properties” button.
- After several seconds, Acrobat Reader terminates without displaying the printer properties.
Environment:
- Adobe Acrobat version: 26.1.21771.0
- Operating system: Windows 11 64-bit
- Printer: RISO ORPHIS FT5230
- Computer environment: Windows domain-joined PC
- Faulting application: Acrobat.exe
Windows Error Reporting information:
- Event name: BEX64
- Exception code: 0xc0000409
- Failure module: unknown
- Stack hash: StackHash_49ca
- Additional value: P9 = 000000000000000a
- Report ID: 10d95908-8955-4364-b2a4-209df3a94f74
Comparison tests:
- …
2 votes -
PPKLite causing Crashes on document close.
Product: Adobe Acrobat (Windows, 64-bit), version 26.3.22075.0 OS: Windows 10 22H2 (build 19045) Issue: Acrobat crashes with an access violation (0xc0000005) when a document or Acrobat is closed. The user sometimes sees a blank crash dialog. No work is lost. It happens on most working days, usually after the user opens a PDF attachment from Outlook, reads it, and closes it. Crash signatures (Windows Event ID 1000): - PPKLite.api +0x114c77 (same offset on every build) - Acrobat.dll: offset changes per build; +0x9466a8 on 26.3.22075, +0x51e5b8 on 26.2.22031 Dump analysis (WinDbg, full user-mode dumps): - Both signatures crash on the same…
1 vote
- Don't see your idea?