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.

I have a legal copy of Acrobat Pro X (Creative Suite) that I love (I use it over Creative Cloud supplied by my employer). PROBLEM: I cannot have Reader DC (needed for shared forms sent to me occasionally) installed at the same time as it always acts as default app even though the Windows 10 default app still lists Acrobat Pro. This is as infuriating as when Edge automatically changes this every time there is a Windows update. I already own Finereader 15 that does everything Acrobat does and more and does not require a monthly subscription. You lost a customer when you made your business model change, but stop trying to control my computer.

Acrobat Reader DC was updated to ver.20.012.20041 the other day.

Since then, the following error message appears when printing with the command.

Adobe Acrobat Reader DC has stopped working
The program did not work properly due to a problem.

The program will close and Windows will notify you if there is a solution

Printing is done just by issuing a message.

The command I am using is:
"C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe" /n /p /h "<PDF file path>"

The execution environment is as follows.
OS: Windows 7 Professional sp1 64bit
Processor: Intel(R) Core(TM) i7-6700 CPU @3.40GHz 3.40GHz
RAM: 8.00GB

The following Windows logs are written when an error occurs.

The faulty module name may be "AcroRd32.exe" or "AGM.dll".

Faulting application name: AcroRd32.exe, version: 20.12.20041.1044, time stamp: 0x5f23643d.
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000001
Faulting process ID: 0x140c
Start time of the failing application: 0x01d670f162c5aeb7
Faulting Application Path: C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe
Faulting module path: unknown

Report ID: a3b35ad8-dce4-11ea-88ac-484d7ef98554

• The content of the error is the Japanese translation into English by google translation.

Verion 20.006.20034.39303

When copying from a PDF document the text gets cut off after the SECOND letter 't' when trying to paste.

Steps to reproduce:

1) Open the PDF document attached to this
2) Go to the first page of PDF
3) Highlight the sentence "If the input parameter is a timestamp (without time zone) it applies the offset of the time zone you specify and returns a timestamp with the time zone."
4) Paste into a text editor

Expected Results

All the text is copy/pasted

Observed Results:

Only the following is pasted:

"If the input parameter is a"

Very odd!!

I am using the Adobe Reader Javascript API and trying to access the this.pageWindowRect variable. I've found from various forum posts that this has to be 'enabled' by accessing this.media first.

This works most of the time, but intermittently on certain computers, I find that both this.media and this.pageWindowRect are undefined.

It is difficult to reproduce this exactly: sometimes it seems to work fine, and sometimes they seem to stay undefined. I've tried delaying my code - in case things are taking a while to load - and running the code from a document-level script, a button, and the console. It all seems to work intermittently.

The attached file has a timer running in the document-level JS, which prints out the value of these variables every few seconds for a couple of minutes (in case the initialisation is delayed). On most computers this seems to work fine, but on some computers both variables return 'undefined' for the entire period the code is running.

Any support or advice would be much appreciated.