Home

Dev channel update to 81.0.389.2 is live

%3CLINGO-SUB%20id%3D%22lingo-sub-1110845%22%20slang%3D%22en-US%22%3EDev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1110845%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Insiders%2C%20today%20we%E2%80%99re%20releasing%20build%2081.0.389.2%20to%20the%20Dev%20Channel.%26nbsp%3B%20It%E2%80%99s%20a%20smaller%20update%20this%20week%20since%20we%E2%80%99re%20focusing%20on%20our%20other%20channels%2C%20including%20our%20very%20first%20Stable%20channel%20update%3A%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fmsedgedev%2F2020%2F01%2F15%2Fupgrading-new-microsoft-edge-79-chromium%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.windows.com%2Fmsedgedev%2F2020%2F01%2F15%2Fupgrading-new-microsoft-edge-79-chromium%2F%3C%2FA%3E!%20%26nbsp%3BAs%20part%20of%20that%2C%20we%20also%20announced%20a%20fun%20opportunity%20coming%20up%20later%20today%20to%20talk%20directly%20to%20some%20members%20of%20our%20development%20team.%26nbsp%3B%20For%20details%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fupdated-a-chance-to-talk-directly-with-microsoft-engineers-about%2Fm-p%2F1099775%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fupdated-a-chance-to-talk-directly-with-microsoft-engineers-about%2Fm-p%2F1099775%3C%2FA%3E.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAdditionally%2C%20we%E2%80%99ve%20started%20a%20discussion%20about%20the%20future%20of%20the%20Fluent%20Design%20Language%20and%20how%20it%E2%80%99s%20utilized%20in%20Edge%3A%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fdiscussion-updating-our-interface-with-fluent-touches%2Fm-p%2F1105938%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fdiscussion-updating-our-interface-with-fluent-touches%2Fm-p%2F1105938%3C%2FA%3E.%20%26nbsp%3BAs%20for%20the%20most%20noteworthy%20features%20and%20fixes%20this%20week%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAdded%20features%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAdded%20the%20ability%20to%20hide%20the%20Collections%20button%20from%20the%20address%20bar.%3C%2FLI%3E%0A%3CLI%3EAdded%20a%20%E2%80%9Ccoming%20soon%E2%80%9D%20message%20to%20all%20users%20who%20still%20have%20favorites%20sync%20disabled.%3C%2FLI%3E%0A%3CLI%3EAdded%20a%20dialog%20to%20inform%20users%20when%20another%20program%20on%20the%20device%20installs%20an%20extension%20in%20Edge.%3C%2FLI%3E%0A%3CLI%3EEnabled%20integration%20of%20the%20Windows%20built-in%20spellchecker.%3C%2FLI%3E%0A%3CLI%3EAdded%20a%20management%20policy%20to%20prevent%20the%20first%20run%20experience%20from%20running.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EImproved%20reliability%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ERe-enabled%20favorites%20sync%20for%20some%20users%20who%20hadn%E2%80%99t%20gotten%20it%20re-enabled%20last%20week.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20sorting%20favorites%20and%20then%20hitting%20undo%20sometimes%20causes%20the%20favorites%20to%20be%20deleted.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20on%20Mac%20where%20the%20send%20feedback%20button%20sometimes%20crashes%20the%20browser.%3C%2FLI%3E%0A%3CLI%3EFixed%20a%20crash%20when%20using%20accessibility%20software%20like%20screen%20readers.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20closing%20an%20IE%20mode%20tab%20sometimes%20crashes%20the%20browser.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20attempting%20to%20customize%20sync%20settings%20during%20the%20First%20Run%20Experience%20crashes%20the%20tab.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20watching%20DRM-protected%20video%20like%20on%20Netflix%20doesn%E2%80%99t%20play%20at%20the%20highest%20possible%20quality%20on%20certain%20devices%20with%20Nvidia%20graphics.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EChanged%20behavior%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EImproved%20Read%20Aloud%20performance.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20exporting%20a%20Collection%20to%20Excel%20results%20in%20the%20column%20headers%20being%20messed%20up.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20cancelling%20an%20edit%20on%20a%20Collections%20item%20doesn%E2%80%99t%20undo%20the%20changes%20to%20it.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20sites%20that%20are%20deleted%20from%20the%20Top%20Sites%20tiles%20on%20the%20New%20Tab%20Page%20sometimes%20return.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20the%20Share%20UI%20doesn%E2%80%99t%20appear%20when%20the%20Share%20button%20is%20clicked.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20the%20link%20in%20Settings%20to%20manage%20a%20browser%20profile%E2%80%99s%20associated%20account%20sometimes%20doesn%E2%80%99t%20work.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20linked%20clicked%20from%20other%20applications%20sometimes%20don%E2%80%99t%20open%20if%20Edge%20is%20already%20running%20and%20was%20launched%20with%20administrator%20privileges.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20Tracking%20Prevention%20sometimes%20causes%20content%20blocked%20notifications%20to%20the%20right%20of%20the%20address%20bar%20(cookies%2C%20for%20example)%20not%20to%20appear%20properly.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20the%20ink%20customization%20options%20when%20annotating%20feedback%20screenshots%20don%E2%80%99t%20work.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20the%20Grammar%20Tools%20color%20picker%20isn%E2%80%99t%20visible.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20the%20Cisco%20Webex%20extension%20doesn%E2%80%99t%20work%20properly.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20manually%20navigating%20to%20an%20extension%E2%80%99s%20page%20by%20typing%20their%20address%20into%20the%20address%20bar%20doesn%E2%80%99t%20work.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20editing%20settings%20from%20within%20an%20Application%20Guard%20window%20that%20causes%20the%20window%20to%20have%20to%20close%20and%20re-open%20leads%20to%20the%20window%20closing%2C%20but%20never%20re-opening.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKnown%20issues%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAfter%20an%20initial%20fix%20for%20it%20recently%2C%20some%20users%20are%20still%20experiencing%20Edge%20windows%20becoming%20all%20black.%20UI%20popups%20like%20menus%20are%20not%20affected%20and%20opening%20the%20Browser%20Task%20Manager%20(keyboard%20shortcut%20is%20shift%20%2B%20esc)%20and%20killing%20the%20GPU%20process%20fixes%20it.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3ESome%20users%20are%20still%20not%20seeing%20Collections%20being%20enabled%20by%20default%20on%20Canary%20and%20Dev.%20For%20users%20who%20want%20to%20try%20Collections%2C%20enabling%20the%20flag%20at%20edge%3A%2F%2Fflags%2F%23edge-collections%20should%20still%20work%20to%20turn%20on%20the%20feature.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EThere%20are%20some%20issues%20where%20users%20with%20multiple%20audio%20output%20devices%20sometimes%20don%E2%80%99t%20get%20any%20sound%20from%20Edge.%20In%20one%20case%2C%20Edge%20becomes%20muted%20in%20the%20Windows%20Volume%20Mixer%20and%20unmuting%20it%20fixes%20it.%26nbsp%3B%20In%20another%2C%20restarting%20the%20browser%20fixes%20it.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EAt%20certain%20zoom%20levels%2C%20there%20is%20a%20noticeable%20line%20between%20the%20browser%20UI%20and%20the%20web%20contents.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20those%20using%20the%20Beta%20channel%2C%20we're%20also%20releasing%20the%20first%20update%20to%20major%20version%2080%20to%20it%20this%20week.%26nbsp%3B%20Thank%20you%20for%20all%20your%20feedback%20and%20bug%20finds%20that%20got%20us%20there!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1111288%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1111288%22%20slang%3D%22en-US%22%3ENice%2C%20has%20the%20problem%20with%20forcepoint%20causing%20Access%20Violation%20error%20been%20solved%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1111823%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1111823%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3BThis%20update%20has%20a%20bug%20in%20the%20dark%20theme%20that%20caused%20the%20omnibox%20-%20along%20with%20the%20suggestion%20box%2C%20to%20be%20locked%20at%20light%20theme%2C%20regardless%20of%20the%20preferences.%20I%20really%20hope%20this%20will%20be%20fixed%20in%20the%20next%20Dev%20build.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1111995%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1111995%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3BThis%20and%20the%20previous%20dev%20channel%20builds%20have%20been%20broken%20for%20me.%26nbsp%3B%20When%20opening%20Edge%20the%20application%20area%20is%20all%20white%20with%20no%20UI%20visible.%26nbsp%3B%20After%20a%20while%20the%20UI%20loads%20and%20the%20infamous%20%22This%20page%20is%20having%20a%20problem%22%20appears%20(no%20access%20to%20about%2C%20settings%2C%20or%20feedback).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20expect%20this%20is%20all%20related%20to%20Symantec%20Endpoint%20Protection%2C%20which%20appears%20to%20have%20on-going%20issues%20with%20the%20latest%20Chrome%2081%20builds%2C%20since%20this%20issue%20doesn't%20happen%20on%20machines%20I%20test%20that%20do%20not%20have%20SEP%20installed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWorkaround%20is%20to%20use%20the%20Beta%20channel%20which%20is%20still%20based%20on%20Chrome%2079.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112037%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112037%22%20slang%3D%22en-US%22%3EStable%20is%20also%20using%20Chromium%2079%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3Emicrosoft.com%2Fedge%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112655%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112655%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3BThe%20%22%3CSPAN%3EEnabled%20integration%20of%20the%20Windows%20built-in%20spellchecker%22%20feature%2C%20does%20not%20seem%20to%20be%20fully%20supporting%20Hardware%20Keyboard%20-%20Autocorrect%20misspelt%20words%20as%20I%20type%20feature%20from%20Windows%2010%3F%20Is%20this%20something%20you%20will%20be%20enabling%20in%20the%20future%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAlso%2C%20do%20we%20know%20why%26nbsp%3Boverlay-scrollbars%20flag%20has%20been%20removed%3F%20I%20have%20been%20using%20it%20on%20chrome%20for%20years%20and%20was%20happy%20to%20know%20that%20edge%20was%20supporting%20them%20in%20insider%3B%20the%20native%20Windows%2010%20thick%20scrollbars%20are%20just%20too%20large%20and%20not%20very%20modern%20looking%2C%20occupying%26nbsp%3Bsignificant%20amount%20of%20space%20when%20not%20needed.%20Would%20be%20great%20if%20Edge%20scrollbars%20would%20be%20able%20to%20use%20XAML%20scrollbars%20like%20the%20ones%20used%20by%20the%20UWP%20framework.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20now%20have%20to%20use%20extension%20called%20Minimal%26nbsp%3BScrollbar%20to%20achieve%20similar%20result%2C%20although%20not%20supported%20on%20all%20website%2C%20it%20makes%20the%20scrollbars%20so%20much%20more%20pleasant.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112688%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112688%22%20slang%3D%22en-US%22%3EStill%20missing%20feature%20to%20directly%20%22Open%22%20a%20file%20without%20downloading%20it%20first%20(all%20MS%20browsers%20have%20this%20feature)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112703%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112703%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414787%22%20target%3D%22_blank%22%3E%40Yoneff%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F414787%22%20target%3D%22_blank%22%3E%40Yoneff%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3EStill%20missing%20feature%20to%20directly%20%22Open%22%20a%20file%20without%20downloading%20it%20first%20(all%20MS%20browsers%20have%20this%20feature)%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FDiscussions%2FProvide-run-open-save-save-as-options-when-downloading-files%2Fm-p%2F962775%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FDiscussions%2FProvide-run-open-save-save-as-options-when-downloading-files%2Fm-p%2F962775%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112716%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112716%22%20slang%3D%22en-US%22%3EMaybe%20they%20mean%20this%20flag%20is%20turned%20on%20by%20default%3CBR%20%2F%3E%3CBR%20%2F%3EUse%20Windows%20Spellchecking%3CBR%20%2F%3EUse%20Windows%20spellchecking%20dictionaries%20when%20available%20to%20find%20spelling%20mistakes%20and%20provide%20suggestions.%20%E2%80%93%20Windows%3CBR%20%2F%3E%23win-use-native-spellchecker%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112720%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112720%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Will%20EdgeDev%20continue%20to%20be%20separate%20from%20the%20now-released%20new%20Edge%3F%3C%2FP%3E%3CP%3E2.%20How%20do%20we%20remove%20the%20old%20Edge%20from%20our%20computers%3F%20Uninstall%20is%20grayed%20out.%3C%2FP%3E%3CP%3E3.%20Why%20do%20you%20keep%20opening%20the%20old%20Edge%20after%20updates%20to%20new%20Win%2010%20builds%2C%20even%20though%20EdgeDev%20is%20the%20default%20browser%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112741%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112741%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383421%22%20target%3D%22_blank%22%3E%40JimRome%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22lia-spoiler-container%22%3E%3CA%20class%3D%22lia-spoiler-link%22%20href%3D%22%23%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESpoiler%3C%2FA%3E%3CNOSCRIPT%3E(Highlight%20to%20read)%3C%2FNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-border%22%3E%3CDIV%20class%3D%22lia-spoiler-content%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383421%22%20target%3D%22_blank%22%3E%40JimRome%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E1.%20Will%20EdgeDev%20continue%20to%20be%20separate%20from%20the%20now-released%20new%20Edge%3F%3C%2FP%3E%3CP%3E2.%20How%20do%20we%20remove%20the%20old%20Edge%20from%20our%20computers%3F%20Uninstall%20is%20grayed%20out.%3C%2FP%3E%3CP%3E3.%20Why%20do%20you%20keep%20opening%20the%20old%20Edge%20after%20updates%20to%20new%20Win%2010%20builds%2C%20even%20though%20EdgeDev%20is%20the%20default%20browser%3F%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FDIV%3E%3CNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-noscript-container%22%3E%3CDIV%20class%3D%22lia-spoiler-noscript-content%22%3E%26nbsp%3Bwrote%3A1.%20Will%20EdgeDev%20continue%20to%20be%20separate%20from%20the%20now-released%20new%20Edge%3F2.%20How%20do%20we%20remove%20the%20old%20Edge%20from%20our%20computers%3F%20Uninstall%20is%20grayed%20out.3.%20Why%20do%20you%20keep%20opening%20the%20old%20Edge%20after%20updates%20to%20new%20Win%2010%20builds%2C%20even%20though%20EdgeDev%20is%20the%20default%20browser%3F%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FNOSCRIPT%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E1.%20Yes%2C%20definitely%2C%20100%25.%20just%20like%20Google%20uses%20their%20Beta%2FDev%2FCanary%20channels%20to%20continue%20developing%20Google%20chrome%20further%2C%20Microsoft%20uses%20Beta%2FDev%2FCanary%20channels%20to%20develop%20and%20improve%20Microsoft%20Edge.%3C%2FP%3E%3CP%3Enew%20features%20always%20appear%20in%20Canary%2C%20then%20on%20Dev%2C%20then%20on%20Beta%2C%20and%20finally%20on%20Stable%20channel.%3C%2FP%3E%3CP%3Eso%20yes%20they%20will%20be%20separate%20which%20also%20means%20you%20can%20have%20and%20install%20them%20all%20at%20the%20same%20time%20on%20the%20same%20computer%20without%20any%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20You%20don't.%20it's%20a%20built%20in%20preinstalled%20UWP%20app%20and%20there%20is%20no%20option%20in%20the%20Windows%20settings%20nor%20in%20control%20panel%20to%20remove%2Funinstall%20it.%3C%2FP%3E%3CP%3Ewhen%20you%20install%20stable%20version%20of%20the%20new%20Microsoft%20Edge%2C%20it%20will%20automatically%20replace%20the%20Legacy%20Edge%2C%20although%20you%20can%20make%20a%20minor%20adjustment%20to%20the%20Group%20Policy%20to%20allow%20them%20to%20run%20side%20by%20side.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3.%20Go%20to%20Windows%20settings%20%3D%26gt%3B%20Apps%20%3D%26gt%3B%20Default%20Apps%20and%20then%20set%20the%20Edge%20Dev%20as%20default%20browser.%3C%2FP%3E%3CP%3Ehowever%2C%20if%20you%20install%20Edge%20stable%2C%20it%20will%20replace%20Legacy%20Edge%20and%20no%20link%20will%20be%20opened%20in%20the%20Legacy%20Edge%20anymore.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112886%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112886%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EStill%20having%20a%20problem%20when%20trying%20to%20buy%20free%20monthly%20Xbox%20Gold%20Live%20Gold%20games%20for%20Xbox%20360.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20transaction%20starts%20but%20then%20fails%20to%20complete%2C%20and%20shows%20only%20the%20spinning%20circle%20icon%20forever.%20This%20problem%20is%20repeatable%20on%20both%20my%20PCs%20and%20only%20when%20using%20Edge%20Dev%2C%20while%20other%20browsers%20(Firefox%2C%20Edge)%20work%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20reported%20this%20issue%20before%20but%20still%20no%20joy.%20I'm%20surprised%20this%20has%20not%20been%20fixed%20yet%2C%20considering%20that%20it%20is%20a%20transaction%20failure%20that%20affects%20purchases%20on%20an%20official%20Microsoft%20website.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112914%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112914%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3Ecould%20you%20try%20a%20few%20things%20please%3F%3CBR%20%2F%3E1.%20temporary%20disable%20your%20extensions%3A%20edge%3A%2F%2Fextensions%2F%3CBR%20%2F%3E2.%20temporary%20disable%20Tracking%20prevention%3A%20edge%3A%2F%2Fsettings%2Fprivacy%3CBR%20%2F%3E3.%20clear%20saved%20browser%20data%20(cookies%2C%20site%20permissions%20etc)%3A%20edge%3A%2F%2Fsettings%2FclearBrowserData%3CBR%20%2F%3E%3CBR%20%2F%3Edo%20them%20and%20then%20try%20again%20your%20transaction.%3CBR%20%2F%3Eif%20they%20fix%20your%20problem%20then%20great%2C%20if%20they%20don't%2C%20you%20won't%20lose%20anything%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1114789%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1114789%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20guys!%20Why%20isn't%20sign%20in%20supported%20when%20running%20Edge%20as%20administrator%3F%20What's%20the%20reasoning%20behind%20this%20limitation%3F%20Is%20there%20a%20policy%20to%20change%20this%20behavior%3F%20Thanks!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1115010%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1115010%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F410658%22%20target%3D%22_blank%22%3E%40ViniciusFonseca%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F410658%22%20target%3D%22_blank%22%3E%40ViniciusFonseca%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EHello%20guys!%20Why%20isn't%20sign%20in%20supported%20when%20running%20Edge%20as%20administrator%3F%20What's%20the%20reasoning%20behind%20this%20limitation%3F%20Is%20there%20a%20policy%20to%20change%20this%20behavior%3F%20Thanks!!%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3Ethis%20is%20my%20problem%20too.%20Google%20chrome%20works%20and%20allows%20sign%20in%20when%20it's%20run%20as%20administrator%20but%20Edge%20has%20the%20problem%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1115970%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1115970%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20update%20on%20smooth%20scrolling%20for%20edge.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1116502%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1116502%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHaving%20issue%20with%20opening%20web%20pages.%20Every%20time%20I%20open%20a%20web%20page%20I%20it%20just%20clocks%20for%20a%20minute%20then%20I%20get%20the%20%22This%20page%20is%20having%20a%20problem%22%20with%20an%20error%20code%26nbsp%3BSTATUS_ACCESS_VIOLATION.%20I%20noticed%20this%20issue%20being%20reported%20in%20the%20previous%20release%20discussion%20thread%20but%20was%20hoping%20it%20was%20going%20to%20be%20fixed%20in%20this%20thread.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20a%20little%20more%20testing%20and%20found%20that%20any%20site%20I%20have%20that%20tries%20to%20open%20in%20IE11%20will%20actually%20open%20in%20Edge%20Dev.%20I%20also%20looked%20at%20my%20event%20logs%20and%20found%20some%20errors.%20They%20all%20appear%20to%20be%20similar%2C%20so%20I%20proved%20the%20information%20below.%20I%20hope%20you%20find%20this%20information%20helpful.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EEvent%20Viewer%20Log%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EFaulting%20application%20name%3A%20msedge.exe%2C%20version%3A%2081.0.389.2%2C%20time%20stamp%3A%200x5e1cf243%3CBR%20%2F%3EFaulting%20module%20name%3A%20unknown%2C%20version%3A%200.0.0.0%2C%20time%20stamp%3A%200x00000000%3CBR%20%2F%3EException%20code%3A%200xc0000005%3CBR%20%2F%3EFault%20offset%3A%200x0000000000201b02%3CBR%20%2F%3EFaulting%20process%20id%3A%200x360a4%3CBR%20%2F%3EFaulting%20application%20start%20time%3A%200x01d5ce31cb53ce32%3CBR%20%2F%3EFaulting%20application%20path%3A%20C%3A%5CProgram%20Files%20(x86)%5CMicrosoft%5CEdge%20Dev%5CApplication%5Cmsedge.exe%3CBR%20%2F%3EFaulting%20module%20path%3A%20unknown%3CBR%20%2F%3EReport%20Id%3A%20640f9920-822b-4ee8-8b70-afa3d3602947%3CBR%20%2F%3EFaulting%20package%20full%20name%3A%3CBR%20%2F%3EFaulting%20package-relative%20application%20ID%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ecc%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2587%22%20target%3D%22_blank%22%3E%40Steven%20Sanders%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1116505%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1116505%22%20slang%3D%22en-US%22%3EAre%20you%20using%20Forcepoint%2FWebsense%20in%20the%20organization%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1116524%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1116524%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20quick%20reply.%20I%20know%20we%20did%20at%20one%20time%20and%20I%20used%20to%20see%20%22report%20spam%20to%20spam%40forcepoint%22%20in%20our%20external%20emails%20but%20I%20don't%20see%20that%20any%20more.%20I%20will%20need%20ask%20out%20IT%20Security%20to%20see%20if%20it%20is%20currently%20being%20used%20unless%20there%20is%20any%20way%20for%20me%20to%20tell.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20take%20it%20that%20this%20is%20a%20known%20issue%20with%20Forcepoint%2FWebsense%20that%20started%20with%20831.%20If%20so%2C%20is%20it%20going%20to%20be%20resolved%20in%20the%20next%20release%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1116542%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1116542%22%20slang%3D%22en-US%22%3EI'm%20not%20really%20sure%2C%20that's%20something%20josh_bodner%20would%20need%20to%20answer%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1116635%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1116635%22%20slang%3D%22en-US%22%3ECan%20you%20guys%20PLEASE%20do%20something%20about%20the%20behavior%20after%20closing%20the%20last%20tab%3F%3CBR%20%2F%3E%3CBR%20%2F%3ELet's%20say%20I%20finish%20my%20work%20and%20quickly%20close%2015%20tabs%20with%20ctrl%20%2B%20W.%20I%20have%20to%20be%20careful%20not%20to%20close%20the%20last%20tab.%20If%20I%20accidentally%20close%20the%20browser%2C%20I%20then%20have%20to%20login%20to%201Password%20again%20which%20is%20super%20annoying.%20I%20tried%20to%20pin%20a%20tab%20and%20guess%20what%2C%20I%20can%20close%20it%20with%20ctrl%20%2B%20W%20as%20well%2C%20the%20browser%20will%20close%20and%20the%20pinned%20tab%20is%20gone%20after%20relaunching%20the%20Edge.%20That%20is%20completely%20unacceptable%20behavior%20for%20a%20modern%20browser.%3CBR%20%2F%3E%3CBR%20%2F%3E1.%20Give%20us%20the%20option%20to%20NOT%20close%20the%20Edge%20with%20last%20tab%2C%20so%20if%20I%20press%20ctrl%20%2B%20W%2C%20the%20page%20in%20that%20tab%20will%20close%20and%20the%20tab%20is%20now%20showing%20the%20speed%20dial%20(new%20tab%20page).%20That%20is%20how%20Opera%20works%20and%20it's%20great.%3CBR%20%2F%3E%3CBR%20%2F%3E2.%20If%20a%20tab%20is%20pinned%2C%20DO%20NOT%20close%20the%20browser.%20Ctrl%20%2B%20W%20should%20never%20close%20a%20pinned%20tab.%20This%20would%20be%20a%20nice%20%22workaround%22.%3CBR%20%2F%3E%3CBR%20%2F%3ELike%20I%20said%2C%20this%20behavior%20is%20unacceptable%20to%20me%20and%20it%20is%20basically%20the%20only%20reason%20I%20can't%20switch%20from%20Opera%20to%20Edge.%20Hopefully%20you%20can%20do%20something%20about%20this%20soon%2C%20I%20really%20like%20the%20new%20Edge%20otherwise.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1116721%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1116721%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F900%22%20target%3D%22_blank%22%3E%40Jeffrey%20Thorpe%3C%2FA%3E%26nbsp%3Bit%20seems%20to%20be%20a%20sort%20of%20incompatibility%20with%20Forcepoint%20One%20Endpoint%20software.%20I%20have%20the%20same%20issue%20and%20in%20fact%20my%20organization%20is%20using%20it.%20Stopping%20FP%20services%20doesn't%20help%2C%20as%20it%20didn't%20help%20other%20people%20having%20the%20same%20issue.%20However%2C%20the%20problem%26nbsp%3Bmay%20be%20related%20to%20QIP.sys%20driver%20(which%20is%20part%20of%20Forcepoint)%3A%20if%20you%20manage%20to%20stop%20it%2C%20Edge%20will%20eventually%20work%20again.%20In%20alternative%2C%20for%20me%20running%20Edge%20with%20parameter%20%22--no-sandbox%22%20fixes%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECc%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1116739%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1116739%22%20slang%3D%22en-US%22%3EAlso%20you%20can%20find%20the%20conflicting%20drivers%20in%20Edge%20in%20here%3A%20edge%3A%2F%2Fconflicts%2F%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1116749%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1116749%22%20slang%3D%22en-US%22%3E%3CP%3EBest%20version%20ever.%20Really%20cool%20and%20stable%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1117114%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1117114%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F348382%22%20target%3D%22_blank%22%3E%40samuele2%3C%2FA%3E%26nbsp%3B%2C%20thanks%20for%20the%20tip.%20I%20added%20the%20no%20sandbox%20parameter%20to%20my%20shortcut%20and%20it%20Edge%20Dev%20is%20working%20again.%20I%20do%20get%20a%20little%20warning%20about%20the%20unsupported%20command%20line%20flag%20but%20I%20can%20live%20with%20that%20until%20there%20is%20a%20fix%20for%20the%20root%20cause.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1117984%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1117984%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F470422%22%20target%3D%22_blank%22%3E%40DatabaseJase%3C%2FA%3E%26nbsp%3BReplying%20to%20myself%20to%20note%20that%26nbsp%3Brunning%20Edge%20Dev%20with%20parameter%20%22--no-sandbox%22%20fixes%20this%20issue%20too.%20SEP%20is%20most%20likely%20the%20issue%20because%20on%20another%20PC%20without%20SEP%20this%20issue%20doesn't%20occur.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1118738%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1118738%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F391846%22%20target%3D%22_blank%22%3E%40amnesia%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20use%20this%20extension%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fchrome.google.com%2Fwebstore%2Fdetail%2Flast-tab%2Fnggjcpipkefkgldicofgmealjndjnhba%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fchrome.google.com%2Fwebstore%2Fdetail%2Flast-tab%2Fnggjcpipkefkgldicofgmealjndjnhba%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1121406%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1121406%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3BWhat%20time%20does%20the%20Microsoft%20edge%2080%20update%20for%20the%20stable%20and%20beta%20version%20come%20out%3F%3C%2FP%3E%3CP%3EI've%20been%20waiting%20all%20day%20since%20they%20said%20it%20came%20out%20this%20week%20and%20it's%20always%20Tuesdays%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1121121%22%20slang%3D%22en-US%22%3ERe%3A%20Dev%20channel%20update%20to%2081.0.389.2%20is%20live%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1121121%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F526008%22%20target%3D%22_blank%22%3E%40DavidMccready%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20about%20that%20extension%2C%20that's%20not%20the%20point.%20I'm%20using%203-5%20extensions%20(trying%20to%20have%20a%20few%20as%20possible)%20and%20I'm%20not%20going%20to%20use%20one%20for%20such%20a%20basic%20feature.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Microsoft

