Adobe Fails to Open PDFs from Network Path in Parallels Desktop on macOS

[WojciechS4]

Hi,
I'm encountering an issue with opening PDF files from a case management program running in Parallels Desktop on macOS. The program uses a network path like \\192.168.1.1\Ws... to access files. When I try to open a PDF from the program, Adobe launches on the macOS side but doesn't load the specific file. However, if I open the same PDF directly from the Parallels Desktop environment (e.g., the Windows desktop), it opens normally in Adobe on macOS. Parallels Tools are installed, and file sharing seems to work otherwise. Has anyone else faced this issue with network paths and Adobe in Parallels? Any ideas on what might be causing this or how to fix it?

 

[BrianM9]

I am having a very similar issue since Monday after I updated my macos to 26.4. If i open a file (PDF or xlsx) that is stored in folder on the windows vm, it will open the associated application on the macos, but it will not open the file.

 

[drmorley]

I'm having the exact same issue after upgrading to Tahoe 26.4.

I have a Mac Studio running Tahoe 26.4. Last night it updated, and since the update, I can no longer open PDFs in Windows. I use Parallels and have a Windows 11 virtual machine running for work. I have it set so the default app to open PDFs is Acrobat on my Mac. I can open PDFs in other folders, but when I try to open them, Acrobat opens; however, the file doesn't load and only takes me to the Acrobat home page.

I have a MacBook Pro for work running the exact same setup, and I'm experiencing the EXACT same issue. That MacBook updated to Tahoe 26.4 and will no longer open PDF files when double-clicked within my Parallels Windows 11 VM.

 

[bimmerfive]

Hey - i opened a ticket with support and was escalated, and it was escalated...issue seems to be related with latest MacOS 26.4 update. Hoping they will release a patch update soon for parallel desktop.