Windows 10 not opening document types when browsing shared directory using "File://" protocol
I'm hoping that someone on here can please explain what might be preventing this from working.
We've moved to Windows 10 Pro x64. On our Intranet we have an iFrame with the 'src' set to "file://SERVER-NAME/SHARED
This directory is shared in a central location and the user 'Everyone' has Read Only access to it. It works fine on Windows 7 Pro x64.
We can now no longer open PDF or Excel documents from this page. Word documents open fine, and we can still traverse through directories. Behaviour differs between browsers:
In Microsoft Edge, instead of being embedded in the iframe the directory gets opened in Windows Explorer, allows traversal, and all files open normally (since it's just opening from Explorer). I have only tested this browser on Windows 10.
In Google Chrome nothing happens on either Windows 7 or 10. I have researched into this and it's intentional (source https://community.spicewor
In Internet Explorer 11 (latest version) on both Windows 7 & 10 you can traverse the directories. Files such as .docx open fine in Microsoft Word.
When I try to open a file in Microsoft Excel, the program Excel opens but it's blank and doesn't load the document. Subsequent attempts to open simply create new Excel instances.
Attempting to open PDF files does nothing. Occasionally the mouse cursor will display a loading wheel for a couple of seconds but nothing more. Right-clicking on the PDF and choosing to Open with Word does open correctly, converting the PDF document within Word as is usual.
I suspect that there is something about Windows 10 which is 'more secure' and has caused this behavioural change. Has anyone else come across this, and if so what did you do to resolve it?
I have already poked at a number of settings (such as ensuring Protected Mode is disabled in Internet Explorer) to no avail.
Thanks,
David
We've moved to Windows 10 Pro x64. On our Intranet we have an iFrame with the 'src' set to "file://SERVER-NAME/SHARED
This directory is shared in a central location and the user 'Everyone' has Read Only access to it. It works fine on Windows 7 Pro x64.
We can now no longer open PDF or Excel documents from this page. Word documents open fine, and we can still traverse through directories. Behaviour differs between browsers:
In Microsoft Edge, instead of being embedded in the iframe the directory gets opened in Windows Explorer, allows traversal, and all files open normally (since it's just opening from Explorer). I have only tested this browser on Windows 10.
In Google Chrome nothing happens on either Windows 7 or 10. I have researched into this and it's intentional (source https://community.spicewor
In Internet Explorer 11 (latest version) on both Windows 7 & 10 you can traverse the directories. Files such as .docx open fine in Microsoft Word.
When I try to open a file in Microsoft Excel, the program Excel opens but it's blank and doesn't load the document. Subsequent attempts to open simply create new Excel instances.
Attempting to open PDF files does nothing. Occasionally the mouse cursor will display a loading wheel for a couple of seconds but nothing more. Right-clicking on the PDF and choosing to Open with Word does open correctly, converting the PDF document within Word as is usual.
I suspect that there is something about Windows 10 which is 'more secure' and has caused this behavioural change. Has anyone else come across this, and if so what did you do to resolve it?
I have already poked at a number of settings (such as ensuring Protected Mode is disabled in Internet Explorer) to no avail.
Thanks,
David
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER