Running compatibility mode worked for me. I'm not sure what changed between 3.5.x to 4.6.x but it seems to cause issues with applications which target that version of. NET and it seemed ok with every version until we got to 4.6.x. I had an application at my office which also relied on. If it opened SOME pdfs I think there is room for more considerations but if it won't open any at all I'm guessing it's a. NET and the older 9.x version of Acrobat might be looking for something that isn't there. NET Framework (4.6.x I think) and Adobe Acrobat products rely on. Now try and see if you an move the pages around in this PDF. Navigate to the PDF that's causing issues, select it and click Add Files. In addition, you can cast any of the PDFEdit objects to a PDEObject and use it anywhere a PDEObject is called for, such as in the PDEObject. Choose File > Create > Combine Files into a Single PDF. You can then cast and apply that class' methods to the object.
You can find the type of any object with the PDEObjectGetType() method. Fresh installs of 10 come with an updated version of. PDEObject: PDEObject is the abstract superclass of PDFEdit classes. Update: I guess I should clarify why I think it's compatibility with 10. They only mention older Operating Systems so there might be an underlying compatibility issue if it's a fresh W10 install rather than an upgrade from an older OS.
I'm betting it's an OS compatibility issue. Try running it in compatibility mode for W7.
