SOLVED

Default PDF viewer / System Viewer

Copper Contributor
Version 90.0.818.56 (Official build) (64-bit)
 
The way Edge Chromium handles downloaded .pdf files has bugged me ever since it was released and is still not working properly.
 
My System Viewer (default Windows application for .pdf files) is set to Foxit PhantomPDF as you can see here:
Picture1.jpgPicture2.jpg
 
When I download a .pdf file in Edge you can also see the Foxit icon next to the file:
Picture3.jpg
 
However, when I click "Open file" it opens as a new Tab in Edge and NOT in Foxit Phantom:
Picture4.jpg
 
This happens regardless of how the option "Always open with system viewer" is set, i.e. both when it is OFF and ON:
Picture5.jpg
 
In older versions (up to 89.0.774.75 (Official build) (64-bit)) it was possible to right click and then choose “Open with System Viewer” manually. Not ideal but a workaround nonetheless:
Picture6.jpg

 

With the latest version the only option is to click on “Show in folder” and then open the default .pdf via Windows Explorer:

Picture7.jpg

4 Replies
best response confirmed by Pellique (Copper Contributor)
Solution
Reply to self.
I just got Version 90.0.818.62 (Official build) (64-bit) and this has finally been fixed.
Hi @Pellique ,

"I just got Version 90.0.818.62 (Official build) (64-bit) and this has finally been fixed." so your problem is solved? xD

If so you can mark your answer as solved ;D

Best regards,
Schnittlauch

"First, No system is safe. Second, Aim for the impossible. Third no Backup, no Mercy" - Schnittlauch

My answer helped you? Don't forget to leave a like. Also mark the answer as solved when your problem is solved. :)
I can't find a way to mark as solved.
You should be able to see a "mark as best answer" button under each comment :)

https://techcommunity.microsoft.com/t5/tech-community-blog/a-guide-to-using-the-best-response-featur...
1 best response

Accepted Solutions
best response confirmed by Pellique (Copper Contributor)
Solution
Reply to self.
I just got Version 90.0.818.62 (Official build) (64-bit) and this has finally been fixed.

View solution in original post