File:// Links not working on Chrome or Edge (Chromium)

%3CLINGO-SUB%20id%3D%22lingo-sub-1288891%22%20slang%3D%22en-US%22%3EFile%3A%2F%2F%20Links%20not%20working%20on%20Chrome%20or%20Edge%20(Chromium)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1288891%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20recently%20encountered%20an%20issue%20with%20IE11%2C%20and%20are%20trying%20to%20move%20to%20a%20different%20browser%20solution%20on%20company%20Workstations.%20Our%20intranet%20is%20Sharepoing%202013%20(On-Prem)%2C%20and%20we%20have%20a%20large%20number%20of%20documents%20linked%20in%20%22file%3A%2F%2F%22%20format.%20I%20would%20like%20to%20avoid%20replacing%20every%20single%20document%20on%20our%20intranet%20with%20a%20different%20link%20format%3B%20does%20anyone%20know%20of%20a%20way%20for%20Chromium%20based%20browsers%20to%20open%20%22file%3A%2F%2F%22%20based%20links%26nbsp%3B%3CSTRONG%3Ein%20file%20explorer%3C%2FSTRONG%3E.%20I%20am%20aware%20of%20the%20%22file%3A%2F%2F%22%26nbsp%3Bchrome%20extension%20that%20opens%20them%20in%20an%20index%20search%2C%20but%20we%20want%20the%20links%20to%20open%20in%20file%20explorer.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20time!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E~JP%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1288891%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1289031%22%20slang%3D%22en-US%22%3ERe%3A%20File%3A%2F%2F%20Links%20not%20working%20on%20Chrome%20or%20Edge%20(Chromium)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1289031%22%20slang%3D%22en-US%22%3E%22By%20design!%22%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20is%20a%20security%20feature%20to%20prevent%20navigating%20across%20security%20boundaries.%20You%20can%20take%20a%20look%20at%20%3CA%20href%3D%22https%3A%2F%2Fchrome.google.com%2Fwebstore%2Fdetail%2Flocal-explorer-file-manag%2Feokekhgpaakbkfkmjjcbffibkencdfkl%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fchrome.google.com%2Fwebstore%2Fdetail%2Flocal-explorer-file-manag%2Feokekhgpaakbkfkmjjcbffibkencdfkl%3C%2FA%3E%20to%20see%20if%20that%20would%20work.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1289059%22%20slang%3D%22en-US%22%3ERe%3A%20File%3A%2F%2F%20Links%20not%20working%20on%20Chrome%20or%20Edge%20(Chromium)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1289059%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F130%22%20target%3D%22_blank%22%3E%40Trevor%20Seward%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EHi%20Trevor%2C%20thanks%20for%20the%20response.%20We%20are%20aware%20that%20this%20is%20a%20security%20feature%20by%20design%2C%20but%20even%20in%20Microsoft%20Edge%20(Chromium)%2C%20this%20invalidates%20a%20good%2070%25%20of%20the%20documents%20stored%20on%20our%20SharePoint.%20I%20don't%20see%20why%20this%20can't%20be%20disabled%20for%20local%20intranet%20files.%20I%20am%20looking%20into%20that%20extension%2C%20and%20associated%20integration%20module%2C%20and%20it%20looks%20promising.%20I'll%20have%20to%20vet%20the%20program%20itself%2C%20but%20thank%20you%20for%20pointing%20this%20out%20to%20me!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1724505%22%20slang%3D%22de-DE%22%3ERe%3A%20File%3A%2F%2F%20links%20not%20working%20on%20Chrome%20or%20Edge%20(Chromium)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1724505%22%20slang%3D%22de-DE%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F612944%22%20target%3D%22_blank%22%3E%40AENT_SysAdmin%3C%2FA%3E%20%3CBR%20%2F%3E%20Hello%20we%20have%20the%20same%20problem.%26nbsp%3B%20We%20have%20a%20large%20SQL%20database%20with%20programmed%20frontend%20for%20a%20link%20collection%20behind%20which%20documents%20lie%20on%20company%20servers.%20So%20everything%20internally%20on%20your%20own%20servers.%20If%20this%20continues%20to%20be%20blocked%2C%20it%20kills%20hundreds%20of%20links%20and%20basic%20functionality%20of%20the%20tool.%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20found%20a%20solution%20to%20the%20problem%3F%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We've recently encountered an issue with IE11, and are trying to move to a different browser solution on company Workstations. Our intranet is Sharepoing 2013 (On-Prem), and we have a large number of documents linked in "file://" format. I would like to avoid replacing every single document on our intranet with a different link format; does anyone know of a way for Chromium based browsers to open "file://" based links in file explorer. I am aware of the "file://" chrome extension that opens them in an index search, but we want the links to open in file explorer. 

 

Thanks for your time!

 

~JP

3 Replies
Highlighted
"By design!"

This is a security feature to prevent navigating across security boundaries. You can take a look at https://chrome.google.com/webstore/detail/local-explorer-file-manag/eokekhgpaakbkfkmjjcbffibkencdfkl to see if that would work.
Highlighted

@Trevor Seward 

Hi Trevor, thanks for the response. We are aware that this is a security feature by design, but even in Microsoft Edge (Chromium), this invalidates a good 70% of the documents stored on our SharePoint. I don't see why this can't be disabled for local intranet files. I am looking into that extension, and associated integration module, and it looks promising. I'll have to vet the program itself, but thank you for pointing this out to me!

Highlighted

@AENT_SysAdmin 
Hallo wir haben das gleiche Problem. Wir haben eine große SQL Datenbank mit programmiertem Frontend für eine Link Sammlung hinter denen Dokumente auf Firmenservern liegen. Also alles intern auf eigenen Servern. Sollte das weiterhin geblockt werden, killt das hunderte Links und eine Basisfunktionalität des Tools. 

Haben Sie eine Lösung für das Problem gefunden?

Beste Grüße