Hello Insiders, today we’re releasing build 81.0.389.2 to the Dev Channel.  It’s a smaller update this week since we’re focusing on our other channels, including our very first Stable channel update:  https://blogs.windows.com/msedgedev/2020/01/15/upgrading-new-microsoft-edge-79-chromium/!  As part of that, we also announced a fun opportunity coming up later today to talk directly to some members of our development team.  For details, see https://techcommunity.microsoft.com/t5/discussions/updated-a-chance-to-talk-directly-with-microsoft-....  

 

Additionally, we’ve started a discussion about the future of the Fluent Design Language and how it’s utilized in Edge:  https://techcommunity.microsoft.com/t5/discussions/discussion-updating-our-interface-with-fluent-tou....  As for the most noteworthy features and fixes this week: 

 

Added features: 

 

  • Added the ability to hide the Collections button from the address bar.
  • Added a “coming soon” message to all users who still have favorites sync disabled.
  • Added a dialog to inform users when another program on the device installs an extension in Edge.
  • Enabled integration of the Windows built-in spellchecker.
  • Added a management policy to prevent the first run experience from running.

 

Improved reliability: 

 

  • Re-enabled favorites sync for some users who hadn’t gotten it re-enabled last week.
  • Fixed an issue where sorting favorites and then hitting undo sometimes causes the favorites to be deleted.
  • Fixed an issue on Mac where the send feedback button sometimes crashes the browser.
  • Fixed a crash when using accessibility software like screen readers.
  • Fixed an issue where closing an IE mode tab sometimes crashes the browser.
  • Fixed an issue where attempting to customize sync settings during the First Run Experience crashes the tab.
  • Fixed an issue where watching DRM-protected video like on Netflix doesn’t play at the highest possible quality on certain devices with Nvidia graphics.

 

