See more in-depth tips of the same method here: with additional troublehsoting tips This is by far the best method I've found to do this. The best approach that you can follow is to create a batch script like shown here: to re-register all of your DLL's and discover exactly to which programs they are associated with.

PS: I think you can reasonably assume that there will be 64-bit Acrobat/Reader for Windows. On the other hand, an exceptionally large and graphically-complex single page PDF file just might be an issue.Īgain, we would like to work with you to track down the problem (and perhaps make the case of 64-bit Acrobat on Windows sooner rather than later). Note for the record, that Acrobat doesn't attempt to read the entire PDF file into memory at one time and thus, the file size itself wouldn't be the governing factor. That is not saying that a problem of crashing (or other anomalies) due to running out of 32-bit address space couldn't happen, but I would really like to see examples to make the case for 64-bit. Please contact me via private message on these forums with a pointer to such a file and I will gladly pursue this.įWIW, I have personally opened up exceptionally complex, graphic arts-based PDF files of over 500 megabytes in size and upwards of 100,000 pages with Acrobat Pro on Windows without any crashes. 32-bit versus 64-bit), a software bug, a problem with the PDF file itself, or something else. If you would be willing to share a file that crashes Acrobat Pro on Windows due to size or complexity, we would be glad to examine what is going on and determine whether the issue is truly an address space issue (i.e.

Adobe reader dc download for windows 10