PDF Files Not Openning in Dir Opus When Double Clicked

After updating Dir Opus to 10.5.0.0 (4779) 64 bit version whenever I double-click a PDF file in Dir Opus it will not open the PDF file. I have also tried highlighting the file and right-clicking then choosing Open from the context menu, but still won't open. If I bring up task manager Adobe Reader is running in the background, but it is not showing on the desktop. I can double-click a PDF file in Windows Explorer, a PDF file on the Desktop, etc... and it opens fine. Before updating Dir Opus, I could open PDF files from Dir Opus fine.

Using Windows 8 Pro 64 bit and Adobe Reader 11.0.1.

Thanks....

Try using the Open With menu to (re-)assign Adobe Reader as the default PDF handler. Does that solve it?

I tried that, didn't fix the problem. If I assign Reader (the built-in PDF reader in Windows 8), then double-click a PDF file within Dir OPUS it opens fine in the Windows 8 Reader. I just found out that if I choose Open With from the Context Menu then choose Adobe Reader, it will open the PDF (no matter what is assign to open PDF files). But double-clicking the PDF file or choosing Open from the context menu within Dir Opus will not open the PDF file, even though if I check task manager Adobe Reader is running (in fact I have to End the Adobe task in Task Manager to be able to open a PDF file from anywhere).

I also have Dir Opus on my laptop. I updated Dir Opus to the newest version on the laptop and I can open PDF files fine by double-clicking them within Dir Opus. The laptop has Windows 7 Ultimate 64 bit. So it must be some Windows 8 problem.

Anyone else able to re-create this bug? Thanks.....

Well this is weird, but it's working now. All I did was launch Dir Opus from the Metro Interface (I think that is what they call that tile thing desktop in Windows 8). After that it now works even if launched from the Desktop screen and even after a reboot. Maybe it has something to do with I have Start8 install and set to boot to Desktop, not that Tile Metro thing. So maybe it just needed to be run from the Metro screen once. Who knows.....

I have the same problem. PDF file will not open from within DO using Acrobat reader XI. Looking in the task manager acrobat has started running in the background but has not opened the file. If I try opening same file from explorer it open ok.

Using Windows 8 64bit, DO light 10.5.0.0 (4779) 64bit

I also have the same problem. Double-clicking certain PDF files with DO will open them in the text editor instead of in Adobe Acrobat 10. Applying "Open" "and "Open with" on these problematic PDF files within DO work fine - they open in Acrobat. I don't experience any of these problems with Windows Explorer.

Env: Win 8 64-bit, DO 10.5.2.5 Beta or 10.5.2.0, Adobe Acrobat 10.2

NOTE: If I "Save As" these problematic PDF in Acrobat 10, it fixes the problem -- the PDF files will now open properly in Acrobat using DO double-clicking.

I'm not sure what to make of this. I thought the file manager would simply send the command based on the set file association. Does DO inspect the file structure before sending to Acrobat?

EM

Does it make a difference if you turn off Preferences / File Operations / Double-click on Files / Open unregistered file types in text viewer if they appear to be plain text?

Yes, turning off "Open unregistered file types in text viewer if they appear to be plain text" fixed the issue.

I've isolated the source of these problematic PDF files to a web service that generates PDF reports. So it looks like it's an isolated case.

Thanks for the quick resolution.

EM

If you're comfortable using RegEdit, have a look under HKEY_CLASSES_ROOT and see if there is a .pdf key below it.

I suspect that key is missing, which is why Opus is acting as if .PDF is not a registered file type.

Probably dependent on what creates them, some PDF files are all (or mostly) plain text, so they may be detected as text files.

Installing or repairing Acrobat (or anything else that deals with PDF files) will probably repair the filetype, and I'm guessing it was broken by installing/uninstalling things which weren't careful with maintaining the filetype.