Changed behavior: 

 

  • Improved Read Aloud performance.
  • Fixed an issue where exporting a Collection to Excel results in the column headers being messed up.
  • Fixed an issue where cancelling an edit on a Collections item doesn’t undo the changes to it.
  • Fixed an issue where sites that are deleted from the Top Sites tiles on the New Tab Page sometimes return.
  • Fixed an issue where the Share UI doesn’t appear when the Share button is clicked.
  • Fixed an issue where the link in Settings to manage a browser profile’s associated account sometimes doesn’t work.
  • Fixed an issue where linked clicked from other applications sometimes don’t open if Edge is already running and was launched with administrator privileges.
  • Fixed an issue where Tracking Prevention sometimes causes content blocked notifications to the right of the address bar (cookies, for example) not to appear properly.
  • Fixed an issue where the ink customization options when annotating feedback screenshots don’t work.
  • Fixed an issue where the Grammar Tools color picker isn’t visible.
  • Fixed an issue where the Cisco Webex extension doesn’t work properly.
  • Fixed an issue where manually navigating to an extension’s page by typing their address into the address bar doesn’t work.
  • Fixed an issue where editing settings from within an Application Guard window that causes the window to have to close and re-open leads to the window closing, but never re-opening.

 

Known issues: 

 

  • After an initial fix for it recently, some users are still experiencing Edge windows becoming all black. UI popups like menus are not affected and opening the Browser Task Manager (keyboard shortcut is shift + esc) and killing the GPU process fixes it. 
  • Some users are still not seeing Collections being enabled by default on Canary and Dev. For users who want to try Collections, enabling the flag at edge://flags/#edge-collections should still work to turn on the feature. 
  • There are some issues where users with multiple audio output devices sometimes don’t get any sound from Edge. In one case, Edge becomes muted in the Windows Volume Mixer and unmuting it fixes it.  In another, restarting the browser fixes it. 
  • At certain zoom levels, there is a noticeable line between the browser UI and the web contents.

 

