Windows 10: Unable to open PDF from file share in Microsoft Edge

Windows-10-Banner

I’ve been working on a Windows 10 1511 defect where the devices are unable to open some PDF files from a fully qualified domain name (FQDN) mapped drive such as a DFS using Microsoft Edge browser.

Users receive this message in Edge when they try to launch a PDF from a FQDN mapped drive:

Hmm, we can’t reach this page.
Try this
Make sure that you’ve got the right web address. . .

Hmm we cant reach this page error

I’m showing how to create the issue with a workaround I found. I’m going to link this post to this issue on Edges Developer site. Please click there and vote if you have seen the same issue.

There are a number of workarounds for this such as:

  • Copy the PDF file locally and launch it.
  • Map a drive using single label resolution (example: \\server\share).
  • Connect to the share directly using UNC with single label resolution (example: \\server\share).

How to replicate the issue in a lab

In order to emulate the issue I had in the enterprise, I modified to local hosts file (C:\Windows\System32\drivers\etc\hosts) in my home network to make my home NAS act similar to a DFS namespace using a FQDN source.

Open Host file

I added a new line to the hosts file which had the local IP address of my NAS and a made up FQDN for testing. In this case it was nas.scriptimus.local.

 

Edit Host file

I then mapped a drive to the NAS share where I already had a number of PDF ebooks.

Try to open a PDF

When I tried to access any of these files I received a prompt similar to this.

Hmm we cant reach this page error

So what’s the issue?

Well this shouldn’t happen. For one thing, Edge will open the same files using other methods. For example:

  • If I copy the files locally the files open in Edge.
  • If I map a drive using just the hostname the files open in Edge.
  • If I UNC to the share the files open in Edge.

This is the same issue countless people are experiencing in the enterprise. The issue was closed on Microsoft Connect as they were unable to reproduce the issue.

To ‘fix’ this issue

Simply add the DNS name or suffix to the Local Intranet sites in Internet Explorer 11.Add IE 11 Zone

After this you can open your PDF files in Edge without issue.

 

Opens fine now

I use the term ‘fix’ loosely because you really should not need to do this but as a work around it works for me. If anyone has a better fix then please feel free to comment below.

Advertisements

About Andrew Barnes

A Scripting and Deployment Specialist.
This entry was posted in Windows 10 and tagged , . Bookmark the permalink.

3 Responses to Windows 10: Unable to open PDF from file share in Microsoft Edge

  1. Jon Anderson says:

    Have you looked at this in WireShark while opening the file? You commented on the bug I sumbitted to Microsoft.

    In my case, we only had issue with PDFs that came from a particular vendor. That vendor, for whatever reason, had about 73KB of NULL characters after the EOF character.

    When I viewed the attempt to open the file in WireShark, I noticed that SMB was repeatedly requesting data from the same offset, on the order of 11,000 requests. Compared to a normal file that which only took about 150. The data at the offset happened to be in the NULL space.

    Like

    • Thanks Jon,

      I couldn’t figure out why some files would work in my scenario above. I plan to test for this zero byte issue and see if your files match my issue. I think it’s all connected somehow but just need to connect the dots. It’s my hope for now that Microsoft stop closing this issue due to not being able to reproduce it.

      Like

      • Jon Anderson says:

        I was surprised that I didn’t find a bug submission for it when I noticed the issue. In my case, I could also open the offending PDF in HxD (or any other hex editor) and easily find the thousands of “00” characters.

        I’m interested to hear what you find about the different files.

        Nice site.

        Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s