How to always allow specific local protocol

%3CLINGO-SUB%20id%3D%22lingo-sub-825421%22%20slang%3D%22en-US%22%3EHow%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-825421%22%20slang%3D%22en-US%22%3E%3CP%3EI%20often%20use%20Edge%20Chromium%20to%20open%20urls%20that%20rely%20on%20local%20protocols%20like%3A%3C%2FP%3E%3CPRE%3Ezotero%3A%2F%2Fselect%2Fitems%2F1_EDK2F%0Avscode%3A%2F%2Ffile%2FC%3A%2FUsers%2Fuser%2FDesktop%2Fscript.py%3A52%3A1%3C%2FPRE%3E%3CP%3EBut%20each%20time%20I%20want%20to%20open%20these%20urls%2C%20Edge%20always%20asks%20me%20if%20I%20want%20to%20open%20Zotero%20or%20VsCode.%20I%20didn't%20have%20this%20confirmation%20popup%20when%20I%20used%20Chrome.%20Is%20there%20a%20way%20to%20always%20allow%20specific%20local%20protocols%20so%20I%20won't%20get%20this%20popup%3F%3C%2FP%3E%3CP%3EEdge%20version%3A%20Version%2078.0.249.1%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-825594%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-825594%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F388976%22%20target%3D%22_blank%22%3E%4007_19%3C%2FA%3E%26nbsp%3Bthanks%20for%20submitting%20this%20report.%20I%20see%20the%20prompt%20in%20Chrome%2C%20but%20there%20is%20a%20checkbox%20there%20that%20says%20%22Always%20open%20these%20types%20of%20links%20in%20the%20associated%20app%22.%20I%20am%20betting%20you%20checked%20that%20box%20at%20some%20time%20in%20the%20past%20and%20have%20forgotten.%20What%20I%20find%20interesting%20is%20that%20Edge%20is%20not%20presenting%20that%20option.%20I'm%20going%20to%20follow%20up%20on%20why%20we%20removed%20the%20checkbox.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-John%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826373%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826373%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318459%22%20target%3D%22_blank%22%3E%40johnjansen%3C%2FA%3E%26nbsp%3B%20Yes%20I%20probably%20have%20forgotten%20that%20I%20checked%20this%20box%20at%20some%20point.%20Thanks%20for%20following%20up%20on%20this!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-826823%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-826823%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F388976%22%20target%3D%22_blank%22%3E%4007_19%3C%2FA%3E%26nbsp%3BIt%20turns%20out%20that%20that%20setting%20is%20now%20removed%20from%20Chrome%20(Canary)%20as%20well.%20It's%20being%20removed%20so%20that%20you%20always%20have%20to%20approve%20using%20a%20protocol%20because%20with%20the%20old%20design%20there%20was%20no%20way%20for%20you%20to%20know%20you'd%20checked%20that%20box%2C%20which%20is%20a%20bit%20of%20a%20security%20concern.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20again%20for%20reporting%20this%20one.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-John%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-827133%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-827133%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318459%22%20target%3D%22_blank%22%3E%40johnjansen%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20checking%2C%20but%20if%20it's%20the%20case%2C%20why%20not%20having%20a%20setting%20in%20the%20%22Site%20permissions%22%20section%20so%20we%20can%20always%20allow%20specific%20local%20protocol.%20That%20way%2C%20there%20is%20no%20security%20issue%20(we%20can%20always%20go%20to%20site%20permissions%20to%20remove%20the%20protocol%20permission)%20and%20you%20keep%20the%20users%20happy!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-827154%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-827154%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F388976%22%20target%3D%22_blank%22%3E%4007_19%3C%2FA%3E%26nbsp%3Byeah%2C%20I%20already%20sent%20mail%20internally%20to%20brainstorm%20the%20best%20way%20to%20move%20forward%20with%20this.%20I%20don't%20really%20like%20the%20idea%20of%20being%20prompted%20with%20every%20protocol%20link%20if%20I%20trust%20the%20domain%20serving%20the%20link%2C%20but%20I%20always%20defer%20to%20our%20security%20experts.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-827177%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-827177%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318459%22%20target%3D%22_blank%22%3E%40johnjansen%3C%2FA%3E%26nbsp%3BYou're%20just%20amazing%2C%20thanks%20a%20lot%20for%20your%20time%20and%20your%20dedication!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1024954%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1024954%22%20slang%3D%22en-US%22%3EIs%20there%20an%20update%20on%20this%3F%20This%20is%20very%20disruptive%20in%20our%20enterprise%20environment%20during%20our%20testing.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1070845%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1070845%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F436815%22%20target%3D%22_blank%22%3E%40jagrock%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20looks%20like%20there%20is%20now%20a%20policy%20to%20enable%20the%20checkbox%20again%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%23externalprotocoldialogshowalwaysopencheckbox%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%23externalprotocoldialogshowalwaysopencheckbox%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071046%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071046%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E%26nbsp%3B-%20thanks!%26nbsp%3B%20This%20worked.%26nbsp%3B%20Now%20to%20figure%20out%20where%20it's%20storing%20this%20so%20I%20can%20set%20our%20apps%20(WebEx%2C%20Teams%2C%20etc)%20to%20do%20this%20automatically%20for%20our%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071063%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071063%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F436815%22%20target%3D%22_blank%22%3E%40jagrock%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20handler%20preference%20is%20stored%20in%20%25localappdata%25%5CMicrosoft%5CEdge%5Bversion%5D%5CUser%20Data%5CDefault%20%5Bor%20profile%20name%5D%5CPreferences.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20two%20ways%20to%20prepopulate%20it%20I%20know%20of%20are%3A%3C%2FP%3E%3CUL%3E%3CLI%3EAdd%20a%20master_preferences%20file%20to%20the%20installation%20directory%20of%20Edge%20for%20it%20to%20load%20on%20first%20run%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.google.com%2Fchrome%2Fa%2Fanswer%2F187948%3Fhl%3Den%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.google.com%2Fchrome%2Fa%2Fanswer%2F187948%3Fhl%3Den%3C%2FA%3E%3C%2FLI%3E%3CLI%3EUse%20PowerShell%20to%20add%20this%20to%20the%20end%20of%20the%20preferences%20file%20before%20the%20last%20curly%20brace%3CBR%20%2F%3E%2C%22protocol_handler%22%3A%7B%22excluded_schemes%22%3A%7B%22yourhandlername%22%3Afalse%7D%7D%3C%2FLI%3E%3C%2FUL%3E%3CP%3EUnfortunately%2C%20this%20preference%20is%20undone%20whenever%20the%20user%20clears%20their%20browser%20cache%2C%20so%20I%20think%20I'm%20going%20to%20opt%20to%20just%20have%20folks%20check%20the%20box.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1073360%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1073360%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20a%20lot%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F458117%22%20target%3D%22_blank%22%3E%40AndrewSAIF%3C%2FA%3E.%20I%20didn't%20have%20to%20use%20a%26nbsp%3Bmaster_preferences%20or%20powershell%20to%20edit%26nbsp%3B%3CSPAN%3EPreferences.%20I%20simply%20right-click%20it%20and%20choose%20to%20open%20it%20with%20my%20text%20editor%20%22vscode%22%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EOnce%20open%2C%20Preferences%20looks%20like%20a%20json%20file%2C%20so%20you%20should%20be%20able%20to%20open%20it%20with%20any%20text%20editor.%20But%20your%20operating%20system%20doesn't%20know%20that%20because%20the%20extension%20is%20removed.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20work%20for%20me%20(to%20allow%20zotero%20and%20vscode%20protocols)%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20close%20Edge%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20go%20to%20%25localappdata%25%5CMicrosoft%5CEdge%5Bversion%5D%5CUser%20Data%5CDefault%20%5Bor%20profile%20name%5D%5CPreferences.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20Right-click%20Preference%20and%20choose%20a%20text%20editor%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20scroll%20down%20to%20the%20very%20end%20of%20the%20text%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20remove%20the%20last%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20add%26nbsp%3B%20(notice%20the%20first%20comma%2C%20and%20no%20need%20to%20add%20%3A%2F%2F%20for%20the%20protocols%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-javascript%22%3E%3CCODE%3E%2C%22protocol_handler%22%3A%7B%22excluded_schemes%22%3A%7B%22zotero%22%3Afalse%2C%20%22vscode%22%3Afalse%7D%7D%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Eedit%3A%20once%20you%20edit%20have%20edited%20Preferences%20and%20open%20Edge%2C%20the%20position%20of%20the%20protocol_handler%20will%20automatically%20be%20move%20just%20beneath%20%22password_hash_data_list%22%20so%20you%20won't%20see%20it%20anymore%20right%20a%20the%20very%20end%20of%20the%20text.%20So%20after%20the%20first%20edit%2C%20if%20you%20need%20to%20add%20more%20protocols%2C%20you%20will%20have%20to%20look%20for%20%22protocol_handler%22.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1074351%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1074351%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F388976%22%20target%3D%22_blank%22%3E%4007_19%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou're%20correct%2C%20you%20can%20manually%20edit%20the%20file%20with%20a%20text%20editor%20and%20achieve%20the%20same%20result.%20It%20looked%20like%20jagrock%20was%20trying%20to%20configure%20this%20on%20multiple%20machines%20at%20once%20though%2C%20which%20is%20why%20I%20suggested%20those%20methods.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1077201%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1077201%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F388976%22%20target%3D%22_blank%22%3E%4007_19%3C%2FA%3E%26nbsp%3BYes%2C%20I%20had%20tried%20this%20prior%20to%20posting%20here%20and%20it%20didn't%20work.%26nbsp%3B%20Maybe%20it%20will%20now%20since%20the%20popup%20was%20added%20in.%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20this%20persistent%20or%20does%20the%20end%20user%20clearing%20cache%2Fcookies%2C%20resetting%20settings%2C%20etc%20clear%20it%20out%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1219109%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20always%20allow%20specific%20local%20protocol%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1219109%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20the%20new%20update%20(I%20have%26nbsp%3B%20Version%2082.0.439.1%20(Official%20build)%20dev%20(64-bit)%20)%2C%20this%20solution%20doesn't%20work%20anymore.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20checked%20my%20Preferences%20file%20in%20AppData%5CLocal%5CMicrosoft%5CEdge%20Dev%5CUser%20Data%5CDefault%20and%20the%20exclusion%20rule%20is%20still%20there%20(%22protocol_handler%22%3A%7B%22excluded_schemes%22%3A%7B%22vscode%22%3Afalse%2C%22zotero%22%3Afalse%7D%7D%20)%20%2C%20but%20each%20time%20I%20open%20one%20of%20the%20specified%20protocol%2C%20I%20am%20asked%20to%20confirm%20that%20I%20want%20to%20open%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20to%20fix%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

I often use Edge Chromium to open urls that rely on local protocols like:

zotero://select/items/1_EDK2F
vscode://file/C:/Users/user/Desktop/script.py:52:1

But each time I want to open these urls, Edge always asks me if I want to open Zotero or VsCode. I didn't have this confirmation popup when I used Chrome. Is there a way to always allow specific local protocols so I won't get this popup?

Edge version: Version 78.0.249.1

14 Replies
Highlighted

@07_19 thanks for submitting this report. I see the prompt in Chrome, but there is a checkbox there that says "Always open these types of links in the associated app". I am betting you checked that box at some time in the past and have forgotten. What I find interesting is that Edge is not presenting that option. I'm going to follow up on why we removed the checkbox. 

 

-John 

Highlighted

@johnjansen  Yes I probably have forgotten that I checked this box at some point. Thanks for following up on this!

Highlighted

@07_19 It turns out that that setting is now removed from Chrome (Canary) as well. It's being removed so that you always have to approve using a protocol because with the old design there was no way for you to know you'd checked that box, which is a bit of a security concern.

 

Thanks again for reporting this one. 

 

-John

Highlighted

@johnjansen  Thanks for checking, but if it's the case, why not having a setting in the "Site permissions" section so we can always allow specific local protocol. That way, there is no security issue (we can always go to site permissions to remove the protocol permission) and you keep the users happy!

Highlighted

@07_19 yeah, I already sent mail internally to brainstorm the best way to move forward with this. I don't really like the idea of being prompted with every protocol link if I trust the domain serving the link, but I always defer to our security experts.

Highlighted

@johnjansen You're just amazing, thanks a lot for your time and your dedication!

Highlighted
Is there an update on this? This is very disruptive in our enterprise environment during our testing.
Highlighted
Highlighted

@AndrewSAIF - thanks!  This worked.  Now to figure out where it's storing this so I can set our apps (WebEx, Teams, etc) to do this automatically for our users.

Highlighted

@jagrock 

 

The handler preference is stored in %localappdata%\Microsoft\Edge[version]\User Data\Default [or profile name]\Preferences.


The two ways to prepopulate it I know of are:

  • Add a master_preferences file to the installation directory of Edge for it to load on first run
    https://support.google.com/chrome/a/answer/187948?hl=en
  • Use PowerShell to add this to the end of the preferences file before the last curly brace
    ,"protocol_handler":{"excluded_schemes":{"yourhandlername":false}}

Unfortunately, this preference is undone whenever the user clears their browser cache, so I think I'm going to opt to just have folks check the box. 

Highlighted

Thanks a lot @AndrewSAIF. I didn't have to use a master_preferences or powershell to edit Preferences. I simply right-click it and choose to open it with my text editor "vscode" 

 

Once open, Preferences looks like a json file, so you should be able to open it with any text editor. But your operating system doesn't know that because the extension is removed.

 

This work for me (to allow zotero and vscode protocols):

- close Edge

- go to %localappdata%\Microsoft\Edge[version]\User Data\Default [or profile name]\Preferences.

- Right-click Preference and choose a text editor

- scroll down to the very end of the text 

- remove the last

 

}

 

- add  (notice the first comma, and no need to add :// for the protocols

 

,"protocol_handler":{"excluded_schemes":{"zotero":false, "vscode":false}}}

 

 

edit: once you edit have edited Preferences and open Edge, the position of the protocol_handler will automatically be move just beneath "password_hash_data_list" so you won't see it anymore right a the very end of the text. So after the first edit, if you need to add more protocols, you will have to look for "protocol_handler". 

 

Highlighted

@07_19 

 

You're correct, you can manually edit the file with a text editor and achieve the same result. It looked like jagrock was trying to configure this on multiple machines at once though, which is why I suggested those methods.

Highlighted

@07_19 Yes, I had tried this prior to posting here and it didn't work.  Maybe it will now since the popup was added in.

Is this persistent or does the end user clearing cache/cookies, resetting settings, etc clear it out?

Highlighted

Since the new update (I have  Version 82.0.439.1 (Official build) dev (64-bit) ), this solution doesn't work anymore.

 

I checked my Preferences file in AppData\Local\Microsoft\Edge Dev\User Data\Default and the exclusion rule is still there ("protocol_handler":{"excluded_schemes":{"vscode":false,"zotero":false}} ) , but each time I open one of the specified protocol, I am asked to confirm that I want to open it.

 

How to fix this?