For those using the Beta channel, we're also releasing the first update to major version 80 to it this week.  Thank you for all your feedback and bug finds that got us there! 

 

47 Replies
Highlighted
Nice, has the problem with forcepoint causing Access Violation error been solved?
Highlighted

@josh_bodner This update has a bug in the dark theme that caused the omnibox - along with the suggestion box, to be locked at light theme, regardless of the preferences. I really hope this will be fixed in the next Dev build.

Highlighted

@josh_bodner This and the previous dev channel builds have been broken for me.  When opening Edge the application area is all white with no UI visible.  After a while the UI loads and the infamous "This page is having a problem" appears (no access to about, settings, or feedback).

 

I expect this is all related to Symantec Endpoint Protection, which appears to have on-going issues with the latest Chrome 81 builds, since this issue doesn't happen on machines I test that do not have SEP installed.

 

Workaround is to use the Beta channel which is still based on Chrome 79.

Highlighted
Stable is also using Chromium 79 :)
microsoft.com/edge
Highlighted

@josh_bodner The "Enabled integration of the Windows built-in spellchecker" feature, does not seem to be fully supporting Hardware Keyboard - Autocorrect misspelt words as I type feature from Windows 10? Is this something you will be enabling in the future?

 

Also, do we know why overlay-scrollbars flag has been removed? I have been using it on chrome for years and was happy to know that edge was supporting them in insider; the native Windows 10 thick scrollbars are just too large and not very modern looking, occupying significant amount of space when not needed. Would be great if Edge scrollbars would be able to use XAML scrollbars like the ones used by the UWP framework.

 

I now have to use extension called Minimal Scrollbar to achieve similar result, although not supported on all website, it makes the scrollbars so much more pleasant.

Highlighted
Still missing feature to directly "Open" a file without downloading it first (all MS browsers have this feature)
Highlighted

@Yoneff 


@Yoneff wrote:
Still missing feature to directly "Open" a file without downloading it first (all MS browsers have this feature)

https://techcommunity.microsoft.com/t5/Discussions/Provide-run-open-save-save-as-options-when-downlo...

Highlighted
Maybe they mean this flag is turned on by default

Use Windows Spellchecking
Use Windows spellchecking dictionaries when available to find spelling mistakes and provide suggestions. – Windows
#win-use-native-spellchecker
Highlighted

@josh_bodner 

1. Will EdgeDev continue to be separate from the now-released new Edge?

2. How do we remove the old Edge from our computers? Uninstall is grayed out.

3. Why do you keep opening the old Edge after updates to new Win 10 builds, even though EdgeDev is the default browser?

Highlighted

@JimRome 

Spoiler

@JimRome wrote:

1. Will EdgeDev continue to be separate from the now-released new Edge?

2. How do we remove the old Edge from our computers? Uninstall is grayed out.

3. Why do you keep opening the old Edge after updates to new Win 10 builds, even though EdgeDev is the default browser?


1. Yes, definitely, 100%. just like Google uses their Beta/Dev/Canary channels to continue developing Google chrome further, Microsoft uses Beta/Dev/Canary channels to develop and improve Microsoft Edge.

new features always appear in Canary, then on Dev, then on Beta, and finally on Stable channel.

so yes they will be separate which also means you can have and install them all at the same time on the same computer without any problem.

 

2. You don't. it's a built in preinstalled UWP app and there is no option in the Windows settings nor in control panel to remove/uninstall it.

when you install stable version of the new Microsoft Edge, it will automatically replace the Legacy Edge, although you can make a minor adjustment to the Group Policy to allow them to run side by side.

 

3. Go to Windows settings => Apps => Default Apps and then set the Edge Dev as default browser.

however, if you install Edge stable, it will replace Legacy Edge and no link will be opened in the Legacy Edge anymore.

 

 

Highlighted

@josh_bodner 
Still having a problem when trying to buy free monthly Xbox Gold Live Gold games for Xbox 360.

 

The transaction starts but then fails to complete, and shows only the spinning circle icon forever. This problem is repeatable on both my PCs and only when using Edge Dev, while other browsers (Firefox, Edge) work fine.

 

I have reported this issue before but still no joy. I'm surprised this has not been fixed yet, considering that it is a transaction failure that affects purchases on an official Microsoft website. 

Highlighted
Hi,
could you try a few things please?
1. temporary disable your extensions: edge://extensions/
2. temporary disable Tracking prevention: edge://settings/privacy
3. clear saved browser data (cookies, site permissions etc): edge://settings/clearBrowserData

do them and then try again your transaction.
if they fix your problem then great, if they don't, you won't lose anything :)
Highlighted

Hello guys! Why isn't sign in supported when running Edge as administrator? What's the reasoning behind this limitation? Is there a policy to change this behavior? Thanks!!

Highlighted

@ViniciusFonseca 


@ViniciusFonseca wrote:

Hello guys! Why isn't sign in supported when running Edge as administrator? What's the reasoning behind this limitation? Is there a policy to change this behavior? Thanks!!


Hi,

this is my problem too. Google chrome works and allows sign in when it's run as administrator but Edge has the problem

Highlighted

Any update on smooth scrolling for edge. @josh_bodner 

Highlighted

@josh_bodner 

 

Having issue with opening web pages. Every time I open a web page I it just clocks for a minute then I get the "This page is having a problem" with an error code STATUS_ACCESS_VIOLATION. I noticed this issue being reported in the previous release discussion thread but was hoping it was going to be fixed in this thread.

 

Did a little more testing and found that any site I have that tries to open in IE11 will actually open in Edge Dev. I also looked at my event logs and found some errors. They all appear to be similar, so I proved the information below. I hope you find this information helpful.

 

Event Viewer Log:

Faulting application name: msedge.exe, version: 81.0.389.2, time stamp: 0x5e1cf243
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000201b02
Faulting process id: 0x360a4
Faulting application start time: 0x01d5ce31cb53ce32
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
Faulting module path: unknown
Report Id: 640f9920-822b-4ee8-8b70-afa3d3602947
Faulting package full name:
Faulting package-relative application ID:

 

cc: @Steven Sanders 

Highlighted
Are you using Forcepoint/Websense in the organization?
Highlighted
Thanks for the quick reply. I know we did at one time and I used to see "report spam to spam@forcepoint" in our external emails but I don't see that any more. I will need ask out IT Security to see if it is currently being used unless there is any way for me to tell.

I take it that this is a known issue with Forcepoint/Websense that started with 831. If so, is it going to be resolved in the next release?
Highlighted
I'm not really sure, that's something josh_bodner would need to answer :)
Highlighted
Can you guys PLEASE do something about the behavior after closing the last tab?

Let's say I finish my work and quickly close 15 tabs with ctrl + W. I have to be careful not to close the last tab. If I accidentally close the browser, I then have to login to 1Password again which is super annoying. I tried to pin a tab and guess what, I can close it with ctrl + W as well, the browser will close and the pinned tab is gone after relaunching the Edge. That is completely unacceptable behavior for a modern browser.

1. Give us the option to NOT close the Edge with last tab, so if I press ctrl + W, the page in that tab will close and the tab is now showing the speed dial (new tab page). That is how Opera works and it's great.

2. If a tab is pinned, DO NOT close the browser. Ctrl + W should never close a pinned tab. This would be a nice "workaround".

Like I said, this behavior is unacceptable to me and it is basically the only reason I can't switch from Opera to Edge. Hopefully you can do something about this soon, I really like the new Edge otherwise.
Highlighted

@Jeffrey Thorpe it seems to be a sort of incompatibility with Forcepoint One Endpoint software. I have the same issue and in fact my organization is using it. Stopping FP services doesn't help, as it didn't help other people having the same issue. However, the problem may be related to QIP.sys driver (which is part of Forcepoint): if you manage to stop it, Edge will eventually work again. In alternative, for me running Edge with parameter "--no-sandbox" fixes it.

 

Cc: @josh_bodner 

Highlighted
Also you can find the conflicting drivers in Edge in here: edge://conflicts/

Highlighted

Best version ever. Really cool and stable

Highlighted

@samuele2 , thanks for the tip. I added the no sandbox parameter to my shortcut and it Edge Dev is working again. I do get a little warning about the unsupported command line flag but I can live with that until there is a fix for the root cause. 

Highlighted

@DatabaseJase Replying to myself to note that running Edge Dev with parameter "--no-sandbox" fixes this issue too. SEP is most likely the issue because on another PC without SEP this issue doesn't occur.

 

@josh_bodner 

Highlighted
Highlighted

@DavidMccready 

 

I know about that extension, that's not the point. I'm using 3-5 extensions (trying to have a few as possible) and I'm not going to use one for such a basic feature.

Highlighted

@josh_bodner What time does the Microsoft edge 80 update for the stable and beta version come out?

I've been waiting all day since they said it came out this week and it's always Tuesdays

Highlighted
The "Enabled integration of the Windows built-in spellchecker" feature, does not seem to be fully supporting Hardware Keyboard - Autocorrect misspelt words as I type feature from Windows 10? 

@Thomaszko I wonder if this is something we also don't support yet for the onscreen keyboard, or is just specific to the hardware keyboard.  Either way, could you file in-product feedback about this so we can get it in our bug database just in case it's not already?  

Highlighted

Spoiler

3. Why do you keep opening the old Edge after updates to new Win 10 builds, even though EdgeDev is the default browser?

3. Go to Windows settings => Apps => Default Apps and then set the Edge Dev as default browser.


@HotCakeX I think he means the fact that, after you upgrade to a new build of Windows, we auto-launch Edge Legacy.  That behavior is hard-wired and has nothing to do with the default browser.  We're working on replacing that behavior so that Edge Stable (once it's installed) will be able to auto-launch itself, but since Edge Stable isn't going to be auto-installed on peoples' machines for a while, you'll probably want to just install Edge Stable yourself if you want to stop seeing Edge Legacy.  

Highlighted

@HotCakeX wrote:

@ViniciusFonseca 


@ViniciusFonseca wrote:

Hello guys! Why isn't sign in supported when running Edge as administrator? What's the reasoning behind this limitation? Is there a policy to change this behavior? Thanks!!


Hi,

this is my problem too. Google chrome works and allows sign in when it's run as administrator but Edge has the problem


@HotCakeX I'm curious why you want to run Edge as administrator?  Doing so defeats a lot of the security that the sandboxes provide, so it's not a state we want people to be in.  (It also caused people whose machines were configured in a certain way to not be able to load any webpages; see https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/.  That's why we put in the warning when you're running Edge as an administrator!)  

Highlighted

I'm using 3-5 extensions (trying to have a few as possible) and I'm not going to use one for such a basic feature.

@amnesia I'd like to know more about why this feature that's easy to implement as an extension shouldn't be.  Is it just a principled thing, like that the browser should do as much as it can natively? (Which also has counter-arguments that a browser should be as simple as possible.)  Or is it because of fears of performance penalties?  Personally, I find it very helpful that we now have access to the Chrome extension store since there are lots of features that can be implemented as extensions now instead of having to wait for us to get around to building them in natively.  

Highlighted

What time does the Microsoft edge 80 update for the stable and beta version come out?

@ZeroUserr The update to bring Beta up to version 80 happened last week, so if your Beta isn't at 80 yet, something's probably wrong.  It and Stable will never be at the same version, which means that 80 will come to Stable once 81 hits Beta (although they were both technically at 79 together before we officially released Stable since we were just publishing the same bits to Beta and Stable back then in order to test our Stable publishing pipeline).  

Highlighted
Replying to myself to note that running Edge Dev with parameter "--no-sandbox" fixes this issue too. SEP is most likely the issue because on another PC without SEP this issue doesn't occur.

@DatabaseJase just remember to remove that flag once we get it fixed!  No update on the fix yet, but I've asked the devs if there's anything we should expect for next week.  

Highlighted

@josh_bodner 


@josh_bodner wrote:

@HotCakeX wrote:

@ViniciusFonseca 


@ViniciusFonseca wrote:

Hello guys! Why isn't sign in supported when running Edge as administrator? What's the reasoning behind this limitation? Is there a policy to change this behavior? Thanks!!


Hi,

this is my problem too. Google chrome works and allows sign in when it's run as administrator but Edge has the problem


@HotCakeX I'm curious why you want to run Edge as administrator?  Doing so defeats a lot of the security that the sandboxes provide, so it's not a state we want people to be in.  (It also caused people whose machines were configured in a certain way to not be able to load any webpages; see https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/.  That's why we put in the warning when you're running Edge as an administrator!)  


 

Hi thanks for the reply,

well the thing is I don't want to deliberately run Edge as admin, sometimes the situation enforces it.

like when I use Edge on Windows server or in Windows Sandbox.

those are not rare situations at all. in those cases we can't use sign in.

I understand it's a security risk but at least for users that know what they are doing, there needs to be a way to go around it..

the de-elevate on launch flag doesn't help

Highlighted
ismayil.59@hotmail.com
Highlighted
Highlighted
You are risking getting spam emails putting your email in there in plain text
Highlighted

 


well the thing is I don't want to deliberately run Edge as admin, sometimes the situation enforces it.

like when I use Edge on Windows server or in Windows Sandbox.


@HotCakeX ah, that makes sense, those local admin accounts launch everything as an admin.  I'll see if we've got any plans around getting that auto-de-elevate to work in those contexts.  

Highlighted
Thank you, appreciate it :)
Highlighted
I see it as a potential security problem and/or privacy leak (because of the required permissions/data access). Plus, I don't like how this extension works. It creates and invisible pinned tab and moves the "real" tab to the right. To me, the browser feels and looks crappy.

I'm using extensions to "integrate" other services to the browser (something like 1Password or raindrop.io), not to add basic functions or improve/add behavior that should have been there from the start.
Highlighted
I see it as a potential security problem and/or privacy leak (because of the required permissions/data access). Plus, I don't like how this extension works. 

@amnesia makes sense, we've gotten quite a lot of feedback about the trustworthiness of extensions.  In fact, that's one of the main reasons we're creating our own extension store instead of just exclusively using Google's.  Anything that's in our store has been vetted by us for a base level of security and trustworthiness, and we hope to import a substantial portion of the existing extensions from Chrome's store into ours in the future (assuming they pass our vetting process).  

 

And I guess if you also have a particular problem with the way that extension functions, there are others you can try, although they most likely will operate similarly since there's no way for an extension to stop the last tab from closing and thus also taking down the window except by making sure it's actually not ever the last tab in the window (for example, https://chrome.google.com/webstore/detail/live-on/oficfgdfeoknbjfhommlpiekdapmnebh/https://chrome.google.com/webstore/detail/keep-one-pinned-tab/nmcefdbkkkjndgafnlaikloffhdeknod).  

Highlighted
That's really great to know. I think in the future Microsoft Edge extension store will be the most secure/trustworthy one, after that is Firefox and then is Chrome and others in 4th 5th place etc...
Highlighted
Highlighted

@josh_bodner I feel like we're going in circles. Again, I will not use an extension from Google's store to add some basic functionality to a modern browser.

Highlighted
Google doesn't own those extensions though, so the name "Google" is irrelevant here.
each extension developer owns the extension they make. the developers can put their extensions on various places, Google extension store, Microsoft Add-on store, Windows store, Opera add-on store etc.

the point is, Edge is now using Chromium, which is the best platform right now in terms of extension development and extension availability. so why not use that potential.
Highlighted
hızlı bir şekilde yapıyorum